App crash on launch by apple "exception" type":"EXC_CRASH","signal":"SIGABRT"

help me to resolve this issue, please

To receive the most efficient support for this issue, we recommend contacting Apple Developer Technical Support, who can provide code-level support for Apple frameworks, APIs, and tools. Contact them directly by filing a Technical Support Incident.

BusterBrown17 is correct: Opening a DTS TSI is always a good option for weird crashes like this. However, I can also provide a little context here on DevForums.

Consider this snippet from your crash report:

Exception Type:  EXC_CRASH (SIGABRT)

This almost always means that the app crashed due a a trap, that is, it detected a problem with its own internal state and deliberately crashed itself. Now look at the crashing thread backtrace:

Thread 42 name:  isarworker
Thread 42 Crashed:
0   libsystem_kernel.dylib  … __pthread_kill + 8
1   libsystem_pthread.dylib … pthread_kill + 268
2   libsystem_c.dylib       … __abort + 128
3   libsystem_c.dylib       … abort + 192
4   libsystem_malloc.dylib  … malloc_vreport + 908
5   libsystem_malloc.dylib  … malloc_report + 64
6   libsystem_malloc.dylib  … find_zone_and_free + 308
7   isar_flutter_libs       … env_close + 140
8   isar_flutter_libs       … mdbx_env_open + 1680
9   isar_flutter_libs       … isar_core::instance::IsarInstance::open_internal::h5dfcafd44edbc112 + 736
10  isar_flutter_libs       … isar_instance_create + 1028
11  isar_flutter_libs       … _$LT$F$u20$as$u20$threadpool..FnBox$GT$::call_box::hcbf6df1e100ade07 + 60
12  isar_flutter_libs       … std::sys_common::backtrace::__rust_begin_short_backtrace::hdb41e98604887671 + 4364
13  isar_flutter_libs       … core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::h8fa6c9cf1…
14  isar_flutter_libs       … std::sys::unix::thread::Thread::new::thread_start::h9881401f140304fe + 36
15  libsystem_pthread.dylib … _pthread_start + 148
16  libsystem_pthread.dylib … thread_start + 8

In frame 7 your code — well, code from the third-party runtime you’re using — seems to be freeing some memory. Frame 6 is the system memory allocator. It has detected a problem and called frame 5 to report it and then trap.

You wrote:

App crashes in review but works well in Simulator or real device.

The majority of such problems are caused by a difference between the Debug and Release build of your product. I recommend that you run some tests with the Release build, as described in Testing a release build.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"