[BUG] Firebase SIGABRT error

[GeminiR]

OpenIM SDK Version

io.openim:android-sdk:3.8.3

OpenIM Server Version

No response

SDK Platform

Android SDK

Device Model

Honor X9c、Honor X9b 5G、 Galaxy A24、 Galaxy A16、 Transsion - FIH Foxconn

Operating System Version

Android 12-15

Bug Description and Steps to Reproduce

com.scm.app.deliveryapp_issue_d413bb414403860da9162f05e51dfad2_crash_session_690f7d2c000100017013ee1442f9c797_DNE_0_v2_stacktrace.txt

com.scm.app.deliveryapp_issue_d413bb414403860da9162f05e51dfad2_crash_session_6912dd0f00ee00014b9ffc090a7b24e0_DNE_0_v2_stacktrace.txt

com.scm.app.deliveryapp_issue_d413bb414403860da9162f05e51dfad2_crash_session_6912f85c010300012965e7f207c21199_DNE_0_v2_stacktrace.txt

com.scm.app.deliveryapp_issue_d413bb414403860da9162f05e51dfad2_crash_session_69119e73010b000134b286521af9ff35_DNE_0_v2_stacktrace.txt

com.scm.app.deliveryapp_issue_d413bb414403860da9162f05e51dfad2_crash_session_691231f201900001456f54cb552f83a7_DNE_0_v2_stacktrace.txt

We have encountered a significant number of SIGABRT crashes in production after integrating the OpenIM Android SDK.
These crashes occur across multiple device models and Android versions.

Unfortunately, the crash reports collected by Firebase Crashlytics are missing detailed native stack traces (no symbol information),
so we’re currently unable to pinpoint the exact cause of the issue.
I’ve attached a sample crash log file for your reference.

Could the OpenIM team please provide a debug/symbolized version of libgojni.so or the corresponding symbol file (e.g. .dbg, .sym, etc.)?
This would allow us to upload the symbols to Firebase and fully decode the crash traces to identify the root cause.

If it’s not possible to share the symbol files, could you please suggest any alternative ways to investigate or locate the source of these native crashes?

Thank you very much for your assistance.

Screenshots Link

No response

[FGadvancer]

---

Hello, based on the information you provided, we believe this crash may be caused by the AAR package.
First, please make sure your android-sdk version is 3.8.3 (corresponding to the 3.8.3 tag of the repository), and not another patched version.

If you need the AAR package to retain more debugging information, you can try modifying the Makefile in the corresponding tag.
Replace:

GOARCH=amd64 gomobile bind -v -trimpath -ldflags="-s -w" -o ./open_im_sdk.aar -target=android ./open_im_sdk/ ./open_im_sdk_callback/

with:

GOARCH=amd64 gomobile bind -v -trimpath -o ./open_im_sdk.aar -target=android ./open_im_sdk/ ./open_im_sdk_callback/

Then rebuild the AAR package. (You can find detailed build instructions in the README.)
By doing this, the AAR will keep the related debug symbols, allowing you to locate the exact logic that triggers the crash.

Additionally, we’d like to understand under what conditions this crash occurs.
Is there any special operation or scenario where the crash can be reproduced consistently?

---

[GeminiR]

Hello, based on the information you provided, we believe this crash may be caused by the AAR package. First, please make sure your android-sdk version is 3.8.3 (corresponding to the 3.8.3 tag of the repository), and not another patched version.

If you need the AAR package to retain more debugging information, you can try modifying the Makefile in the corresponding tag. Replace:

GOARCH=amd64 gomobile bind -v -trimpath -ldflags="-s -w" -o ./open_im_sdk.aar -target=android ./open_im_sdk/ ./open_im_sdk_callback/
with:

GOARCH=amd64 gomobile bind -v -trimpath -o ./open_im_sdk.aar -target=android ./open_im_sdk/ ./open_im_sdk_callback/
Then rebuild the AAR package. (You can find detailed build instructions in the README.) By doing this, the AAR will keep the related debug symbols, allowing you to locate the exact logic that triggers the crash.

Additionally, we’d like to understand under what conditions this crash occurs. Is there any special operation or scenario where the crash can be reproduced consistently?

I am currently using the SDK through Gradle dependencies, not a locally imported AAR.

implementation 'io.openim:android-sdk:3.8.3'
implementation 'io.openim:core-sdk:3.8.3'

My understanding is that you are suggesting I check out the 3.8.3 tag from the repository and rebuild the AAR myself using the command you provided, so that the generated AAR will contain full debug symbols.
This should allow me to obtain complete stack traces when the crash happens.
Is my understanding correct?

At the moment, we do not have a stable reproduction scenario.
However, Firebase has reported this crash multiple times, which is quite strange.
If we manage to reproduce it locally, we will share the details with you immediately.

[GeminiR]

Hello, based on the information you provided, we believe this crash may be caused by the AAR package. First, please make sure your android-sdk version is 3.8.3 (corresponding to the 3.8.3 tag of the repository), and not another patched version.

If you need the AAR package to retain more debugging information, you can try modifying the Makefile in the corresponding tag. Replace:

GOARCH=amd64 gomobile bind -v -trimpath -ldflags="-s -w" -o ./open_im_sdk.aar -target=android ./open_im_sdk/ ./open_im_sdk_callback/
with:

GOARCH=amd64 gomobile bind -v -trimpath -o ./open_im_sdk.aar -target=android ./open_im_sdk/ ./open_im_sdk_callback/
Then rebuild the AAR package. (You can find detailed build instructions in the README.) By doing this, the AAR will keep the related debug symbols, allowing you to locate the exact logic that triggers the crash.

Additionally, we’d like to understand under what conditions this crash occurs. Is there any special operation or scenario where the crash can be reproduced consistently?

Is it sufficient to replace the dependency implementation 'io.openim:core-sdk:3.8.3' with the compiled artifact open_im_sdk.aar while keeping implementation 'io.openim:android-sdk:3.8.3'? So far, the tests seem to work without issues.

[FGadvancer]

After replacing it with the debug-enabled version, are you still able to reproduce the panic information?

[GeminiR]

After replacing it with the debug-enabled version, are you still able to reproduce the panic information?

Sorry for the late reply. Recently, due to special circumstances at the company, we are not allowed to release versions. I have temporarily replaced the io.openim:android-sdk:3.8.3 dependency with the compiled open_im_sdk.aar. So far, the issue hasn't reoccurred. I plan to release a grayscale version next week to monitor if the issue reappears in the live environment.