cortinico
commented
1 year ago Is this happening on a blank app? Are you able to reproduce it consistently in any form?
Closed ugurdalkiran closed 1 year ago
cortinico
commented
1 year ago Is this happening on a blank app? Are you able to reproduce it consistently in any form?
ugurdalkiran
commented
1 year ago What is an empty app?
It's actually empty. :) It's a very simple app with just the reanimated package installed and consisting of View and Text components.
cortinico
commented
1 year ago It's actually empty. :) It's a very simple app with just the reanimated package installed and consisting of View and Text components.
Is it crashing also if you remove reanimated? If so, that's a RN issue and we should look into it. If not, we should move this issue to: https://github.com/software-mansion/react-native-reanimated/issues
ugurdalkiran
commented
1 year ago As a result, it cannot find the "RCTText" component, which is a component of the RN.
cortinico
commented
1 year ago As a result, it cannot find the "RCTText" component, which is a component of the RN.
What do you mean with "As a result"?
Could you answer my questions:
Is it crashing also if you remove reanimated? If so, that's a RN issue and we should look into it. If not, we should move this issue to: software-mansion/react-native-reanimated/issues
ugurdalkiran
commented
1 year ago Hi.
I created a clean application (0.70.6) and did not add any packages. In this state, there is no problem when I create a release APK and try it. 🎉
Even if I add a reanimated or just react-native-svg package, that is, add 1 package and use it inside, the release APK sometimes crashes when opening.
cortinico
commented
1 year ago Thanks for the follow up @ugurdalkiran
Even if I add a reanimated or just react-native-svg package, that is, add 1 package and use it inside, the release APK sometimes crashes when opening.
Can you try to create a new package with create-react-native-library:
https://github.com/callstack/react-native-builder-bob/blob/main/README.md
And verify if the app crashes?
tangzonglin
commented
1 year ago @ugurdalkiran hi, how did you solve it ?
Sunbreak
commented
1 year ago Fixed by #35770
We could reproduce it in our APP and find the root cause is concurrency of ReactInstanceManager#getOrCreateManager() between CoreModulesPackage#createUIManager() and Fabric's JSIModuleSpec#getJSIModuleProvider()
Description
[New Architecture] [Fabric] [Android] [Crash]
I can develop my application without any problem in development mode. There is no problem at startup. Everything is perfect.
But when I get the release APK and test it, my application sometimes opens without any problems. I can view my View and Text components within the application.
Sometimes, when I click on the application icon, my application suddenly crashes. 😟
Info: Since my development environment is on Windows, I am operating on the "Visual Studio 2022 Developer Command Prompt v17.4.1" terminal. To keep the application path short, I create the application folder as "C:/a07061".
Info: Although it says "newArchEnabled=false" in android/gradle.properties, I can see {fabric: true} in development mode. (This is how it comes in the default react-native install.)
I have shared the log information about this crash and the video of the event below.
Application package name: com.a07061
List of packages installed in my app:
App.js content, which is the app first screen.
Video:
https://user-images.githubusercontent.com/27302986/203388374-67a7efdb-819c-4072-8d19-d9a721aa08d5.mp4
Log:
We can focus on the "-------- beginning of crash" part where the crash occurred in the log section. I add that maybe it is important before.
The important point I see in the log is:
Sometimes at the point I run the application it cannot find the View or Text components and the application does not open. :(
Version
0.70.6
Output of
npx react-native infoC:\a07061>npx react-native info
Steps to reproduce
...
Snack, code example, screenshot, or link to a repository
...