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 or GitHub 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.
The project on case #5618 builds into a broken APK with no assemblies on it.
You have first to replay "copy /Y" with cp -f, once that, things will run but fail to produce something usable.
I am guessing this is because FastDev is on, which is the default.
Under FastDev, assemblies are not placed in the APK, so APK's are "broken" if you try to run them without an IDE. When run from an IDE, the APK is first copied over, and then all the needed assemblies are copied over.
Here's the problem.
When xbuild is creating the APK it thinks FastDev is enabled, so it leaves assemblies out.
But MD and/or the deployment task, thinks FastDev is off, so no assembly upload happens and we end up with a broken install.
Just to clarify, this is all from within the MD addin.
The project is building without the assemblies from within MD, but MD is not deploying the additional assemblies needed when copying the project to the device.
What version of MD?
MfA Addin 220.127.116.11 - it doesn't show any update even if I enable alpha/beta channels.
Uninstall the 18.104.22.168 addin, you should be using the one included with MD which has a lower version (22.214.171.124 was only used for internal testing and was an experimental versioning scheme that we decided against).
The issue boiled that I had a mandroid reporting 2.0.0 when in fact it was a 4.0.1 install.
It would be super nice if md-addins refused to work on versions it doesn't support.