-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Android app not starting after release - only shows boot splash screen #2431
Comments
me too
2023-05-11 18:03:05.651 31774-31806 ReactNativeJNI com.goodmorning I Memory warning (pressure level: TRIM_MEMORY_UI_HIDDEN) received by JS VM, ignoring because it's non-severe |
I have tried all the solutions mentioned above. |
i have same issue |
The set of patterns where the first occurrence is packaged in the APK. For each native library APK entry path matching one of these patterns, only the first native library found with that path gets packaged. Example: android.packagingOptions.jniLibs.pickFirsts += "**/pickFirst.so" |
Hi all, thanks for the bug report. I am able to reproduce it - still searching for a solution at the moment. |
same issue |
+1 |
Same issue, in logs saw two error, one with |
package.json, remove this line |
Ah so it is a pick a flow (vanilla or Expo) issue, thank you |
still force close for me |
thank you so much, it worked for me |
greetings! can you send the error log |
10:14 M 0
|
on my project, i try custom root path using babel-plugin-module-resolver, is it make impact to build release app or not ? |
can you upload a sample project with the reported error? I need to take a closer look to be able to help. hug. |
first i try build from new ignite boilerplate then i build release and its working well. conclusion is the problem when when i try migrate to v8.8.2, so i try again to remigrate from v8.7.0 to v8.8.2 . first build still force close after i follow this my APK running well on device. Thankyou ! @geninhocell |
because the problem is not from IOS 😆 |
Thanks for save my hours |
I've cooked up a fully automatic fix, it just requires the add import Constants, { ExecutionEnvironment } from "expo-constants";
const isInExpoMode = Constants.executionEnvironment === ExecutionEnvironment.StoreClient;
const entryPoint = isInExpoMode ? require("./App") : require("./index");
export default entryPoint In your "main": "entry-point.js", This will direct any run modes that use the Tested and confirmed working on:
For further reading here is the link to the documentation on runtime detection in expo projects |
Just tested this in the latest version of Ignite (v9 to be released) and it is no longer an issue just FYI for new projects that will use this template. Thanks to all who chimed in here to help others along! |
just updated 8.7.0 to 8.8.2, and got the same problem on Android. Success run release mode after remove this line. Thankyou for the solution. |
@gwijaya94 Do you have both expo splash screen and react native bootsplash installed? |
@frankcalise Yeah both are installed, with reference from Ignite-diff-purge. |
@gwijaya94 Do you have both expo splash screen and react native bootsplash installed? Try dropping expo splash screen then |
|
none of the above fixes are working for me any ideas,, or when is version 9 due to be released @frankcalise |
@LeeRaybone you can jump on it now with |
Thanks for save my hours. Worked for me. |
Describe the bug
Hello,
First of all, thank you for your work! Ignite is awesome!
I tried to preview the newest Ignite version and see what changed with the introduction of RN 0.71. I managed to release a test app on iOS, but I couldn't do the same with Android. The app runs perfectly on the emulator (npm run android), but when I run:
and try to run it on either a physical device or by dragging an APK on the emulator window, the app installs correctly and the splash screen shows up, but then it crashes immediately.
Steps to reproduce:
I noticed that during the building of an APK file, two warnings were displayed:
And then, I saw the same warnings with :react-native-screens and :react-native-gesture-handler. I found a comment on the RNGH repo suggesting that adding this line to app/build.gradle might help:
software-mansion/react-native-gesture-handler#2307 (comment)
However, it didn't help in my case.
Has anyone encountered similiar problem? I would highly appreciate any help :)
Ignite version
8.8.0
Additional info
System
platform darwin
arch arm64
cpu 10 cores Apple M1 Pro
directory Erko /Users/balhut/Developer/new-repo/clear/Erko
JavaScript (and globally-installed packages)
node 18.15.0 /Users/balhut/.nvm/versions/node/v18.15.0/bin/node
npm 9.6.6 /Users/balhut/.nvm/versions/node/v18.15.0/bin/npm
corepack 0.15.3
ios-deploy 1.12.2
npm 9.6.6
yarn - not installed
pnpm - not installed
expo 48.0.15 managed
Ignite
ignite-cli 8.8.0 /Users/balhut/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src build /Users/balhut/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build
Android
java 11.0.19 /usr/bin/java
android home - undefined
iOS
xcode 14.3
cocoapods 1.12.1 /Users/balhut/.rbenv/shims/pod
Tools
git git version 2.40.1 /opt/homebrew/bin/git
The text was updated successfully, but these errors were encountered: