Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.4.X
Votes
0
Found in
2019.4.3f1
Issue ID
1264496
Regression
No
[iOS] Using custom storyboard as a launch screen with multitasking enabled fails the archive validation for App Store
Steps to reproduce:
1. Open attached project (test-storyboard-error.zip)
2. Make sure that these Player Settings are set as follows:
- Resolution and Presentation/Requires Fullscreen is disabled
- Splash Image/Use Storyboard for Launch Screen is enabled and test.storyboard is selected
3. Build for iOS
4. Archive the Xcode project
5. When the app is archived, select the build and click 'Validate App' in the organizer window
Actual result: App validation will fail because Xcode fails to find the specified launch screen value.
Workaround: Removing .storyboard extension from the Info.plist "UILaunchStoryboardName" value
Reproduced with: 2018.4.24f1, 2019.4.3f1, 2020.1.0b12
Not reproducible with: 2020.2.0a16 (was fixed by moving 'Use Storyboard for Launch Screen' option to the Launch Screen type dropdown)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment