hi @languste, there is a known issue in our current SDK 29 release where our Assets module is lazily loaded. To confirm that this is indeed the issue in your case, could you make the following changes to your app:
import Expo from 'expo';
Expo.Asset; // <----- Add this line here
This will explicitly load the Asset module (if our module doesnt get loaded in time, it falls back to React Native’s default Asset module behavior which does not take into account bundled assets)
I tried your suggestion (on different code locations) but it does not to fix this issue for me .
Any further tips or recommondations to debug this?
maybe debugging /usr/local/lib/node_modules/exp/node_modules/xdl/build/Project.js and comparing hashes?
or adding some debug code to figure out if React Native’s asset resolution for Image components has been overwritten or not?
Furthermore it would be nice if someone could confirm this issue. Any recently iOS (simulator/standalone) build with assetBundlePatterns configured should be sufficient to trigger this issue on a cold/offline first start.