Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.1.15f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113628
Regression
No
"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
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment