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 on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
It's an issue with the Deployment target.
@Dean can you please take a look?
work around is to turn off AndroidManagedSymbols for now.
This is to do with the mkbundled mono-symbolicate not working.
@danish can you please try to reproduce the issue with 126.96.36.1990 ?
I wasn't able to reproduce the issue even with latest bits (188.8.131.523).
My bad, I mean can you try to reproduce the issue with 184.108.40.2064?
As we couldn't repro, marking it as Resolved - Not_Reproducible.
Thanks @narayanp, I've also tried with the attached project and it deploys successfully with current Beta (220.127.116.115) for either Debug or Release configurations.
I will mark this bug as a duplicate of a new bug I have filed that precisely characterizes the appearance of this problem in the XamarinVS 18.104.22.1689 version. As mentioned there, my suspicion is that this problem might be related to the particular build environment (the particular computer) that was used to build this exact problematic version of the Xamarin.VisualStudio installer. I suspect that could explain why the issue has somewhat "mysteriously" appeared and disappeared both in this bug (Bug 44105) as well as in one other report of the problem (Bug 43833).
*** This bug has been marked as a duplicate of bug 46279 ***