Wanted to test the metal support, so I updated to todays 4.6.2p2 (free). When I try to run on my iOS device, I get a crash “You are using Unity iPhone Basic. You are not allowed to remove the Unity splash screen from your game” even though I’m not touching the splash screen image. I tried this with an existing project upgrade and a new project built with this version. Same error.
this check seems to be very fragile, was broken several times before
got the same error
pls report it, maybe next week it will be fixed
I have the same problem. Did you find a solution?
No. Maybe next weeks patch will fix it.
I solved the problem.
After you generate the project delete these files from the project:
LaunchScreenImage-Landscape.png
LaunchScreenImage-Portrait.png
LaunchScreen.xib
Then select the Unity-iPhone target from your Targets list and select the Info tab.
Delete the key UILaunchStoryboardName~iphone from the Custom iOS Target Properties.
Clean your project and build.
Now it should work because it takes the correct screenshots from the Images.xcassets file.
6 Likes
Same problem here, very frustrating =/
The Info tab was empty for me for some reason. I removed that key directly from Info.plist, but then the build fails because XCode can’t find “LaunchScreen.xib”.
Mmmmm. strange… it should work because Info.plist file is exactly the same.
Did you remove the row completely ? You have to select the row with key UILaunchStoryboardName~iphone and press the delete key on your mac.
Did you delete the app from the device? Sometimes XCode does not update the plist file in the app if you don’t do a clean install.
By the way I realized that you just need to remove the UILaunchStoryboardName~iphone key from the Info.plist file.
Don’t delete the files… it’s useless.
3 Likes
Tried it once again and it worked now. Weird. Thanks!
Thanks for the solution kaharoth!
Yes, thanks kaharoth. Especially since the problem still persists in the 4.6.3 release.
Joining in to say thanks as well.
Also when testing through TestFlight and someone describes a problem as “shows a gray screen then crashes” they’ll be talking about this.
It wasn’t obvious to me whether the message about the missing splash shows up on the device or in XCode so I didn’t make the connection at first.
Thank you, fixed it
Thank you kaharoth, this fixed my build too! A little bit of delete sure does wonders.
Run into the same problem after updating to 4.6.3 and the solution from kaharoth fixed it, thanks!
This is not the first time this check caused issues, seems like a never ending cause for regressions.
Anyone filed the ticket yet?
Unity said somewhere it is fixed already for 4.6.3p1, so we just have to wait.
I have the same problem in 4.6.3f1 release. When build for iPhone the message “You are using Unity iPhone Basic. You are not allowed to remove the Unity splash screen from your game” appears. For iPad everything is OK.
As I see kaharoth solution, developers create build for PRO version and forget to remove custom splash screens 
Two app updates of mine with the fix proposed on this thread have been approved by Apple
Doing just this didn’t work for me, then I accidentally came across somewhere else I needed to remove the LaunchScreen stuff.
In XCode → select project → Build Phases → Copy Bundle Resources → Remove the 3 LaunchScreen files → Clean and Build.
After doing this additional step, it worked for me.
Not working. Unity. Fix this issue please. It is a high-priority showstopper bug right now. In the future you need to to test your every Unity build to be able to successfully make a build on every platform.
Please be rigorous and organized in your QA.
Have you tried with 4.6.3p1 ???
Detailed information like “Not working” is going to be very helpful for Unity to fix it. How about stating which version you’re talking about since as it says 5 posts up “already for 4.6.3p1,” yet you didn’t even clarify what version you’re talking about.
Note - if you want Unity to be “rigorous and organized in their QA” to catch every possible bug with all the work they’ve got going on right now expect to wait MONTHS for a fix… You can’t have quick fixes and super rigorous QA - not going to happen.
1 Like