[split_config.arm64_v8a.apk!libfilament-jni.so] utils::TPanic<utils::PostconditionPanic>::panic(char const*, char const*, int, char const*, std::__ndk1::basic_string<char, std::__ndk1::char_traits<char>, std::__ndk1::allocator<char>>)

[sanchit-cars24]

Android app faces crash and I got "[split_config.arm64_v8a.apk!libfilament-jni.so] utils::TPanicutils::PostconditionPanic::panic(char const*, char const*, int, char const*, std::__ndk1::basic_string<char, std::__ndk1::char_traits, std::__ndk1::allocator>)" from logs. It crashes in android 15 and also below versions

To Reproduce
Steps to reproduce the behavior:

1. This is random (no evidance so far to mention specific steps)

Expected behavior
I expected crash not to happen
If crash happens then it should give more details in log to know what causes this error

Screenshots
NA

Logs
[split_config.arm64_v8a.apk!libfilament-jni.so] utils::TPanicutils::PostconditionPanic::panic(char const*, char const*, int, char const*, std::__ndk1::basic_string<char, std::__ndk1::char_traits, std::__ndk1::allocator>)

Desktop (please complete the following information):

• OS: Android

Smartphone (please complete the following information):

• Device: [Redmi Redmi Note 13 Pro 5G]
• OS: [e.g. Android 15.0 and lowers other devices

[z3moon]

Thanks for the report. But we need more information. Can you grab a stack trace? if not, what was the app performing during the crash?

[sanchit-cars24]

When we launch app, after the splash screen disappear, we see few APIs(15-16) including analytics , app config , user data and server images in the logs after these api calls it suddenly crashes with this reason, it is completely random , there is no specific api after which it occurs and no as such no of api calls.

• For some users it happens after 2-3 min usage of app
• play store stack trace only gives
  -*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

backtrace:
#00 pc 0x000000000005d7d8 /apex/com.android.runtime/lib64/bionic/libc.so (abort+172)
#1 pc 0x0000000000208ed0 /data/app/~~ChJ80nkIL1ftHPMpNF0_lw==/com.cars24.seller-UevTs3kxBKAJDppzkqfSRQ==/split_config.arm64_v8a.apk!libfilament-jni.so (utils::TPanicutils::PostconditionPanic::panic(char const*, char const*, int, char const*, std::__ndk1::basic_string<char, std::__ndk1::char_traits, std::__ndk1::allocator>)+176) (BuildId: ceaf9975a78e78741916cf751bb5102eca427e98)

[sanchit-cars24]

95% users are Android 15 , very few users are android 13 or 14 .

[AndreyMedal]

I have same issue on different versions of Android in Compose code. Any ideas how to fix?

From Galaxy Note 20 (API 33):

This typically happens when the parent component's onDispose method is triggered after opening/closing multiple different models via BottomSheet.

A  Cmdline: tv.app
A  pid: 4565, tid: 4565, name: .app >>> tv.app<<<
A        #01 pc 0000000000220050  /data/app/~~CX5QwX4_Gtz-M4n8gR_CQA==/tv.app-IHX_7bUOjf-JxYTjIXL5sQ==/base.apk!libfilament-jni.so (utils::TPanic<utils::PreconditionPanic>::panic(char const*, char const*, int, char const*, std::__ndk1::basic_string<char, std::__ndk1::char_traits<char>, std::__ndk1::allocator<char> >)+176) (BuildId: d5861ae549ccbba9b42c018622ea03a688c32f73)

[paulorrfilho]

I just sent a PR to handle this issue.

Panic.cpp should call android_set_abort_message() so Android developers can see the reason for the crash in the tombstone in either Google Play Console or Crashlytics.