Hi all,
I have a situation where my ejected Android app doesn’t load the latest bundle from the Expo servers.
Or, that is, I can see from Sentry logs that a few phones have downloaded the latest version. But the vast majority - 99% ish hasn’t. The app is in production.
(this has not been a problem earlier with this app)
I did the following to make sure.
-
expo publish
(bundle1) - Build signed app in Android Studio
-
adb install
on phone - Confirm bundle1 is loading in app on phone,
-
expo publish
(bundle2, version number += 1) - Confirm bundle2 is loading in app on phone,
- Upload to Play Store, rollout
- Wait a few hours
- Uninstall manually installed app from phone
- Install app from Play Store
- Confirm bundle2 is loading in app on phone, nope, bundle1 is being served
- Scratch head
-
expo publish
(bundle3, version number += 1) - Confirm bundle3 is loading in app on phone, nope, bundle1 is being served
- Scratch head again, search forums and GitHub for clues
- Post question in forum
- Wait…
The weirdest thing is that a tiny small percentage of my user base has recieved the bundle3 version.
Is there a way to trace the query from my app and the response the bundle server returns? Without doing it from inside the app.
If someone at @Expo looks in to this, the app is @fmckl/REG
. Bundle version being served (to most users) is 3.75.1
, latest version is 3.75.3
. Release channel expo-31
.
Thanks
// Kristofer
Expo CLI 2.4.0 environment info:
System:
OS: macOS High Sierra 10.13.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.13.0 - ~/.nvm/versions/node/v10.13.0/bin/node
npm: 6.4.1 - ~/.nvm/versions/node/v10.13.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.1 AI-173.4907809
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
expo: ^31.0.5 => 31.0.5
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-31.0.1.tar.gz => 0.57.1
react-navigation: ^2.18.2 => 2.18.2
npmGlobalPackages:
expo-cli: 2.4.0