App auto-closes on launch

Hello.

I have developed an app: Kedeo.es:

https://apps.apple.com/us/app/kedeo-es/id1609942690

Use external libraries to connect to Google Firebase Auth and Notifications. Also use Storekit for in-app purchase.

It works perfectly, and it has also passed the tests and is published in the store, however, my client says that there are between 20% and 40% of users who are automatically closed just by opening. Does anyone else have this bug? It doesn't happen to me, and that's why I can't get any log to know more about the problem.

If anyone can help I'd appreciate it.

Greetings.

Up vote post of alejandro275 Down vote post of alejandro275
418 views
Posted by
alejandro275
Reply
Add a Comment

Replies

The phrase “automatically closed just by opening” suggests that the app is crashing on launch. If so, it should generate a crash report. Ask if they can locate one. For advice on how to do that, see Acquiring Crash Reports and Diagnostic Logs.

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

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Add a Comment

Thanks. Will try to get it.

The funny thing is that during tests with Testflight, no one complained. The problems with a part of the users, happens during production, with the download from the app store.

Greetings.

Posted by
alejandro275
Up vote reply of alejandro275 Down vote reply of alejandro275
Add a Comment

This is the bug that returs. Could it be caused by an external library like admob??:

https://iosapps-ssl.itunes.apple.com/itunes-assets/Purple122/v4/5c/51/01/5c510191-1502-23fa-1c89-3e41ea66e627/crashlog-A3D22378-740B-412A-9D6F-831F38890B7C.txt?accessKey=1651858650_6552063813599093776_%2BZFaO5Nhm1EBRUrWSifSx0DwDJI9LpdBIyMe4Cs%2BtCfa5uNdQMpikNHy9g%2Blb5PGiHDMeepTjYllPE1C1ZqEppX8hPYR9%2FBb0BuG8OBYalfZhrHwykAi7jehgoTFi9cdBZqoyh1dhKJPOCzOJI6GLb0HyhBdnNHylJrxwJ%2B1SKFQz%2Bcu1AQhSoJDj9SKCkNgT3f%2FWtE49OLCB7pHsmKfVw%3D%3D

Posted by
alejandro275
Up vote reply of alejandro275 Down vote reply of alejandro275
Add a Comment

Consider this:

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000010022f0d4

Your program crashed because it hit a trap, that is, some code within your process detected a problem and deliberately crashed.

Now look at the backtrace of the crashing thread:

Thread 0 Crashed::   Dispatch queue: com.apple.main-thread
0 Kedeo.es  …
1 Kedeo.es  …
2 Kedeo.es  …
3 UIKitCore … -[UIViewController _sendViewDidLoadWithAppearanceProxyObjectTaggingEnabled] + 108 …
4 UIKitCore … -[UIViewController loadViewIfRequired] + 1048 …
5 UIKitCore … -[UIViewController view] + 32 …

Frames 5…3 are UIKit trying to load a view controller’s view. That view controller is in your code, frame 2, and that’s not symbolicated )-:

To investigate this further, you need to symbolicate your crash report. For more on this, 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"

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo

  • What I don't understand is why it fails only during the production period, and not in my xcode or in testflight. I'm trying to get more information.

    Greetings.

    —
    alejandro275
Add a Comment