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 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.
Steps to reproduce this issue
1. Open or create any Android application.
2. Debug or run the application on Physical device
Actual result: When user debug or run the application on physical device, it is taking too much time to installing shared runtime and Installing package and not deploying application on device we have tried it for approximate 30 minutes. While on all Emulators ant on other devices, application deployed and launched successfully.
Expected Result: Application should deployed to SamsungS3.
Samsung S3-Version 4.0.4
After disconnected device from system we are getting error in deploy to device
Deploy to device: https://gist.github.com/atin360/a1a68206bf4c61aa1bc4
X.S 4.0.9(build 3)
REGRESSION: This is working fine with Xamarin.Android 4.7.9
@narayanp: Please provide diagnostic build output.
Open the Developer Command Prompt for VS, then:
> cd path\to\your\project
> msbuild /t:Install /p:Configuration=Release Project.csproj /v:diag > build.txt
Then attach build.txt.
The Device Deployment logs would also be useful:
Does this happen on OS X?
I have checked the same issue after uninstalling Xamarin.Android 4.7.10 and iOS for VS 1.2.121 and again installed these, Now I am successfully able to deploy application on Physical device Samsung S3.
Hence closing this issue.
Ok Prashant thanks for checking. On possibility is we may have some sort of issue with upgrading from 4.7.9 to 4.7.10. Can you try the original upgrade path explicitly and see if it happens after that?
Today we have checked this issue by updgrading xamarin.Android from 4.7.9 to 4.7.10 and we are able to deploy application successfully on device S3.
Hence closing this issue. Changing its status to verified.