Search Issue Tracker
Fixed
Fixed in 6000.3.11f1, 6000.4.0b11, 6000.5.0a8, 6000.6.0a1
Votes
0
Found in
6000.3.7f1
6000.4.0b7
6000.5.0a6
6000.6.0a1
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”
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a8):
Landed in 6000.5.0a8
Resolution Note (fix version 6000.4.0b11):
Fixed in 6000.4.0b11
Resolution Note (fix version 6000.3.11f1):
Fixed in 6000.3.11f1