Bug 44868 - VS 2013 debug mode deployment on Samsung device no longer works
Summary: VS 2013 debug mode deployment on Samsung device no longer works
Status: RESOLVED DUPLICATE of bug 45543
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 7.0 (C8)
Hardware: PC Windows
: Normal normal
Target Milestone: master
Assignee: Jonathan Pryor
Depends on:
Reported: 2016-09-29 10:20 UTC by Larrimar Tia
Modified: 2017-08-23 20:44 UTC (History)
2 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 Larrimar Tia 2016-09-29 10:20:54 UTC
# Steps to reproduce
Run a xamarin for android app on actual Samsung device on debug mode.

# Expected behavior
Application will run on Samsung device while VS 2013 is on debug mode

# Actual behavior
VS deploys successfully but installed app on device suddenly closes 

# Supplemental info (logs, images, videos)
No screenshots available, the OS simply displays an error message 

# Test environment (full version information)
SM-G9287C (Android 6.0 - API 23)
Comment 2 Jonathan Pryor 2016-10-24 18:31:56 UTC
Perhaps this is a DUPE of Bug #45543?
Comment 3 Cody Beyer (MSFT) 2017-08-23 20:44:25 UTC
Comment 2

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