Xamarin.Android uses AndroidManagedSymbols to control whether an mSYM is produced. Since it's disabled by default, it needs a property in the project file to enable it, so affects templates too.
This does not match the final spec, which uses a MonoSymbolArchive property instead. MonoSymbolArchive should default to true for symbolicatable, releaseable builds - i.e. when there are debug symbols and the shared runtime is not in use.
Basically, users shouldn't have to ever see MonoSymbolArchive in their csproj, it only exists in case users need to disable it. This also means that existing projects will get symbols.
Marking high as the AndroidManagedSymbols should go away ASAP.
The value should be removed from the templates as well.
I am trying to verify this issue with Xamarin.Android 7.0.99-90 and observed that the AndroidManagedSymbols property still exist in the csproj file of newly created project.
Please refer to the screencast:
Hence, I am reopened this issue.
The AndroidManagedSymbols has been replaced with MonoSymbolArchive
VS (and XS?) needs to update the templates to reflect this change
Fixed in version 22.214.171.1245 (master)
Commit: 4586442f81d1aa43f9922a32f8fdf240166c40ac (xamarin/XamarinVS)
Fixed in version 126.96.36.1995 (cycle9)
Commit: 4531f65c279d4c3b215383bbe8576d66bf8896a7 (xamarin/XamarinVS)