Bug 15938 - "Installing application on device" never completes
Summary: "Installing application on device" never completes
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.10.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-11-05 10:16 UTC by Tim Jowers
Modified: 2013-11-05 14:27 UTC (History)
1 user (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 NOT_ON_ROADMAP

Description Tim Jowers 2013-11-05 10:16:31 UTC
Updated Visual Studio. VS 2010, 10.0.40219.1 SP1Rel. .Net V 4.5.50938 SP1Rel. Win 7 Pro. 
Now can no longer deploy from Xamarin. 
Switched from beta to stable channel and updated Xamarin but same problem. Version 4.0.13 (build 38).
Showstopper.
Get stuck for at least 10 minutes when trying to run in either Release or Debug then get stuck here:

Detecting installed packages

Installing application on device
Comment 1 Tim Jowers 2013-11-05 10:17:29 UTC
Xamarin Studio
Version 4.0.13 (build 38)
Installation UUID: ed3e53cf-9a6c-4ceb-b832-ebd86ed15b70
Runtime:
	Microsoft .NET 4.0.30319.18408
	GTK+ 2.24.20 theme: MS-Windows
	GTK# (2.12.0.0)

Xamarin.Android
Version: 4.8.3 (Indie Edition)
Android SDK: C:\lib\adt-bundle-windows-x86_64-20130522\sdk
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0   (API level 14)
		4.0.3 (API level 15)
		4.2   (API level 17)
		4.3   (API level 18)
Java SDK: C:\Program Files\Java\jdk1.6.0_45
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, m
Comment 2 Tim Jowers 2013-11-05 11:40:05 UTC
My mistake ... what I installed was:
VS ultimate 2013
Version 12.0.21005.1 REL
Same .NET version. 
Odd that older VS 10 is still there and can be opened.
Comment 3 Tim Jowers 2013-11-05 11:41:16 UTC
Also, deployment has been running for 1 hour now. Still shows "Installing application on device" but the progress bar is slowly progressing and now near 85%. This is the second device I've tried, both Samsung (Galaxy tab II 10" and Galaxy Note)
Comment 4 Tim Jowers 2013-11-05 11:53:21 UTC
oh boy, adb install seems to hang too.
Comment 5 Tim Jowers 2013-11-05 12:04:43 UTC
opened adt eclipse and made new simple android project. Shows:
This version of the rendering library is more recent than your version of ADT plug-in. Please update ADT plug-in
Eclipse->Update. nothing found.
Android AVD update: updates made to "Android SDK Tools" and Android SDK Platform-tools". 
Reopened eclipse and check for updates but 
This version of the rendering library is more recent than your version of ADT plug-in. Please update ADT plug-in
So manually updated android stuff from android update site (new software menu option in eclipse) but that failed with:
An error occurred while collecting items to be installed
session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.android.ide.eclipse.adt,22.3.0.v201310242005-887826
No repository found containing: osgi.bundle,com.android.ide.eclipse.adt.package,22.3.0.v201310242005-887826
No repository found containing: osgi.bundle,com.android.ide.eclipse.base,22.3.0.v201310242005-887826
No repository found containing: osgi.bundle,com.android.ide.eclipse.ddms,22.3.0.v201310242005-887826
No repository found containing: osgi.bundle,com.android.ide.eclipse.gldebugger,22.3.0.v201310242005-887826
No repository found containing: 

When trying to run simple app I get:
[2013-11-05 12:04:14 - tesat] Uploading tesat.apk onto device '42f7cd098848afb9'
[2013-11-05 12:04:20 - tesat] Failed to install tesat.apk on device '42f7cd098848afb9': timeout
[2013-11-05 12:04:20 - tesat] Launch canceled!
Comment 6 Tim Jowers 2013-11-05 13:05:55 UTC
bug with Google's Android ADB. Killed adb.exe and restarted and working now.
Comment 7 Mikayla Hutchinson [MSFT] 2013-11-05 14:27:02 UTC
Yep, adb is notoriously unreliable. We've been investigating ways to cut it out of the pipeline, but that won't happen any time soon, unfortunately.