I have an expo build that I am running in order to submit it to the app store. It says that it is still building but when i go into the logs it shows that it is complete. I do not know why it got stuck on this step and how to fix it. What should I do.
it usually shows that i can download the build in order to submit it to app store but it just shows queued even though it completed the build.
This was a temporary issue with the website a couple hours ago. Specifically build job statuses weren't being synced with the website, causing completed builds to remain in a "Queued" state. This issue has been resolved and builds now show their correct statuses. Successfully completed builds will now show a "Finished" state and be downloadable.
Related
I have been trying to build my apk today but I always face this problem. After completing the build, i download it to my phone and i cannot open it. However, this was not the case 2-3 days ago. I had no difficulties or errors in Run expo doctor. I was able to download the apk to my device and test my app.
I am not really sure what to do and any help would be appreciated.
This is what I got after running npx expo doctor:
I managed to solve my problem. I used Android Studio's logcat feature and when I ran the app on the emulator I found the issue - it was related to admob. At this point, I dont need admob, so I deleted its folder from my project and everything was fine after this.
Running expo doctor usually ends up in flagging what dependency needs to be upgraded if the jump to automatically update it goes into the majors like in your case from 4 to 5.
Maybe try upgrading #expo/config-plugins by using expo upgrade or commands from your preferred package manager.
If that’s impossible due to other packages depending on the specific version, maybe consider adding overrides in your package.json. Here is a helpful article about that.
In my experience this may not be the only reason for the crash of the app. Try running the app consecutively about 3 or 4 times even if it crashes and I believe Android will prompt you to submit a bug report and maybe show you the call stack it failed at.
Let us know how it goes.
So this has been asked before but I'm asking it again because nothing has worked, I've read through all of the similar posts I could find and all but one has semi fixed the problem.
https://medium.com/#adityasingh_32512/solved-unable-to-load-script-from-assets-index-android-bundle-bdc5e3a3d5ff
This medium article is the only solution that i can find that will get debug builds running again but that is only because it is pre packaging the javascript bundle and not really fixing the problem of the app not connecting to the metro server, once the debug build is running via this method I'm unable to shake the device and get the debug menu to show up.
I've been developing this app for probably 10 months, live for 3-4 months, and can usually trudge through these errors that pop up but this one is tricky.
I've been using cleartextTrafficPermitted="true", tried implementing a custom network security config android:networkSecurityConfig="#xml/network_security_config", tried a different physical device, cleared the metro cache, deleted .gradle/ build folders, cleaned, rebuilt.. All with the same end result of the app crashing on boot and the same error in logcat Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.
Release builds work but that's because its not trying to connect to the metro server, pretty stumped on this one.
Answering this for others that might find it useful. Still not sure what I did wrong but in the process of setting up a CI/CD pipeline for the app I re cloned the project and magically android debug builds started working again. No changes to the code, the android project must have gotten corrupted somehow so recloning allowed android studio to start from square one. Weird one.
I just uploaded a new build to the App Store Connect. The build has finished "Processing" under the Activity tab, but it's still on "Processing" on the TestFlight tab.
The most bizarre thing is that not only the just uploaded Build is "Processing" but ALL OF THEM, builds that were uploaded and processed long ago.
Activity Tab
TestFlight Tab
This is the first time I experienced this, does anyone knows what is going on?
As it turns out, it was only a visual bug on the AppStore Connect. After a long time processing everything went back to normal.
I'm the only one stupid? Since yesterday evening I am trying to upload to TestFlight my project and see ...
Dear XXXXXX, While processing your iOS app, XXXXXX 1.0(2685), errors
occurred in the app thinning process, and your app couldn’t be
thinned. If your app contains bitcode, bitcode processing may have
failed. Because of these errors, this build of your app will not be
able to be submitted for review or placed on the App Store. For
information that may help resolve this issue, see Tech Note 2432.
Regards, The App Store team
iOS 10 problems ?
but validation is successful
bit code = off, privacy keys -> set & Two days ago it was Ok, project code is not changed
Thanks in advance for answers
So iv spent the last couple of weeks building my first app in Android Studio and all has gone well. Successfully launched on device through whole testing / Dev phase.
I got to a point where I was happy and proceeded to build a signed APK using Build->Generate Signed APK.
This was successful and now I have a published APK.
I have since noticed a spelling mistake (Rookie error!).
I have corrected the spelling but now when I click the "play" button to launch a test version it appears to be building the app on outputs a big stack trace ending with the following...
BUILD SUCCESSFUL
Total time: 1 mins 21.581 secs 13:15:46: External task execution
finished 'build'.
But then that is it, no offer to view on device like during the initial build stage. (no device popup)
What am I missing to get this to publish onto a test device again?
Any help or pointers are appreciated, I'm new to this Gradle thing, I have a feeling its something to do with that but I don't know where to start and Google doesn't seem to find anything useful to me :/