This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 48%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGS%3C/text%3E%3C/svg%3E)
Hi Team,
We have a app developed in .net MAUI for both android and ios. We are able to see Crashes in ios (Appstore connect)
here is how we are able to see the crashes
Step 1 :- open X-Code
Step 2 :- click on window> Organizer
Step 3 :- select the app and click on crashes. we are able to find the crashes
When we try to symbolicate the crash following the below steps
symbolicate -o "symbolicatedCrash.txt" "MyAppName 2-12-14, 9-44 PM.crash" "MyAppName.app"
following the below link with dsym files
https://jmillerdev.com/symbolicating-ios-crash-files-xamarin-ios/
it is not showing any error, but the symbolication is not showing meaning full information.
Can you please help in symbolicating the crash.
And also is there is any way that we can schedule a screen sharing section with Microsoft team for 30 mins. As we cannot share any source code in Forums.
Thanks in Advance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 3%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWZ%3C/text%3E%3C/svg%3E)
It is an extra question of the other thread- How to check crash log sent by Apple review team for iOS .Net MAUI application. - Microsoft Q&A
If Bruce's answer is right solution, you can accept it.
it is not showing any error, but the symbolication is not showing meaning full information.
I read the article, the way that you try to symbolicate the crash is correct. It's not clear what the symbolizations are, and you are not willing to share the information on Q&A. If you want to schedule a screen sharing section, please open a support ticket for this. You will get 1:1 support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
the crash file has address in the dumps. symbolicate uses the symbol file (.dSYM) from the build to update the addresses to symbol name (and source line number if available) when defined. this make the crash log more readable.
first you are interested the exception. then you are interested in the backtrace to determine what the app was doing. you particularly want to follow the trace of the thread that crashed.