Search Issue Tracker
In Progress
Fixed in 2023.2.0b11, 2023.3.0a3
Votes
0
Found in
2023.2.0b3
2023.3.0a2
2024.1.0a1
Issue ID
UUM-44326
Regression
Yes
[iOS] Images used in Relative & Constant launch screens aren't included in the generated Xcode build, resulting in the Xcode build failing
Steps to reproduce:
# Open attached project (splash-test.zip)
# Switch to iOS platform
# Make sure that 'Unity Launch Screens' are set up with the included images (Player Settings/Splash Image)
# Build for iOS
# Open the generated Xcode project and try to build via Xcode
Expected result: Launch screen images are included in Xcode project, the build succeeds and the image is displayed on device.
Actual result: Launch screen images are missing & building via Xcode fails because of that.
Note: Same happens with relative and constant launch screens (as stated in the title). Using 'Default' launch screen does include the default, black-ish images in the resulting build.
Reproduced with: 2023.2.0b3
Not reproducible with: 2022.3.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment