Bug 6215 - MonoDevelop cannot deploy to device using latest Android tools/SDK + Jelly Bean
Summary: MonoDevelop cannot deploy to device using latest Android tools/SDK + Jelly Bean
Status: RESOLVED DUPLICATE of bug 6117
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-07-20 14:18 UTC by Aaron Bockover
Modified: 2016-08-03 15:37 UTC (History)
2 users (show)

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

Description Aaron Bockover 2012-07-20 14:18:25 UTC
Using a Galaxy Nexus recently upgraded OTA to Jelly Bean (4.1.1) and the very latest Android tools/SDK with the latest MonoDevelop and M4A, I can no longer deploy using MonoDevelop:

-- Detecting shared runtime location
-- Detecting package list location
-- Getting package list from device
-- Failed to get package list.
** Text node cannot appear in this state.  Line 1, position 1.

I am able to deploy using xbuild directly however.

MonoDevelop 3.0.3.4
Installation UUID: 5d3787d3-4a93-457a-99b1-4577aebb964c
Runtime:
	Mono 2.10.9 (tarball)
	GTK 2.24.10
	GTK# (2.12.0.0)
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.3.2 (1177)
	 Build 4E2002
Monotouch: 5.2.12
Mono for Android: 4.2.4.167234518
Android SDK: /Users/aaron/android-sdk
Supported Android versions:
	Version: 1.6	ApiLevel: 4
	Version: 2.1	ApiLevel: 7
	Version: 2.2	ApiLevel: 8
	Version: 2.3	ApiLevel: 10
	Version: 3.1	ApiLevel: 12
	Version: 4.0	ApiLevel: 14
	Version: 4.0.3	ApiLevel: 15
Java SDK: /usr/bin

Build information:
	Release ID: 30003004
	Git revision: 57eb8135299a707287d21a1e0ca1040babf6d9aa-dirty
	Build date: 2012-07-16 19:44:05+0000
	Xamarin addins: c331c3ba7ef02e9823ef5dfc9f6f9038f187158b
Operating System:
	Mac OS X 10.7.4
	Darwin bacon.local 11.4.0 Darwin Kernel Version 11.4.0
	    Mon Apr  9 19:32:15 PDT 2012
	    root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64

(Also, MonoDevelop should probably include this in its Version Information tab):

aaron@bacon android-sdk/tools% adb 2>&1 | head -n1
Android Debug Bridge version 1.0.29

Finally, pm list packages -f produces the following format of output, though I don't know what MonoDevelop actually runs to get the package list.

$ adb shell pm list packages -f
package:/data/app/Mono.Android.DebugRuntime-1.apk=Mono.Android.DebugRuntime
package:/data/app/Mono.Android.Platform.ApiLevel_8-1.apk=Mono.Android.Platform.ApiLevel_8
...
Comment 1 Aaron Bockover 2012-07-20 14:23:50 UTC

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