OS Version: Android 13 (TP1A.220624.014.T575XXU6EWH4)
Report Version: 104
Exception Type: Unknown (SIGSEGV)
Application Specific Information:
Segfault
Thread 0 Crashed:
0 split_config.arm64_v8a.apk 0x71b20fed44 + 488318692676
1 split_config.arm64_v8a.apk 0x71b21093e8 + 488318735336
2 split_config.arm64_v8a.apk 0x71b2109360 + 488318735200
3 split_config.arm64_v8a.apk 0x71b20b7324 + 488318399268
4 split_config.arm64_v8a.apk 0x71b20b60a0 c4socket_gotHTTPResponse
5 split_config.arm64_v8a.apk 0x71c5ade1f8 Java_com_couchbase_lite_internal_core_impl_NativeC4Socket_gotHTTPResponse
6 base.odex 0x71d49a8d18 + 488898202904
Well… not unless you give us a few clues.
- Are you using a Couchbase product? Which one? What version?
- What kind of hardware are you running on?
- Do you have logs to show us?
Sure @blake.meike.
Couchbase version: couchhbase lite 3.1 with addiing following dependency implementation “com.couchbase.lite:couchbase-lite-android:3.1.0”
Hardware:Galaxy Tab Active3 (Android 13 version).
In one of our error monitoring sites the above lines of log getting printed.
Terrific! That’s a great start!
Now we need some logs.
That bit of stack trace in the OP is not going to be very useful in finding an issue. As you can see from the offsets (+ 488898202904) the problem could be just about anywhere.
Are you using Crashlytics or some other tool so that you can get a bit more information? Can you reproduce this in the lab?
This topic was automatically closed after 11 days. New replies are no longer allowed.