-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
npx react-native init AwesomeProject #32927
Labels
Needs: Triage 🔍
Platform: Linux
Building on Linux.
Resolution: Locked
This issue was locked by the bot.
Comments
The test phone is Redmi Note 8 Pro |
Can I ask you to clarify what "flash back" means in this context? |
I can confirm that this issue is reproducible on a fresh project - there's also another issue opened about this that has a few more insights. So let's move the conversation there: #32928 |
cortinico
added a commit
to cortinico/react-native
that referenced
this issue
Jan 20, 2022
Summary: As the title says, we dont' want to remove `libjscexecutor.so` when baking release builds and having JSC enable as this leads to instacrashes. Fixes facebook#32928 Fixes facebook#32927 Changelog: [Android] [Fixed] - Do not remove libjscexecutor.so from release builds Differential Revision: D33681932 fbshipit-source-id: 4a71fd6cfaae35a1f24f048648e32d78d573a457
facebook-github-bot
pushed a commit
that referenced
this issue
Jan 20, 2022
Summary: Pull Request resolved: #32932 As the title says, we dont' want to remove `libjscexecutor.so` when baking release builds and having JSC enable as this leads to instacrashes. Fixes #32928 Fixes #32927 Changelog: [Android] [Fixed] - Do not remove libjscexecutor.so from release builds Reviewed By: ShikaSD Differential Revision: D33681932 fbshipit-source-id: 5b59fd1fb76c80c191198d65c916bbbd9232c75b
lunaleaps
pushed a commit
that referenced
this issue
Jan 20, 2022
Summary: Pull Request resolved: #32932 As the title says, we dont' want to remove `libjscexecutor.so` when baking release builds and having JSC enable as this leads to instacrashes. Fixes #32928 Fixes #32927 Changelog: [Android] [Fixed] - Do not remove libjscexecutor.so from release builds Reviewed By: ShikaSD Differential Revision: D33681932 fbshipit-source-id: 5b59fd1fb76c80c191198d65c916bbbd9232c75b
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Needs: Triage 🔍
Platform: Linux
Building on Linux.
Resolution: Locked
This issue was locked by the bot.
Description
Debugging in development mode is normal. After packaging, the installation and startup flash back.
Update from 0.66.4 to 0.67.0 had the same problem.
Version
0.67.0
Output of
npx react-native info
System:
OS: Linux 4.15 Ubuntu 16.04.7 LTS (Xenial Xerus)
CPU: (4) x64 Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz
Memory: 1.30 GB / 7.70 GB
Shell: 4.3.48 - /bin/bash
Binaries:
Node: 12.22.7 - ~/.nvm/versions/node/v12.22.7/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v12.22.7/bin/yarn
npm: 8.3.0 - ~/.nvm/versions/node/v12.22.7/bin/npm
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 28, 29, 30, 31
Build Tools: 23.0.1, 27.0.3, 28.0.3, 29.0.2, 30.0.2, 31.0.0
System Images: android-29 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 1.8.0_201 - /home/lzhd/software/jdk1.8.0_201/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.0 => 0.67.0
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
After the package is successfully installed, the application starts to flash back.
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: