Bug 19568 - Target Device
Summary: Target Device
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 3.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-05-06 12:54 UTC by brandon
Modified: 2016-12-22 18:28 UTC (History)
7 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 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 FIXED

Description brandon 2014-05-06 12:54:24 UTC
Whenever I save my project or open it - the Target iOS Device always changes to iPhone Retina. THis also occurs in Xamarin Studio for the mac
Comment 1 Sadik Ali 2014-05-07 03:59:38 UTC
I have tried this issue and unable to reproduce it. Steps I followed to reproduce it mentioned below:

1. I created a project in VS 2013. Select iOS pad simulator and run it. Then I save it and close the solution. Then Again open the project. Screencast regarding same is : http://screencast.com/t/BTrFz6t7

2.  I created a project in VS2012. Select iOS pad simulator and save it. Close the solution and open the project. Screencast regarding same is :  http://screencast.com/t/5AxmOL54K9

3. I created a project in Mac and followed the steps 1 and 2 both in Mac.
Screencast regarding same is :  http://www.screencast.com/t/oQ8Gj46qNZM

Win Environment Info : 
Microsoft Visual Studio Professional 2012
Version 11.0.50727.1 RTMREL
Microsoft .NET Framework
Version 4.5.50938
Installed Version: Professional
Xamarin.iOS   2.0.84.0 (fc21a4a77bcd611d9b4d0c5b2bbf8104e4349c33)
Visual Studio extension to enable development for Xamarin.iOS

Mac Environment Info
=== Xamarin Studio ===

Version 4.2.3 (build 60)
Installation UUID: 6ea47b0d-1852-4aaf-808d-373ff0a5002b
Runtime:
   Mono 3.2.6 ((no/9b58377)
   GTK+ 2.24.23 theme: Raleigh
   GTK# (2.12.0.0)
   Package version: 302060000

=== Apple Developer Tools ===

Xcode 5.1 (5084)
Build 5B130a

=== Xamarin.iOS ===

Version: 7.2.0.2 (Trial Edition)
Hash: 58c3efa
Branch: 
Build date: 2014-10-03 18:02:26-0400

=== Xamarin.Android ===

Version: 4.12.4 (Trial Edition)
Android SDK: /Users/jatin66/Desktop/Backup/android-sdk-macosx
   Supported Android versions:
       1.6   (API level 4)
       2.1   (API level 7)
       2.2   (API level 8)
       2.3   (API level 10)
       3.1   (API level 12)
       3.2   (API level 13)
       4.0   (API level 14)
       4.0.3 (API level 15)
       4.1   (API level 16)
       4.2   (API level 17)
       4.3   (API level 18)
       4.4   (API level 19)
Java SDK: /usr
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)

=== Xamarin.Mac ===

Xamarin.Mac: 1.8.0.8

=== Build Information ===

Release ID: 402030060
Git revision: 30c4afc300c2a39ec5300851357ce02e49dd217e
Build date: 2014-03-05 22:09:33+0000
Xamarin addins: f8a9589b57c2bfab2ccd73c880e7ad81e3ecf044

=== Operating System ===

Mac OS X 10.9.2
Darwin Jatin66s-iMac.local 13.1.0 Darwin Kernel Version 13.1.0
   Thu Jan 16 19:40:37 PST 2014
   root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64

Please suggest me What I need to do to reproduce this issue.
Comment 2 Jose Gallardo 2016-12-22 18:28:46 UTC
Hi,
Marking the bug as resolved fixed (on C9/current alpha).
Please feel free to reopen it if you can still reproduce the issue with current bits.
Thanks!