Add ability to upload mono mSYM files and run mono-symbolicate automatically

[nathanielcook]

Describe the solution you'd like
In addition to dSYM folders we also have mSYM folders (if you set MonoSymbolArchive to true in the csproj). AppCenter should allow us to upload mSYM folders and AppCenter should automatically run mono-symbolicate to give us the line numbers for both Android and iOS.

Describe alternatives you've considered
I can run mono-symbolicate locally after I download the raw crash report, but it is a bit of a pain.

Additional context
Add any other context or screenshots about the feature request here.

[nathanielcook]

Linking a related issue: mono/mono#11625

Would really love it if mono-symbolicate would work on iOS also. Right now it is working for us only on Android. And again, it seems like this should be built in and run automatically by AppCenter's back end.

[winnie]

@nathanielcook thanks for submitting this! Unfortunately, we don't have the bandwidth to work on this at the moment since a large part of our team is focused on improving HockeyApp scenarios as listed on our roadmap. I'll keep this on our radar though and update this issue if anything changes. Thanks!

[Redth]

It's technically possible to do yourself with a bit of effort today.

First you need to enable building the mono symbols on your project with the <MonoSymbolArchive>true</MonoSymbolArchive> msbuild property.

Next, you'll need to use a post-build script to find the **/*.msym file generated as part of the build and upload it somewhere you can grab it from later.

Finally, you can view the "Raw" crash log dump, copy and paste that to a file, and use mono-symbolicate to process it.

@dellis1972 is going to look at writing some better docs around how to use mono-symbolicate with Xamarin apps.

[justintoth]

We don't want better docs, we want built-in support for crash line numbers in App Center errors (like the rest of the .NET ecosystem has had for 15 years.)

[nathanielcook]

Agreed; I appreciate the follow-up, but this should definitely be automatic.

[rjhind]

However its implemented, AppCenter needs to show line numbers for Android and iOS crashes.

[pellet]

yes please add this as a feature, I'm sure a lot of people using xamarin are having trouble tracking down null reference exceptions and other exceptions without knowing which line is causing it.

[BillFulton]

It's jaw-dropping that line numbers in crash reports are not regarded as critically important. Surely those who set priorities have once developed programs themselves?

[joncortez]

Please move this feature up on the priority list as it is negatively affecting the value of App Center crash reporting. Thanks!

[joncortez]

It's technically possible to do yourself with a bit of effort today.

First you need to enable building the mono symbols on your project with the <MonoSymbolArchive>true</MonoSymbolArchive> msbuild property.

Next, you'll need to use a post-build script to find the **/*.msym file generated as part of the build and upload it somewhere you can grab it from later.

Finally, you can view the "Raw" crash log dump, copy and paste that to a file, and use mono-symbolicate to process it.

@dellis1972 is going to look at writing some better docs around how to use mono-symbolicate with Xamarin apps.

@Redth I tried setting MonoSymbolArchive to true and by itself it did not create the *.mSYM folder. In the release notes for Xamarin.Android 6.1, it states that $(AndroidManagedSymbols) to be set to true together with $(DebugSymbols) to True and $(DebugType) to PdbOnly. I assume we should use MonoSymbolArchive versus AndroidManagedSymbols. What other things we need to set with MonoSymbolArchive to make it work?

[bellissimo]

@joncortez You need $(Optimize) as True, $(DebugSymbols) as True and $(DebugType) as PdbOnly, along with $(MonoSymbolArchive) as True

A couple of queries for Xamarin folk, @Redth :

1. What is the difference between MonoSymbolArchive and AndroidManagedSymbols? And does it make any difference in this context as to which one we set?

2. $(DebugType) can be PdbOnly or Portable (which is more supposed to be more efficient). Again, which one is recommended for line numbers, or does it make no difference which in this context?

[dellis1972]

@bellissimo PdbOnly support is being deprecated in.net 5/6 dotnet/android#5162. So its probably best to try to use Portable now.
AndroidManagedSymbols was removed a while ago , so setting MonoSymbolArchive is the way to control the generation of the mSYM archive.

It looks like we still have AndroidManagedSymbols in our docs, so we should remove that

[cmcnicholas]

here I am in 2021 and app centre still won't show me line numbers :(

[BillFulton]

If it’s against current strategy to work on this, couldn’t it be escalated to high enough management for an exception? Seems unbelievable.

…

On 31 Mar 2021, at 9:23 am, Craig McNicholas ***@***.***> wrote: here I am in 2021 and app centre still won't show me line numbers :( — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#324 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVADQOO3P5MI3HUEDJGQ5LTGJFO5ANCNFSM4HGP47TQ>.

[pellet]

I think I'll disable aot due to this issue. At least I'll be able to see where crashes happen then.

…

On Wed, Mar 31, 2021, 08:28 Bill ***@***.***> wrote: If it’s against current strategy to work on this, couldn’t it be escalated to high enough management for an exception? Seems unbelievable. > On 31 Mar 2021, at 9:23 am, Craig McNicholas ***@***.***> wrote: > > > here I am in 2021 and app centre still won't show me line numbers :( > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub < #324 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ACVADQOO3P5MI3HUEDJGQ5LTGJFO5ANCNFSM4HGP47TQ >. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#324 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC3X6UA5QFPD32W2AO45NDTGJF7FANCNFSM4HGP47TQ> .

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[BillFulton]

Seems wrong to close this. The ’no further activity’ is on Microsoft, not users.

…

On 30 Jun 2021, at 8:04 pm, msftbot[bot] ***@***.***> wrote: This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#324 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVADQOMDBAD7GO6MNWZKLLTVLTZPANCNFSM4HGP47TQ>.

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[akamud]

Unbelievable.

[cmcnicholas]

Can someone please re-review this from the Microsoft team and give a reason why any other ticket is being prioritised over this? This isn't just a quality of life update, it's vital.

[fgiacomelli]

I'm also looking for a way to have crashlog generated from Xamarin.Android app desymbolicated in Appcenter automatically, without being obliged to use monosymbolicate locally on my PC.

[anpin]

Would agree with everyone above: this is badly needed for iOS!

[cmcnicholas]

Oh no you dont

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[RyanNieburViewpoint]

This should not be stale.

…

On Wed, Mar 30, 2022 at 3:00 PM msftbot[bot] ***@***.***> wrote: This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. — Reply to this email directly, view it on GitHub <#324 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADQ63HB6DQ4BH4FTCOXYQFTVCTFJPANCNFSM4HGP47TQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[anpin]

bump

[BillFulton]

Let’s not lose sight of this critical issue.

…

On 30 Aug 2021, at 3:02 am, Mahmoud Ali ***@***.***> wrote: Unbelievable. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#324 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVADQIDF4XFCYT45SLK3ELT7JRZVANCNFSM4HGP47TQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[MaximMikhisor]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

Even do not dream about it.

[BillFulton]

This is essential

…

On 31 Jul 2022, at 6:04 pm, Maxim Mikhisor ***@***.***> wrote: This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. Even do not dream about it. — Reply to this email directly, view it on GitHub <#324 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVADQJFKGOTIFCFJ6FOUTDVWYXQBANCNFSM4HGP47TQ>. You are receiving this because you commented.

[danielmeza]

We need some atention here please!

[dupuisdavid]

Any update???

[dupuisdavid]

MonoSymbolArchive

I'm also trying to generate debug symbols but without success.
Here are my parameters :
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "> <MonoSymbolArchive>true</MonoSymbolArchive> <DebugSymbols>true</DebugSymbols> <DebugType>pdbonly</DebugType> <Optimize>true</Optimize> <OutputPath>bin\Release</OutputPath> <ErrorReport>prompt</ErrorReport> <WarningLevel>4</WarningLevel> <AndroidManagedSymbols>true</AndroidManagedSymbols> <AndroidUseSharedRuntime>false</AndroidUseSharedRuntime> <AotAssemblies>false</AotAssemblies> <EnableLLVM>false</EnableLLVM> <BundleAssemblies>false</BundleAssemblies> <DefineConstants>DEBUG;</DefineConstants> <AndroidEnableMultiDex>true</AndroidEnableMultiDex> <EmbedAssembliesIntoApk>true</EmbedAssembliesIntoApk> <CheckForOverflowUnderflow>true</CheckForOverflowUnderflow> <PlatformTarget>AnyCPU</PlatformTarget> <GenerateSerializationAssemblies>Off</GenerateSerializationAssemblies> <AndroidSupportedAbis>armeabi-v7a;x86;x86_64;arm64-v8a</AndroidSupportedAbis> <AndroidLinkMode>SdkOnly</AndroidLinkMode> </PropertyGroup>

Any help?
Thank you!

[brunck]

@dupuisdavid maybe setting DebugType to "portable" would help?
Reference: #324 (comment)

[BillFulton]

We need this functionality now!!!

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[ghost]

This issue will now be closed because it hasn't had any activity for 15 days after stale. Please feel free to open a new issue if you still have a question/issue or suggestion.

[brunck]

@winnie Please re-open this issue. This is still a problem and many people are waiting for this functionality (including me).

[BillFulton]

Dear bot No.

…

On 13 Dec 2022, at 1:01 pm, msftbot[bot] ***@***.***> wrote: This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. — Reply to this email directly, view it on GitHub <#324 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVADQIUZY4MEBJNAVXXNB3WM7KITANCNFSM4HGP47TQ>. You are receiving this because you commented.

[rhult]

I got tired of waiting for this to never happen so I put together a small tool that helps somewhat. See the repo at https://github.com/rhult/crash-sharpener

It is not a full solution, but it does two things:

1. Add information to stack traces that can be uploaded as handled errors to App Center
2. A tool you can run locally to symbolicate those stack traces

You can use this to automate symbolicating by downloading the errors from App Center using its API, and then symbolicate them on your machine. I have tested it with iOS and Android on .net7 and it works well. I get line numbers from release builds this way.