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 GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Add comment