.NET MAUI, how to load the iOS crash report to Visual Studio

Question

Created Jun ’23

Replies 2

Boosts 1

Views 2.2k

Participants 3

I'm working on a .NET MAUI application. The project is ready and it works fine on Android. It even works fine on my iPhone - both the Debug and Release version. However when I publish the application to App Store, it is rejected because it is crashing. I received several crashlog-9850E490-EC2E-4278-A4EE-8EB08D14C815.txt like files. I'm not sure how to decode them so I can see the call-stack where the crash happens.

For Windows project I always have a *.dmp file what I can open using Visual Studio and see the call-stack. However I'm not sure how to open such iOS crash report using Visual Studio for Mac.

Any help is appreciated. Thanks!

Boost

Answer 1

DTS Engineer OP

Apple

Jun ’23

I'm not sure how to open such iOS crash report using Visual Studio for Mac.

That specific question is one you should ask your IDE’s vendor.

Taking a step back, is the crash report in human-readable or JSON format? If it’s the latter, you can convert it to the former by changing the extension to .ips and then using Quick Look in the Finder.

Once you have it in human-readable format, you should be able to see some basic info. You may need to symbolicate the backtraces to make progress. My standard reference for that is Adding Identifiable Symbol Names to a Crash Report.

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

0

Answer 2

CsabaStupak OP

Jun ’23

It looks like the issue was with Profile certificate. Not sure if the certificate became invalid because of "new Apple program license agreement" or due to deep-link support I added to my application.

Anyway this was pretty frustrating. The problem I see here that the compiler, the publish process and even the review or CER report did not warn about the certificate issue (it just crashed) and I just can guess what could be the problem and do trial-error approach to solve the issue...

In this case it took 2 weeks until I find that this is the problem :-(

0