Bug 35107 - Xib UI differences when updating a classic API project to unified API
Summary: Xib UI differences when updating a classic API project to unified API
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 9.0 (iOS9)
Hardware: PC Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-10-20 14:50 UTC by John Miller [MSFT]
Modified: 2016-04-12 15:16 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Library, still Classic API (11.95 KB, application/zip)
2015-10-20 14:51 UTC, John Miller [MSFT]
Details
Library, with app projects, migrated to Unified and created as Unified (19.31 KB, application/zip)
2015-10-20 14:51 UTC, John Miller [MSFT]
Details
Screenshot as classic, pre migration. (36.65 KB, image/png)
2015-10-20 14:52 UTC, John Miller [MSFT]
Details
Screenshot as unified (29.61 KB, image/png)
2015-10-20 14:52 UTC, John Miller [MSFT]
Details


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 NORESPONSE

Description John Miller [MSFT] 2015-10-20 14:50:49 UTC
**Overview:**

   When migrating a Classic API project to Unified, the UI designed in .xib files appears difference once on the Unified API.
   This was noticed while a customer had the following scenario:

- Shared iOS Library project containing views (.xibs). 
- This shared project was migrated from classic -> unified.
- Classic API project that was using the shared library. Now needed to be updated to Unified. 
- Another project, this time created with the Unified template (not migrated) which also uses the shared library. 

The Unified (not migrated) looks different than the Classic->Unified project using the same shared iOS Library and View. E.g. The font sizes appear a little larger and the controls are are slightly larger, etc.

**Steps to Reproduce:**

   In an attempt to reproduce this, I started with a shared library that has a .xib in it (classic api). I just added some controls to the center (button, two text boxes and a label). 

   I consumed this in a classic API project and show the view. Attached is the screenshot for this. 
   Then, migrated this to Unified, which required the library be migrated too. 
   Created a new unified project from the template and consumed the migrated library. 
   Ran the new unified project and displayed the view. It looks difference, even though the view has not changed in code or layout. Attached is the screenshot. 

**Actual Results:**

   See screenshot differences. http://screencast.com/t/hxdDg5sc

**Expected Results:**

   The layouts should be exactly the same. 

**Build Date & Platform:**

   === Xamarin Studio ===

Version 5.10 (build 811)
Installation UUID: e01c3049-a2d2-4e0a-aad8-afe6fb627c4d
Runtime:
	Mono 4.2.1 (explicit/804ddbc)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402010060

=== Xamarin.Profiler ===

Version: 0.20.0.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Xamarin.Android ===

Version: 6.0.0.8 (Business Edition)
Android SDK: /Users/johnmiller/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
		4.4   (API level 19)
		5.0   (API level 21)
		5.1   (API level 22)

SDK Tools Version: 24.4.0
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 23.0.1

Java SDK: /usr
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

=== Xamarin Android Player ===

Version: 0.6.2
Location: /Applications/Xamarin Android Player.app

=== Apple Developer Tools ===

Xcode 7.0 (8227)
Build 7A220

=== Xamarin.iOS ===

Version: 9.2.0.84 (Business Edition)
Hash: b5396c2
Branch: master
Build date: 2015-09-30 15:22:15-0400

=== Xamarin.Mac ===

Version: 2.4.0.79 (Business Edition)

=== Build Information ===

Release ID: 510000811
Git revision: 34cd31ea72536afab530c14d9220b286075e83cd
Build date: 2015-09-30 10:40:37-04
Xamarin addins: 8e6fccfc0c19a7e0b7b11be925f09751d827eb5c
Build lane: monodevelop-lion-cycle6

=== Operating System ===

Mac OS X 10.10.5

**Additional Information:**

   I've attached the project still as classic so that it's easier to reproduce. I've attached a second copy thats migrated and has the unified project in it.
Comment 1 John Miller [MSFT] 2015-10-20 14:51:10 UTC
Created attachment 13459 [details]
Library, still Classic API
Comment 2 John Miller [MSFT] 2015-10-20 14:51:44 UTC
Created attachment 13460 [details]
Library, with app projects, migrated to Unified and created as Unified
Comment 3 John Miller [MSFT] 2015-10-20 14:52:22 UTC
Created attachment 13461 [details]
Screenshot as classic, pre migration.
Comment 4 John Miller [MSFT] 2015-10-20 14:52:42 UTC
Created attachment 13462 [details]
Screenshot as unified
Comment 5 Sebastien Pouliot 2015-10-20 21:09:55 UTC
Based on the screenshot (look at the status bar for an hint) you should double check the launch image for both apps (can't check now). That will affect the window size (and how it's scaled).
Comment 6 Sebastien Pouliot 2016-04-12 15:16:21 UTC
We have not received further information and will assume this is not an issue anymore. If you can still affected by this please re-open the bug and include the requested information. Thanks.