EAS update breaks the app & assets do not load

[deveshXm]

Build/Submit details page URL

link

Summary

I am using expo to build an app & recently I tried to send updates using eas update. I followed the documentation on sending updates however when I receive the update the views & texts I added were loading up for e.g. I added a text "update version" which was not in the first build but after receiving the update the text was showing but the images & icons did not load which were already present in the build (I did not send them by update). After reloading the app it rolls back & goes back to the previous version which is the build itself. The changes which I sent over update are working perfectly fine in local environment & they are showing no errors to me.

I found this stack overflow question which had the exact same issue, I followed what was mentioned in the solution but still the error persisted.

Managed or bare?

my project is managed

Environment

expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22621
Binaries:
Node: 16.19.0 - C:\Program Files\nodejs\node.EXE
npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: AI-221.6008.13.2211.9514443
npmPackages:
expo: ~48.0.6 => 48.0.6
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.71.3 => 0.71.3
react-native-web: ~0.18.11 => 0.18.12
Expo Workflow: managed

Expo doctor :

Expected package @expo/config-plugins@~6.0.0
Found invalid:
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
(for more info, run: npm why @expo/config-plugins)
Some dependencies are incompatible with the installed expo package version:

• react-native-safe-area-context - expected version: 4.5.0 - actual version installed: 3.3.2
• react-native-svg - expected version: 13.4.0 - actual version installed: 12.1.1
  Your project may not work correctly until you install the correct versions of the packages.
  To install the correct versions of these packages, please run: expo doctor --fix-dependencies,
  or install individual packages by running expo install [package-name ...]
  PS C:\Users\Devesh\Desktop\Bento Workspace\bento>

Error output

No response

Reproducible demo or steps to reproduce from a blank project

Ran the following commands in the project to configure for updates

1. expo install expo-updates && eas update:configure && eas build:configure

2. Built application using eas build with channel name set to development in eas.json.

3. Made some changes in the code like adding text then send update to channel development using command eas update --branch development.

4. Linked the branch development with channel development. (Pardon me for naming both channel & branch with same name)

5. Received update after opening & closing app 1-2 times.

6. Text & view which were reflecting changes, but the app failed to load images & icons.

7. App went back to previous version that is the build itself after reloading.

[quinlanj]

Thanks for reporting this issue! In order of usefullness, here are some things you can provide to help us root cause the problem:

Very Helpful

A simple app where you’ve been able to reproduce this issue. Please share:

- the app code


- links to your update. Also whether you are loading via ios or android

- 
link to your build which you tried to load the update from


Somewhat Helpful

In your existing app, please share:

• package.json at the time you made the build
• package.json at the time you made the problematic update

[leons1767]

I had the exact same issue with SDK46. Missing in the Getting started is the fact that eas update does not support SECRET nor pack .env file during update. One simply lost all the environment variables that are accessible during eas build. This is documented in Using environment variables with EAS Update.

The same issue is discussed in issue#1265. If you are using .env file, DevYuns provided a solution in the discussion.

[quinlanj]

Closing due to inactivity. @deveshXm if you were using the Asset module and encountering these errors, it may be due to this: #1688 (comment) .