Skip to content
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 crashes on some samsung devices (5.1.1+) #7087

Closed
melihmucuk opened this issue Apr 20, 2016 · 4 comments
Closed

Android crashes on some samsung devices (5.1.1+) #7087

melihmucuk opened this issue Apr 20, 2016 · 4 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@melihmucuk
Copy link
Contributor

I build an android app and publish on google play, some samsung devices with android 5.1.1+ crash on app start. What is problem with it ? I'm on react-native v0.21.0. I tested with genymotion (4.4.4, 5.1 and 6.0) and I can't notice any issue. I haven't real device for debugging.

Here is my build.gradle:

compileSdkVersion 23
    buildToolsVersion "23.0.1"

    defaultConfig {
        applicationId "com.mobilevo.bikargo"
        minSdkVersion 16
        targetSdkVersion 22
        versionCode 3
        versionName "1.0.2"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }

here is my anr reports from google play developer console:


Build fingerprint: 'samsung/a8hpltedx/a8hplte:5.1.1/LMY47X/A800IXXU1AOJ1:user/release-keys'
Revision: '1'
ABI: 'arm'
pid: 20003, tid: 20037, name: mqt_js >>> com.mobilevo.bikargo <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x4604b088
r0 00000000 r1 00000000 r2 e2ab63e5 r3 e2ab63e5
r4 9e2fdd10 r5 b3e15d34 r6 0000000b r7 4604b089
r8 b3e15850 r9 ae45b2d0 sl ae42f820 fp 9de78754
ip 9e2fde34 sp 9de78730 lr 9dff6f54 pc 4604b088 cpsr 600d0030

backtrace:
#00 pc 1344a088 /dev/ashmem/dalvik-main space (deleted)
#1 pc 0017df50 /data/app/com.mobilevo.bikargo-1/lib/arm/librealmreact.so
#2 pc 00016bf7 /data/app/com.mobilevo.bikargo-1/lib/arm/libreactnativejni.so (facebook::react::JSCExecutor::JSCExecutor(facebook::react::Bridge_, std::string const&)+198)
#3 pc 00016d59 /data/app/com.mobilevo.bikargo-1/lib/arm/libreactnativejni.so (facebook::react::JSCExecutorFactory::createJSExecutor(facebook::react::Bridge_)+20)
#4 pc 0001369d /data/app/com.mobilevo.bikargo-1/lib/arm/libreactnativejni.so
#5 pc 00015b49 /data/app/com.mobilevo.bikargo-1/lib/arm/libreactnativejni.so (facebook::react::Bridge::Bridge(facebook::react::JSExecutorFactory*, std::function<void (std::vector<facebook::react::MethodCall, std::allocatorfacebook::react::MethodCall >, bool)>)+144)
#6 pc 0001079f /data/app/com.mobilevo.bikargo-1/lib/arm/libreactnativejni.so
#7 pc 002dd505 /data/dalvik-cache/arm/data@[email protected]@[email protected]

@fikisipi
Copy link

fikisipi commented Apr 20, 2016

The crash corresponds to a Samsung Galaxy A8 which has 64bit ARM-v8 CPU. Genymotion has a different ABI which is why you don't get any crash. (RISC vs CISC)

A common problem with RN Android was that the native library wasn't generated for all ABIs and you can see more details at #2814. However your trace corresponds to a correctly loaded library which segfaulted during bridge code.

I think you will need to provide a bigger trace and possibly try to reproduce this issue with JNI / NDK debugger.

@satya164
Copy link
Contributor

satya164 commented Apr 20, 2016

What other libraries are you using? #1 pc 0017df50 /data/app/com.mobilevo.bikargo-1/lib/arm/librealmreact.so suggests that Realm has something to do with it.

@appden
Copy link
Contributor

appden commented Apr 22, 2016

We're pretty sure this is an issue with Realm, and since @melihmucuk filed a corresponding issue with us, I think this can be closed here.

@liuzhiqin
Copy link

how to slove this problem

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

6 participants