[Android, IOS] - Android crash app, IOS throw error and not response

[iamhayate]

Describe the bug - Android
2
E/rtc (29944):
E/rtc (29944): #
E/rtc (29944): # Fatal error in: gen/jni_headers/sdk/android/generated_metrics_jni/../../../../../../../../../../../_source/android/webrtc/src/sdk/android/src/jni/jni_generator_helper.h, line 95
E/rtc (29944): # last system error: 0
E/rtc (29944): # Check failed: !env->ExceptionCheck()
E/rtc (29944): #
F/libc (29944): Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 29944 (es.myhome.owner), pid 29944 (es.myhome.owner)

---

Build fingerprint: 'xiaomi/violet/violet:10/QKQ1.190915.002/V12.5.1.0.QFHINXM:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2024-05-31 14:44:35+0700
pid: 29944, tid: 29944, name: es.myhome.owner >>> com.vjtechnologies.myhome.owner <<<
uid: 11085
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
x0 0000000000000000 x1 00000000000074f8 x2 0000000000000006 x3 0000007ffb099da0
x4 fefeff749c489f1f x5 fefeff749c489f1f x6 fefeff749c489f1f x7 7f7f7f7fff7fff7f
x8 00000000000000f0 x9 213efabf11f8ef89 x10 0000000000000001 x11 0000000000000000
x12 fffffff0fffffbdf x13 ffffffffffffffff x14 0000000000000004 x15 ffffffffffffffff
x16 000000759aa8c8c0 x17 000000759aa68900 x18 000000759e14a000 x19 00000000000074f8
x20 00000000000074f8 x21 00000000ffffffff x22 000000747c073d63 x23 aaaaaaaaaaaaaaaa
x24 0000000000000010 x25 000000759d49a020 x26 000000759d2e50b0 x27 0000000000000004
x28 0000007ffb09a140 x29 0000007ffb099e40
sp 0000007ffb099d80 lr 000000759aa1a0c4 pc 000000759aa1a0f0
backtrace:
#00 pc 00000000000830f0 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: 328a3518945f3e056fc055f1eea1cc35)
#1 pc 000000000041e68c /data/app/****************-p1hMWu_D2ZHlmjQFTOQOIg==/base.apk!libjingle_peerconnection_so.so (offset 0x3f26000) (BuildId: 3aead2fcb82aad0b)
Lost connection to device.

Exited.
Describe the bug - IOS
Throw error Thread 1: "-[NSNull stdString]: unrecognized selector sent to instance 0x20734c250" and not response on app

[bernardolansing]

For what it seems, this kind of error may happen for a number of reasons. It was happening to me too, and the solution was pointed out by this comment. For me, another error message showed up a little earlier and gave me more clues about what was wrong.