Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 56201 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
# Steps to reproduce
Add <MonoSymbolArchive>True</MonoSymbolArchive> to your csproj
Build and Archive, publish to google play.
# Expected behavior
Msym files are uploaded.
# Actual behavior
Confirmed using the following steps:
1. Create a Xamarin.Android project from the blank template.
2. Change solution configuration to Release.
3. Add <MonoSymbolArchive>True</MonoSymbolArchive> to the Release section of the .csproj file
4. Build and archive.
5. Publish Ad-hoc to an APK.
6. Unzip the APK -> no msym files were included.
Also tried this with <AndroidManagedSymbols>True</AndroidManagedSymbols> (in case there is a regression from 44447): same result, no msym files.
Created attachment 23180 [details]