Unity Issue Tracker - "Build Automation requires your project to be configured with Unity Cloud" warning is still shown in Build Profiles when the project is linked to the Unity Cloud
Fixed
UUM-113628
"Build Automation requires your project to be configured with Unity Cloud" warning is still shown in Build Profiles when the project is linked to the Unity Cloud
Unity: Build Settings Window
Open
6.4.X
6.3.X
Fixed
6.5.X
6000.5.0a1
Won't Fix
6.2.X
6.1.X
Unity 6000.2 has reached its end of life and will not receive further updates. If you need additional fixes, please upgrade to a newer Unity version.
Cancelling: the 6000.1 version has reached its end of life. If you need additional fixes, please upgrade to a newer Unity version.
Steps to reproduce:
Create a new Unity project using the Universal 3D template without linking it to the Cloud
Install the Build Automation package
Open the Build Profiles window (File > Build Profiles)
Click the "Add Build Profile" button
Select macOS platform and click "Add Build Profile" button
Press the "Add Settings" button and select "Build Automation Settings"
Click the "Configure Unity Cloud" button
Select an organization
Select "Create a new cloud project"
Click the "Create new cloud project and link to Unity project"
Observe the Build Profiles window
Actual results: "Build Automation requires your project to be configured with Unity Cloud" warning is still shown when the project is already configured with Unity Cloud
Expected results: "Build Automation requires your project to be configured with Unity Cloud" warning is not shown as the project is already configured with Unity Cloud
Reproducible with versions: 6000.1.15f1, 6000.2.0f1, 6000.3.0a4
Can’t test with versions: 6000.0.54f1 (due to Build Automation settings not existing in the Build Profiles window)
Tested on (OS): Ubuntu 24.04, macOS Silicon Sequoia 15.5
Notes:
Closing and reopening the Build Profiles window makes the warning disappear
Unlinking the project does not make the warning appear until the Build Profiles window is reopened
Prioritise and Follow this issue
Have a workaround or additional info about this issue?