0.62-RC: Release version instacrash on Android #28163
Labels
Comments
hramos
added
Impact: RC
Platform: Android
|
Thanks for the report. We're currently tracking this as one of the known issues for the 0.62 RC in react-native-community/releases#157 |
hramos
changed the title
6 tasks
|
It looks like this issue is still being reported up to RC5, but seems that
from @owinter86 may be the solution. |
|
Have you been able to build this project with 0.61.5, i.e. is the problem introduced in 0.62? |
|
@alloy Yes 0.61.5 was working fine for me. Removing the iml-files and invalidating cache did not fix it. |
|
Invalidating the caches solved the issue on my end, deleting the build folder was not enough in these cases. This was a direct upgrade from 61.5, to RRC.3 and RC.5. Both hermes enabled and disabled work, both on my machine and external CI. My config is slightly different to the RN init, due to various third party packages, I have dumped my info below, it may help others debug their issues. I am happy to add anything else if people need to compare. app/build.gradle gradle.properties |
|
My issue seems to be unrelated to this one. |
|
Not sure if it helps, but I've experienced a similar crash when bumping from It seems to crash around Flipper with the following log Here is the full adb log of it below. |
|
@Naturalclar I had the same crash after the same update. However, after running |
|
I'm experiencing the same crash after generating a fresh app via So yeah I don't really understand what's going on... since I don't have any pre-existing cache. Error log:Error log: That said, if I open the project from Android Studio and build it from there, it works just fine... 😅 |
|
@kelset I’m new to Android/Java, but judging from your crash log it’s a different one from e.g. @Naturalclar. Yours appears to be about a lib being built for a different arch than the one you’re trying to run it on, whereas @Naturalclar’s appears to be about the loader not being able to find the lib in the first place. |
|
@bmbmjmdm Can you update this issue with the results of removing all build/cache artefacts? |
|
Tried invalidating cache via Android Studio, deleting all .iml files in ./android, ./android/app and ./android/.ide, deleting android/app/build files and ran a clean+build in Android Studio. Reran then this repeated a bunch |
|
Being naive about Android builds, I’d venture to say it appears to be a pure JS issue. Can you try to find the call-site that leads to the exception and the code/libs involved? Even better would be a fresh sample app that has just the code to demonstrate the exception. |
|
Btw, I see I didn’t mention this before, but @Naturalclar’s crash log is very different from @bmbmjmdm’s. @Naturalclar’s looks more similar to #28270, in that a lib can’t be found. |
|
@alloy I can't say I fully understand that request, so I probably wouldn't be able to find that on my own |
|
Yes, @Naturalclar issue seems similar to #28270, in that key libs (libjscexecutor.so, libfbjni.so) wasn't able to loaded. For @bmbmjmdm's issue, could the issue perhaps be related to Vue Native? |
Let me rephrase; in short I’m asking you to try to isolate the code in your application to the code that triggers this exception. I.e. start removing large parts of your codebase until the exception no longer occurs, which means the code you removed may contain the cause, then further dissect that code. Does that clarify things? |
I don't know a lot about Vue Native either but apparently it somehow transpiles Vue code to React Native, and so there could possibly be some incompatibility issues that happened in 0.62.0. |
I experienced that with clean project on |
|
Make sure to clear the android caches. If that doesn't help check for
differences between the freshly gradle file and the one the updated project.
…On Thu, Mar 19, 2020 at 9:51 PM Victor Malov ***@***.***> wrote:
Not sure if it helps, but I've experienced a similar crash when bumping
from 0.62.rc-2 to 0.62.rc-5
The crash didn't happen if I create a new project in 0.62.rc-5 from npx
react-native init
It seems to crash around Flipper with the following log
--------- beginning of crash
03-09 23:17:15.919 8757 8785 E AndroidRuntime: FATAL EXCEPTION: FlipperConnectionThread
03-09 23:17:15.919 8757 8785 E AndroidRuntime: Process: com.rn062, PID: 8757
03-09 23:17:15.919 8757 8785 E AndroidRuntime: java.lang.NoClassDefFoundError: <clinit> failed for class com.facebook.flipper.android.EventBase; see exception in other thread
03-09 23:17:15.919 8757 8785 E AndroidRuntime: at com.facebook.flipper.android.FlipperThread.run(FlipperThread.java:25)
03-09 23:17:15.920 8757 8784 E AndroidRuntime: FATAL EXCEPTION: FlipperEventBaseThread
03-09 23:17:15.920 8757 8784 E AndroidRuntime: Process: com.rn062, PID: 8757
03-09 23:17:15.920 8757 8784 E AndroidRuntime: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libfbjni.so
03-09 23:17:15.920 8757 8784 E AndroidRuntime: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:789)
03-09 23:17:15.920 8757 8784 E AndroidRuntime: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
03-09 23:17:15.920 8757 8784 E AndroidRuntime: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
03-09 23:17:15.920 8757 8784 E AndroidRuntime: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:525)
03-09 23:17:15.920 8757 8784 E AndroidRuntime: at com.facebook.soloader.NativeLoaderToSoLoaderDelegate.loadLibrary(NativeLoaderToSoLoaderDelegate.java:24)
03-09 23:17:15.920 8757 8784 E AndroidRuntime: at com.facebook.soloader.nativeloader.NativeLoader.loadLibrary(NativeLoader.java:43)
03-09 23:17:15.920 8757 8784 E AndroidRuntime: at com.facebook.jni.HybridData.<clinit>(HybridData.java:34)
03-09 23:17:15.920 8757 8784 E AndroidRuntime: at com.facebook.flipper.android.FlipperThread.run(FlipperThread.java:25)
03-09 23:17:15.920 8757 8784 I Process : Sending signal. PID: 8757 SIG: 9
Here is the full adb log of it below.
I experienced that with clean project on RC.5 version.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#28163 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN4NBEWI4JQTOGJNSPKW6LRIKHUXANCNFSM4KZ6P5PQ>
.
|
|
@likern As mentioned earlier, the crash log that mentions the linker being unable to find libraries looks more like #28270 |
|
Whoops, got stuck with this issue and wasted a lot of time. I found the fix for this. Thanks to @jaythummar95, he told me run the following command: Run
That should probably fix this. |
|
Just posting to say I still need to look at this more; issue is not stale, life is just hectic |
|
Update: I have put down Android for a while to focus on iOS. Upon building a release build in iOS, I see the same error there! (Note: debug build runs fine for both operating systems) Therefore this is not a problem with Android Studio or cache, I believe |
|
Can rule out bundle minify as the cause (I disabled minify for release and still got it). Today I'll be setting up a fresh project and adding all dependencies one by one to see if those are causing it. Any help would be appreciated, been working on this project for so long and now I can't release for either platform :/ |
|
Are you able to attach a JS debugger to the app? I wonder if you would be able to set a breakpoint in one of those stack trace frames you reported (or perhaps just on any uncaught exception?) and then traverse the call stack to see if you can identify potential call sites that trigger the presumably recursive code. |
|
Just double checking, still having a Flipper error on an old RC build? In that case I'd recommend to go to stable version first, so that we are talking about the same reference point. At least my memory won't be able to recall what issues might or might not exist in rc builds ;) |
|
Hi thanks for the replies. After far too much debugging, it looks like this is a problem with the vuex store interacting with react-native animations. See GeekyAnts/vue-native-core#263 for details |
|
I'm going to confirm this issue is addressed in GeekyAnts/vue-native-core#118 and if so, I'll close it |
|
Confirmed this is fixed by Thanks everyone for the help! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Overview
I am able to run my app perfectly fine with
react-native run-androidafter creating a dev bundle.However when I try to run
react-native run-android --variant=releaseafter creating a release bundle, the app crashes immediately when started.Bundle command being used for release:
react-native bundle --platform android --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundleReact Native version:
System:
OS: Windows 10 10.0.18362
CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
Memory: 7.01 GB / 15.93 GB
Binaries:
Node: 10.16.2 - C:\Program Files\nodejs\node.EXE
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.4.0.0 AI-183.6156.11.34.5692245
npmPackages:
react: 16.11.0 => 16.11.0
react-native: 0.62.0-rc.1 => 0.62.0-rc.1
Package.json
Logs
When I build release bundle and deploy it, then the app installs and crashes immediately with the following logs:
ReactNativeJS ▶︎ RangeError: Maximum call stack size exceeded.has a stack trace ofThe text was updated successfully, but these errors were encountered: