Bug 6111 - Version of Mono shared runtime and platform framework won't be recognized
Summary: Version of Mono shared runtime and platform framework won't be recognized
Status: RESOLVED DUPLICATE of bug 6117
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- blocker
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-07-13 05:27 UTC by Eduardo Terol
Modified: 2016-08-03 15:23 UTC (History)
8 users (show)

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


Attachments
logcat after unsuccessful recognition of the version (15.04 KB, text/plain)
2012-07-16 03:10 UTC, Eduardo Terol
Details


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 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:
Status:
RESOLVED DUPLICATE of bug 6117

Description Eduardo Terol 2012-07-13 05:27:16 UTC
Since last update to Android 4.1.1 the version of the two packages won't be recognized in Samsung Nexus. Each time I build the application the old packages get deleted and I must build again so they get installed to the device.

The building errors when the two packages are there are:
-------
There is a shared runtime on the device whose version cannot be determined.  A new runtime will not be deployed.  If the runtime needs to be replaced, please manually remove it from the device.

There is a platform support runtime on the device whose version cannot be determined.  A new platform support runtime will not be deployed.  If the platform support runtime needs to be replaced, please manually remove it from the device.
-----

The build output is:
-------
Removing old runtime: Mono.Android.DebugRuntime [2147483647]..
Removing old runtime: Mono.Android.Platform.ApiLevel_8 [2147483647]..
-------

The alternating time works fine (although the packages must be reinstalled to the device) but then again next time will fail with the same messages.
Comment 1 Eduardo Terol 2012-07-13 05:29:49 UTC
An easy workaroung would be to know how to override the recognition of the packages and be able to manually prevent the build process from uninstalling these two packages from the device.
Comment 2 Jonathan Pryor 2012-07-13 15:18:17 UTC
Google has apparently changed the permissions of /data/system/packages.xml so that it is no longer readable on Android 4.1/Jelly Bean. We'll need to find an alternate way to get package version information from the device.
Comment 3 Jonathan Pryor 2012-07-13 15:20:54 UTC
Eduardo: Which IDE are you using, MonoDevelop or Visual Studio?

This looks similar to #6117, except you're not reporting a package installation error.
Comment 4 konne 2012-07-15 18:06:01 UTC
I have the same Issue after my update of the nexus last night. Is there any way for a workaround to disable the checkin of the shared runtime?
Comment 5 Eduardo Terol 2012-07-16 03:10:04 UTC
Created attachment 2198 [details]
logcat after unsuccessful recognition of the version
Comment 6 Eduardo Terol 2012-07-16 03:15:52 UTC
@Jonathan: I have attached the logcat of my device after unsuccessful recognition of the packages version. I fail to see the same error messages as in #6117, but it *might* be the same cause.

@konne: I also have the problem with my nexus after the night of the 13th (are you in Germany too?)

For now we just need a way to disable the version check when building. The option "Preserve application data/cache on device between deploys" seemed a good candidate for this functionality, unfortunately it shows no effect.
Comment 7 konne 2012-07-16 03:44:53 UTC
Hi I'm also in Germany :-)

I have at the moment an workaround. I disabled shared librabries. So the linking / delpoyment need a longer time, but no it is working.
Comment 8 Darren Abbott 2012-07-29 10:12:41 UTC
I have the same problem on my WiFi Xoom that recently upgraded to Jelly Bean.  Disabling shared libraries doesn't work for me.  If I disable fast deployment, I can get into a mode where every other deploy seems to work, but still can't debug reliably.

The only workaround I have is to stay in Release mode (which always works), and try to debug via Log.Debug().

And I am not in Germany :-).
Comment 9 Jonathan Pryor 2012-07-29 23:21:23 UTC
Please try the 4.2.5 Beta release. That should fix deployment to API16 hardware devices.

Thanks,
 - Jon
Comment 10 Jonathan Pryor 2012-07-29 23:21:47 UTC

*** This bug has been marked as a duplicate of bug 6117 ***