This article presents a scenario where Unity Build Automation (UBA) builds start unexpectedly showing the Unity splash screen, while older builds and mobile targets behave correctly. Investigation revealed the issue was caused by a limitation of the legacy licensing fallback, which does not traverse parent-child organizations. Because the Pro entitlement resides in the parent organization, the builder detected “Pro License: NO.” Using Unity 6 and disabling the splash in Player Settings provides a workaround.
Symptoms:
- UBA builds suddenly start displaying the Unity splash screen on startup.
- The build output in the log indicates “Pro license: NO” even though the organization has a Pro entitlement via a parent company.
Cause:
- The legacy licensing system only checks the immediate organization running the build and does not traverse parent-child organization structures.
- Because the Unity Pro license is assigned to the parent organization rather than the child organization running the build, the legacy check fails and sets "Pro License: NO", causing the Unity splash screen to appear.
Resolution:
- As a practical workaround, open the project in Unity 6, where a Pro license is not required to disable the splash screen.
- In Unity 6, navigate to Edit > Project Settings > Player > Splash Image and uncheck “Show Splash Screen.”
- Commit that change to source control and trigger a new UBA build so the updated splash settings take effect.
- Alternatively, you can transfer the project to the parent organization with the Unity Pro entitlement.
More Information:
For more information about configuring the splash screen that displays when your application starts, please check this documentation entry.