-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
after upgrade to SDK 49 App Crash on Production when i upload it on Google Play #2046
Comments
On the Expo build dashboard you will see on last build log this Error :
The Problem still occure Even After i changed the dependencie @react-native-community/datetimepicker version.you can check the Build with id "1d389109-d3af-4d31-99ed-fd69d6ab21f6" done in Sep 5, 2023 2:57 AM , it has no Error |
Hi, have you managed to debug with USB debugging? We have a very similar case and our error message is java.lang.AssertionError: The embedded manifest is invalid or could not be read. Make sure you have configured expo-updates correctly in android/app/build.gradle |
no i didn't try to debug with USB, also i'm Expo, i dont have android/app/build.gradle |
this Problem really took me many days. the big problem is i dont get an Error or just warning about where the problem could be. I had to Downgrade to SDK 48 to make it Work, that prove that there's a problem while using SDK 49 |
I faced the same problem. |
Hi, Here are some docs that might help you with debugging this issue: https://docs.expo.dev/debugging/runtime-issues/#production-errors. I think that in your case it might be worth seeing logs in the logcat. It might give you some useful insights about the problem you face because, without any more information, it's hard to know what's going on. If the issue you face is related to |
I'm also experiencing this issue. We want SDK version 49 because it really pulls together the development and release loop. Inevitably we had to revert to SDK 48. |
SDK 49 does not work for me either. I had to downgrade to SDK 48. It somehow works in development mode with expo start but does not work when building it with eas. I will be happy to help with this issue and provide more information if needed. |
Thanks
Thank you for your solution it's quite helpful to me. i am searching the solution from two days |
We have the same issue as well. SDK 49 crashes when built using GH actions (eas --local) but when it's built using EAS servers, the app does NOT crash. Hopefully, someone can verify my comment, and see if it doesn't crash when you build through EAS servers?? |
I have had the same problem for 5 days. |
We have had the same problems. After switching to 49, the app works on the simulator but not in production. We will try to downgrade to 48. |
I removed the "react-native-reanimated": "~3.3.0",dependency and it solved my problem. observation: the build eas development works without problems with the dependency, however the build eas internal preview(apk) crashes |
This also worked for me. I was having this issue on iOS. Thanks. |
This solved my issue. App was crashing on startup and now is not. This is using expo 49 |
I am having this issue. Proposed solutions are not working. |
I was having the issue with ios testflight. This worked perfectly. Thank you I was lost without it. |
I've also had to employ this strategy for Android. The dev build works as expected; it's only when a production build is performed that a crash without error or stack trace occurs |
This sollution works for me, SKD 49 crashed when running on production mode and TestFlight. |
how to remove? |
Facing the same issue, It is happening in version 50 as well. |
Facing the same issue on IOS. No fix has worked yet |
Expo used to work well perfectly back in the days tried using it for our application it didn't work. Application was stuck on splashscreen despite we're using official recommendations from the docs. I love the React Native ecosystem but we're pushed at this point to use Flutter. |
Try to look into the system logs from the crash (e.g. with Android Studio). |
You may not remove it, if you're using it in your project you just have to add The solution that works for me is to add |
Build/Submit details page URL
https://expo.dev/accounts/oakoudad/projects/Biolens-App
Summary
the App was working fine, after i Upgrade to SDK 49, i test it on Android Studion emulator it worked fine, also in Expo go.
=> Expo doctor shows no Error
The Probelm is : After publishing new version of app on Google Play, the app Crash on oppening .
Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22621
Binaries:
Node: 18.17.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 9.8.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: AI-222.4459.24.2221.10121639
npmPackages:
expo: ^49.0.0 => 49.0.9
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.72.4 => 0.72.4
react-native-web: ~0.19.6 => 0.19.8
Expo Workflow: managed
WARNING: We recommend using PowerShell or Bash via WSL 2 for development with Expo CLI on Windows. You may encounter issues using cmd.exe.
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!
Error output
No response
Reproducible demo or steps to reproduce from a blank project
the project show no error, i will include here the Packages i'm using.
packages.json
Eas.json
The text was updated successfully, but these errors were encountered: