🔥[🐛] android crash reports SIGSEGV with missing build id #8433
Labels
blocked: react-native
Issue or PR blocked by a React Native issue or change.
Needs Attention
platform: android
plugin: crashlytics
Firebase Crashlytics
type: bug
New bug report
Comments
mikehardy
changed the title
|
Hey there, It does not seem that you are using the latest version, can you please upgrade it and try again? From what I remember we very recently did some react native version upgrades. I have also come across this recently: facebook/react-native#48788 I would encourage you to check it out and see if anything helps there. Could also try disabling hermes and seeing if it is an issue related to hermes? I doubt that it is related to Crashlytics so far from what I see. |
|
hello thanks for your quick reply. i update firebase to the latest version hermes enabled:
hermes disabled:
below is the adb logcat crash equivalent to the above firebase crash report. adb logcat for the crash hermes enabled: adb logcat for the crash hermes disabled: |
|
Hi there, thank you for upgrading your firebase trying the suggestions. Now may I ask when does this crash occur? Are you able to provide a repro for this so I can investigate further? |
|
the crash is a little bit tricky, we use a ble scanning library in our production app, and after upgrading RN version to the new architecture we started seeing this crash on specific devices. i opened an issue at the library, but i wasn't convinced that it is a library issue since the crash only happens on certain device and a code generated by codegen, so i also opened an issue at RN. i did further investigation and created a simple calculator turbo module that use event emitter by following this guide turbo modules and the crash only happens when i apply the event emitter and run i created a repro using the ble library when opening the issue at RN. Would it help if i create a repro for you with the calculator turbo module, knowing that it needs a specific device for the crash to happen? i do not know if it is a java version, node version or npm version that is causing this issue |
|
Hmm, I do not personally posses an A13 but I do have an S21. I believe the resolution to this is what will hopefully be given to you on your other ticket you made as it is definitely not a Crashlytics issue as a test crash did produce the logs you wanted and this issue is known on React Native. |
MichaelVerdon
added
the
blocked: react-native
|
I just scanned through everything because it looked kind of interesting. I left you a comment on the react-native issue @barakataboujreich - I think that's the natural home for this one. Do the best you can to make a reproducer that has minimal changes from the template reproducer, and a single button to crash. If it requires Android Go perhaps you can specify an Android Emulator (including image) that is able to reproduce it (I believe you can get Android Go emulators set up?) I don't think there are any actions here though |
|
@mikehardy thank you for your suggestions and taking the time to scan through the issue. i provided a reproducer using the ble scanning library to RN maintainers, but they couldn't do much with it since it is crashing on a device that they do not own... i will try to make a reproducer with one button crash using the template provided by react native. the crash reports i am getting through firebase are on android 11+ for the samsung a13, and the a13 5G that comes in different RAM versions lowest is 4GB and i do not think runs on android go. But i will try to setup an emulator with android go and see if the same crash happens, so we can have a ground to start on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue
with RN 0.78 on android we started receiving crash logs SIGSEGV with missing build id like the following
but if i cause the crash with
crashlytics().crash()we receive a proper crash logi don't know if i am doing something wrong, or i missed something in the setup
i tried to add to build.gradle
and then tried this path since under
build/intermediates/merged_native_libs/release/there was no out folder, it is under a subfoldermergeReleaseNativeLibsbut there was not much difference with the reportluckily we were able to replicate the crash on some devices and it happens in the spec file generated by codegen in event emitter handlers
Project Files
Javascript
Click To Expand
package.json:{ "name": "BleTest", "version": "0.0.1", "private": true, "scripts": { "android": "react-native run-android", "ios": "react-native run-ios", "lint": "eslint .", "start": "react-native start", "test": "jest" }, "codegenConfig": { "name": "NativeCalculatorSpec", "type": "modules", "jsSrcsDir": "specs", "android": { "javaPackageName": "com.nativecalculator" } }, "dependencies": { "@react-native-firebase/app": "^21.11.0", "@react-native-firebase/crashlytics": "^21.11.0", "react": "19.0.0", "react-native": "0.78.1" }, "devDependencies": { "@babel/core": "^7.25.2", "@babel/preset-env": "^7.25.3", "@babel/runtime": "^7.25.0", "@react-native-community/cli": "15.0.1", "@react-native-community/cli-platform-android": "15.0.1", "@react-native-community/cli-platform-ios": "15.0.1", "@react-native/babel-preset": "0.78.1", "@react-native/eslint-config": "0.78.1", "@react-native/metro-config": "0.78.1", "@react-native/typescript-config": "0.78.1", "@types/jest": "^29.5.13", "@types/react": "^19.0.0", "@types/react-test-renderer": "^19.0.0", "eslint": "^8.19.0", "jest": "^29.6.3", "prettier": "2.8.8", "react-test-renderer": "19.0.0", "typescript": "5.0.4" }, "engines": { "node": ">=18" } }firebase.jsonfor react-native-firebase v6:# N/AiOS
Click To Expand
ios/Podfile:# N/AAppDelegate.m:// N/AAndroid
Click To Expand
Have you converted to AndroidX?
android/gradle.settingsjetifier=truefor Android compatibility?jetifierfor react-native compatibility?android/build.gradle:buildscript { ext { buildToolsVersion = "35.0.0" minSdkVersion = 24 compileSdkVersion = 35 targetSdkVersion = 35 ndkVersion = "27.1.12297006" kotlinVersion = "2.0.21" } repositories { google() mavenCentral() } dependencies { classpath("com.android.tools.build:gradle") classpath("com.facebook.react:react-native-gradle-plugin") classpath("org.jetbrains.kotlin:kotlin-gradle-plugin") classpath 'com.google.gms:google-services:4.4.2' classpath 'com.google.firebase:firebase-crashlytics-gradle:3.0.3' } } apply plugin: "com.facebook.react.rootproject"android/app/build.gradle:android/settings.gradle:pluginManagement { includeBuild("../node_modules/@react-native/gradle-plugin") } plugins { id("com.facebook.react.settings") } extensions.configure(com.facebook.react.ReactSettingsExtension){ ex -> ex.autolinkLibrariesFromCommand() } rootProject.name = 'BleTest' include ':app' includeBuild('../node_modules/@react-native/gradle-plugin')MainApplication.java:AndroidManifest.xml:Environment
Click To Expand
react-native infooutput:react-native-firebaseversion you're using that has this issue:21.11.0Firebasemodule(s) you're using that has the issue:crashlyticsTypeScript?Y&5.0.4React Native FirebaseandInvertaseon Twitter for updates on the library.The text was updated successfully, but these errors were encountered: