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:
I test my app on all iPhones and iPads (ios 15) its works without any crash.
can someone help me with what the crash log file contains, please?
Exception Type: EXC_CRASH (SIGABRT)
This means that your app crashed itself by calling abort. Now consider the backtrace of the crashing thread:
2 libsystem_c.dylib … abort + 164
3 Flutter …
4 Flutter …
5 Flutter …
6 Flutter …
7 Flutter …
8 Flutter …
9 Flutter …
10 UIKitCore … -[UINib instantiateWithOwner:options:] + 2296
UIKit is in the process of instantiating your nib and has called into your third-party runtime. That is in the middle of a bunch of work when it calls abort. It’s hard to say why it’s doing that because there’s no symbols.
My advice is that you work to symbolicate this crash report to see if it offers any insight into why your third-party runtime has failed. For info on how to symbolicate, 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"
-
—
MobileTen
-
—
zitob9
-
—
MobileTen
Add a CommentPlease check all story boards resources.
i receive just this
Take a look at your app's deployment target and make sure you're not using new api features below this target level. For example if you're targeting iOS 13 but using features specific to only iOS 15 only meant for iOS 15 and you're not testing on an iOS 13 device. Those type of scenarios. But looking at the report above you are having an issue with your main storyboard file.