Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133786
Regression
Yes
Player build fails with "Failed to open" error when scene is located in a package
Reproduction steps:
1. Open the attached "bug-build-package-scene.zip" project
2. Make a build by using the menu item: Unity Support > Build Player
3. Observe the Console window
Actual result: Build fails with a "Failed to open" error
Expected result: Build succeeds and no errors are thrown in the Console
Reproducible with: 6000.2.0a7, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Not reproducible with: 6000.0.67f1, 6000.2.0a6
Reproduced on: macOS 15.7.3 Arm64 (reporter), Windows 11
Not reproducible on: No other environments tested
Notes:
- To reproduce on Windows, change line 14 in "BuildScript.cs" to: “BuildPipeline.BuildPlayer(scenes, buildLocation, BuildTarget.StandaloneWindows64, BuildOptions.None);”
- Error that is thrown in the console when build fails: “Error building Player: Failed to open”
- When building a project in 6000.0.67f1 or 6000.2.0a6, you get a warning “Invalid AssetDatabase path”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
Add comment