I just upgraded 4.6.0 to 4.6.1, and the “no iPhone 6support” app I am working on suddenly seems to support iPhone 6 launch images, even though I deleted them from the Images.xcassets file in Xcode. Does Unity since 4.6.1 force those launch images somehow?
Reason is we are using a 3rd part ad network sdk (adfurikun), and I always had to delete those iph6 launch screens on every iOS build (because the app does not support iph6 screens). If I didn’t delete those images, the resolution would be “incorrect” for the app - so the ad banner would display incorrectly. So I just deleted those iph6 launch images and the ad banners worked ok.
Now with 4.6.1 no matter what I do the resolution of the app seems to support iPhone 6, and I always get those banners displayed incorrectly.
I don’t know the reason for this but I just suspect that somehow Unity “sneaks in” iPhone 6 launch screens no matter what since 4.6.1… maybe through some setting other than Images.xcassets. Or the problem is really somewhere else…
I found the problem, and yes there is a difference between 4.6.0 and 4.6.1. Not confirmed though but with 4.6.1 the info.plist that’s generated there are a few launch images defines for iPhone 6 and iPhone 6 Plus that manually need to be deleted, unless youre actually wanting to support these devices’ native resolution. It’s not enough just deleting the actual images and entries from the Images.xcassets file, the entries in the info.plist must be deleted too. Not double checked though I assume that 4.6.0 did not add these entries to the info.plist.
It looks like Unity 4.6.1 adds UILaunchImages to the Target → Info settings in the resulting XCode project. Usually Xcode will automatically generate the UILaunchImages array in your plist based on the images specified in the Launch Image Catalogue. However, when UILaunchImages is present in your project, it overrides the usual automatic output.
I recommend just deleting UILaunchImages from your target to work around this issue.
Ok thanks that’s an easier solution. So 4.6.0 did not add UILaunchImages to Info.plist? Why does 4.6.1 need to? The Image Catalogue should be enough… or perhaps this is due to some arcane backwards compatibility issue.
Still the problem is that this must be done on EVERY build from Unity. I’ll have to figure out how to use plistbuddy to remove this automatically after every build…