Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X
Votes
3
Found in
6000.0.22f1
Issue ID
UUM-83822
Regression
No
[Android]Builds fail when multiple "Unable to parse file" errors are thrown when building using "Build And Run" for a Custom Build Profile in a specific project
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Build and run the Player (File > Build And Run)
3. Observe the Console Window
Expect result: No errors are thrown and the build is launched on the connected device
Actual result: Two “Unable to parse file Assets/Settings/Build Profiles/Android TEST.asset: [Parser Failure at line 82: Expected closing '}']” errors are thrown and the builds fail
Reproducible with: 6000.0.22f1
Could not test with: 2021.3.44f1, 2022.3.51f1 (Editor Streams do not contain Build Profiles)
Workaround: First build the Player then launch it on your device without using the “Build And Run”
Note: Not reproducible when building for the standard Android Build Profile or other Custom Build Profiles
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 "UnityWebRequest.result" of the "UnityWebRequestTexture.GetTexture" method changes when accessing "UnityWebRequest.downloadHandler" texture
- Slider rounding does not allow setting certain valid numbers as Values when Low and High Values not set to default
- UI Builder Canvas has too big resizing zone on the outside of the canvas
- GetCurrentAnimatorClipInfoCount() and GetNextAnimatorClipInfoCount() return 0 when animator is in transition
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
christopheAS
Nov 10, 2024 15:21
Small clarification:
The issue appeared in my case after having added player settings override to my build profiles. The formatting of some YAML lines, split on several lines in the serialization format, seems to be the root cause of the issue. Fixing the files manually solves the issue temporarily but it comes back anytime the profile file is resaved. I'm on macOS if that makes a difference
christopheAS
Nov 10, 2024 15:18
Problem may appear during builds but also appears when loading any projects with profiles
VirtualMaestro
Nov 10, 2024 13:48
I can confirm such behavior (the only thing is this happens not only for the Android platform, but basically for any platform when the build happens).
Also, in my case I have two 'Build profiles' (ServerWin and ClientWin) and despite of which profile I'm building it throws two errors per profile:
"
Unable to parse file Assets/Settings/Build Profiles/ServerWin.asset: [Parser Failure at line 72: Expected closing '}']
Unable to parse file Assets/Settings/Build Profiles/ClientWin.asset: [Parser Failure at line 70: Expected closing '}']
Unable to parse file Assets/Settings/Build Profiles/ServerWin.asset: [Parser Failure at line 72: Expected closing '}']
Unable to parse file Assets/Settings/Build Profiles/ClientWin.asset: [Parser Failure at line 70: Expected closing '}']
"
I experienced this with versions:
- Unity 6 (6000.0.25)
- Unity 6 (6000.0.26)
The full log looks like this:
" Unable to parse file Assets/Settings/Build Profiles/ServerWin.asset: [Parser Failure at line 72: Expected closing '}']
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) "
Thanks