Bug 4925 - Splash screen wrong or over processed in 5.3.3
Summary: Splash screen wrong or over processed in 5.3.3
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.9.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-05-07 11:36 UTC by Nic Wise
Modified: 2012-05-11 15:49 UTC (History)
1 user (show)

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

All the screenshots. (386.22 KB, application/zip)
2012-05-07 11:36 UTC, Nic Wise
5.2.11 screenshot (working) (86.78 KB, image/png)
2012-05-07 11:36 UTC, Nic Wise
5.3.3 screenshot (b0rked) (63.76 KB, image/png)
2012-05-07 11:37 UTC, Nic Wise
info.plist (1.30 KB, application/octet-stream)
2012-05-07 12:51 UTC, Nic Wise

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 Nic Wise 2012-05-07 11:36:19 UTC
Created attachment 1818 [details]
All the screenshots.

MD 2.9.5 (and also 2.8.x)
MT 5.3.3 (and also 5.2.11)

The Default@2x source is the same in both cases, however in 5.3.3, it shows up pixelated and generally "wrong". It looks either overprocessed, or the processing took the non-retina version, and renamed it @2x.

There is no difference in the source files. If I go back to the old version of MT/MD (5.2.11) it all goes back to normal.

Shots attached. I can't notice it in any other media files, just the Default@2x.png.

In the .app, the @2x and normal pngs are expected size - 30k and 60k.

Attached is a ZIP with:

1. A shot from the loading on 5.2.11 and 5.3.3 (-screenshot-5.x.x-)

2. The processed png's from both versions (ie, from in the .app, TestFlight/AdHoc release profile) (-appbundle-5.x.x-)

3. The original source images from the project (-original-)

Names should make sense :) I've uploaded the two screenshots directly, so you can see it without getting the zip file down.
Comment 1 Nic Wise 2012-05-07 11:36:54 UTC
Created attachment 1819 [details]
5.2.11 screenshot (working)
Comment 2 Nic Wise 2012-05-07 11:37:22 UTC
Created attachment 1820 [details]
5.3.3 screenshot (b0rked)
Comment 3 Mikayla Hutchinson [MSFT] 2012-05-07 12:27:53 UTC
Looks like a dup of bug 4607, but that was in MD. Are you sure this is related to the MT version and not the MD version?
Comment 4 Nic Wise 2012-05-07 12:32:57 UTC
No, I always install them as a pair. (the bug IS reported in MD, BTW!) I've not tried 5.3.3 with 2.8... But it sounds about right tho. Can try again in the next 2.9 beta.
Comment 5 Jeffrey Stedfast 2012-05-07 12:39:11 UTC
The cause of the problem in bug #4607 was that the resulting Info.plist in the app bundle had a UILaunchImageFile key with an empty value. I'm not entirely sure why that caused iOS to choose the wrong launcher image, but it did.

Nic: can you look at your Info.plist file in the app bundle and check to see if it has that key?
Comment 6 Nic Wise 2012-05-07 12:51:16 UTC
It is present, and it is blank. plist attached.
Comment 7 Nic Wise 2012-05-07 12:51:54 UTC
Created attachment 1822 [details]
Comment 8 Jeffrey Stedfast 2012-05-11 15:49:04 UTC
Okay, then this should be resolved in 3.0 because we no longer write that key-value to the Info.plist if the value is empty.