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 59821 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
If you try to run a build of an android app on a device which has an architecture not matching any of those in the build (For instance, if you build an app with only `armeabi-v7` and try deploy to an `x86_64` emulator), you get a cryptic error about unable to deploy to device.
If you try and install the .apk via adb `adb install com.some.app.apk` it returns an error code of:
We should detect this and present a better error to the user with a suggestion to correct it.
I have an existing comment on a bug that I've marked enhancement that might help with this effort:
This seems like a general enhancement compared to the specific situation in 58594 and thus I am CONFIRMING this behavior.
I initially moved this to VSMac because we addressed this specific issue, however, I think in general the install target should do this so that users using the cmdline or XVS can benefit from this as well.