Search Issue Tracker
Fixed
Fixed in 6000.0.33f1, 6000.1.0a9, 7000.0.0a23
Votes
1
Found in
6000.0.22f1
Issue ID
UUM-83673
Regression
No
“Unable to parse file" error is thrown when opening a specific project with Custom Build Profiles
Reproduction steps
1. Open the attached “ASDQWE” project
2. Observe the Console Window
Expected result: No error is thrown
Actual result: “Unable to parse file Assets/Settings/Build Profiles/Android TEST.asset: [Parser Failure at line 80: Expected closing '}']” error is thrown
Reproducible with: 6000.0.22f1
Could not test with: 2021.3.44f1, 2022.3.51f1 (Build Profiles are not available for these Editor Streams)
Reproducible on: MacOS 14.6.1 (Intel), Windows 10 (user’s)
Not reproducible on: No other environment tested
Notes:
- Opening the Build Profile Window (File > Build Profiles) throws the “Unable to parse file Assets/Settings/Build Profiles/Android Publish.asset: [Parser Failure at line 79: Expected closing '}']” error
- The errors are thrown only once but appear again when reopening the project
- Not reproducible with other Custom Build Profiles
- The Build Profiles were created for the Android Profile
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
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
Resolution Note (fix version 7000.0.0a23):
Verified fixed.
Resolution Note (fix version 6000.0.33f1):
fix unable to parse build profile error.