Woahhhhh that's very strange. The first broken state is the very first (and very buggy) first version I ever shipped to test flight. The last is the current version.
Let me try shipping a new version and we'll see if that fixes things. Thanks so much for bringing this up.
Yeah, that's really strange! I wonder if it's a build process glitch (e.g. old build artifacts that got bundled with release build?) or some really weird issue on Apple's end? :-/
It would be great if you could write something about that glitch if you figure out the cause or hear back from Apple. I also wanted to write a React Native app for App Store release soon, so I guess I might also run into it :-)
I have a suspicion it's somehow related to expo/react-native. I cleaned the local cache and deleted all previous versions before uploading. Hopefully this should fix it 😬
I'm building this on Expo, which offers a way to update the app asynchronously in the background instead of requiring a user to wait for the update to load. There's a setting that was set here that caused it to throw up an old version first and then load in the background.
But I removed that and am pushing up a new build which should be good.
Woahhhhh that's very strange. The first broken state is the very first (and very buggy) first version I ever shipped to test flight. The last is the current version.
Let me try shipping a new version and we'll see if that fixes things. Thanks so much for bringing this up.
Yeah, that's really strange! I wonder if it's a build process glitch (e.g. old build artifacts that got bundled with release build?) or some really weird issue on Apple's end? :-/
It would be great if you could write something about that glitch if you figure out the cause or hear back from Apple. I also wanted to write a React Native app for App Store release soon, so I guess I might also run into it :-)
I have a suspicion it's somehow related to expo/react-native. I cleaned the local cache and deleted all previous versions before uploading. Hopefully this should fix it 😬
That might do the trick! I'll let you know when I receive the update
Cool I think I figured out what's up.
I'm building this on Expo, which offers a way to update the app asynchronously in the background instead of requiring a user to wait for the update to load. There's a setting that was set here that caused it to throw up an old version first and then load in the background.
But I removed that and am pushing up a new build which should be good.
I was having the same issue, looking forward to the update.
Loved doing the exercise either way! I think this app is going to help me.