i am attaching crash logs would be really appreciated for any kind of help :)
Review Environment
Submission ID: f7cb438c-5784-44e7-abcf-4a787c9398ff Review date: April 30, 2024 Version reviewed: 1.0
Guideline 2.1 - Performance - App Completeness
We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue.
Review device details:
The presence of a Last Exception Backtrace section indicates that your app crashed due to an unhandled language exception. Consider its backtrace:
Last Exception Backtrace:
0 CoreFoundation … __exceptionPreprocess + 164
1 libobjc.A.dylib … objc_exception_throw + 60
2 CoreFoundation … -[NSException initWithCoder:] + 0
3 Runner … 0x100a64000 + 591004
4 Runner … 0x100a64000 + 589048
5 Runner … 0x100a64000 + 1233708
6 Runner … 0x100a64000 + 1242920
7 Flutter … 0x1014c4000 + 6040944
8 Flutter … 0x1014c4000 + 277772
9 libdispatch.dylib … _dispatch_call_block_and_release + 32
10 libdispatch.dylib … _dispatch_client_callout + 20
11 libdispatch.dylib … _dispatch_main_queue_drain + 988
12 libdispatch.dylib … _dispatch_main_queue_callback_4CF + 44
13 CoreFoundation … __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
14 CoreFoundation … __CFRunLoopRun + 1996
15 CoreFoundation … CFRunLoopRunSpecific + 608
16 GraphicsServices … GSEventRunModal + 164
17 UIKitCore … -[UIApplication _run] + 888
18 UIKitCore … UIApplicationMain + 340
19 Runner … 0x100a64000 + 17996
20 dyld … start + 2240
Frames 20 through 9 are typical for block that’s been scheduled on the main queue. Frames 8 through 3 are ‘your’ code. Well, more likely code from your third-party tooling.
It’s hard to debug this further from the crash report. Your code has thrown an exception and it’s up to you to work out why. A good first step would be to symbolicate frames 8 through 3. See Adding identifiable symbol names to a crash report.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"