Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.54f1
6000.1.15f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113621
Regression
No
Unlinking Unity project from cloud throws "DirectoryNotFoundException" errors when the Build Automation package is installed
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"
- Click the "Unlink project" button
- Observe the Console window
Actual results: "DirectoryNotFoundException" errors are thrown every second
Expected results: No errors or warnings are thrown
Reproducible with versions: 6000.0.54f1, 6000.1.15f1, 6000.2.0f1, 6000.3.0a4
Tested on (OS): macOS Silicon Sequoia 15.5
Notes:
- Does not reproduce without the Build Automation package
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Initialization Mode" and "Update Mode" drop-downs are not localized in the Custom Render Texture asset
- Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
- Section separator renders in the wrong place in Search Journaling and Archetypes windows
- [D3D12][UWP] Additional persistent shadows are drawn in UWP builds when using D3D12
- Search Journaling window link to Journal Manager documentation isn’t working
Add comment