Bug 11419 - 'Mono Shared Runtime' is allways installed on device
Summary: 'Mono Shared Runtime' is allways installed on device
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 4.8.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-03-26 09:02 UTC by Erlend
Modified: 2017-06-28 21:44 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Erlend 2013-03-26 09:02:24 UTC
When deploying my app in release mode, with the 'Use shared runtime' checkbox disabled, the 'Mono Shared Runtime' is still installed on the device.

If i enable the 'use shared runtime' (still in release mode) it copies the 'Mono Android-16 Support'.

Please advice. I want evertying in ONE APK, so i can deploy the app via a web server.


Comment 1 Erlend 2013-04-03 09:12:56 UTC
i made a custom build script using the instructions here and got it working!

Comment 2 Atsushi Eno 2013-05-22 15:13:57 UTC
Assuming it is rather common to XS and VS. -> Tools and Addins
Comment 3 Cody Beyer (MSFT) 2017-06-28 21:44:15 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.