Bug 38239 - NSBundle.MainBundle.InfoDictionary["UILaunchImages"] not available
Summary: NSBundle.MainBundle.InfoDictionary["UILaunchImages"] not available
Status: RESOLVED DUPLICATE of bug 38206
Alias: None
Product: iOS
Classification: Xamarin
Component: MSBuild ()
Version: XI 9.4 (iOS 9.2)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2016-02-01 08:15 UTC by Thomas Van den Bossche
Modified: 2016-02-01 19:50 UTC (History)
2 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 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 DUPLICATE of bug 38206

Description Thomas Van den Bossche 2016-02-01 08:15:37 UTC
After upgrading to the latest version the NSBundle.MainBundle.InfoDictionary no longer contains an entry for UILaunchImages.

Has this been removed? Is there a workaround?

Xamarin Studio
Version 5.10.2 (build 56)
Installation UUID: c8d9d174-a2c8-4101-870c-d07ece81c653
Runtime:
	Mono 4.2.2 (explicit/996df3c)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402020030

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

Xamarin.Android
Version: 6.0.1.10 (Business Edition)
Android SDK: /Users/thomasvdb/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.0   (API level 21)
		6.0   (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 23.0.0

Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

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

Apple Developer Tools
Xcode 7.2 (9548)
Build 7C68

Xamarin.Mac
Version: 2.4.1.6 (Starter Edition)

Xamarin.iOS
Version: 9.4.1.24 (Business Edition)
Hash: 47eb74b4
Branch: master
Build date: 2016-01-20 17:06:01-0500

Build Information
Release ID: 510020056
Git revision: bb74ff467c62ded42b7b7ac7fdd2edc60f8647b0
Build date: 2016-01-26 16:24:41-05
Xamarin addins: 8b797d7ba24d5abab226c2cf9fda77f666263f1b
Build lane: monodevelop-lion-cycle6-c6sr1

Operating System
Mac OS X 10.11.3
Comment 1 Rolf Bjarne Kvinge [MSFT] 2016-02-01 09:45:44 UTC
This is not something that should change.

Does the Info.plist in your .app contain an entry for UILaunchImages?
Comment 2 Thomas Van den Bossche 2016-02-01 10:23:02 UTC
The info.plist is configured to use the Assets Catalog.

<key>XSLaunchImageAssets</key>
<string>Resources/Images.xcassets/LaunchImage.launchimage</string>
Comment 3 Rolf Bjarne Kvinge [MSFT] 2016-02-01 10:25:18 UTC
@Jeff, is this something you're familiar with?
Comment 4 Jeffrey Stedfast 2016-02-01 13:25:16 UTC
This is another duplicate of that bug that kzu just fixed
Comment 5 Sebastien Pouliot 2016-02-01 18:29:57 UTC
@Thomas, we believe this issue is fxied with our just released hotfix. Can you please:

a. update to XI 9.4.1.25 (now on the stable channel);
b. clean your solution;
c. rebuild and test if this is fixed.

Thanks!
Comment 6 Thomas Van den Bossche 2016-02-01 19:35:45 UTC
@Sebastien The hotfix indeed solved the issue. Thank you for the quick fix!
Comment 7 Sebastien Pouliot 2016-02-01 19:50:12 UTC
Thanks for confirming this!

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