Bug (case #1161290) Parser Failure at line X: Expect ':' between key and value within in 2019.3.0

I got this when updating from 2018.2 to 2019.3

It seems somewhat related to new lines that the new YAML parser handles differently.

My fix was to simply rebuild affected assets, so it wasn't catastrophic.
But, I can see it breaking projects heavily if not addressed.
I tested on a4 and a5 and submitted a bug on 08/06. Case # is 1161290

I'm posting here to get some extra visibility, as QA has yet to reply to the bug report.


Saw someone else mentioning this here: https://forum.unity.com/threads/i2-...olution-for-unity.231226/page-15#post-4601569

I2 localization bakes strings into an scriptable object, so it is a good candidate to trigger this bug.
My bug report includes a small test project with an asset extracted from my own project. The issues reproduces every time.

 

I am still getting this BUG!!
Its the I am using 2019.3.0f6
Also some of my Tilemaps Colliders wont work my player can walk through them on certain chunks and can walk on some areas.

 

Thank you for reply, so I have also made a video and posted a forum, here is the link to that:-
https://forum.unity.com/threads/tilemap-colliders-wont-work-v-2019-3-0f6.824691/

For some reason whenever i get that bug my tile map collider wont work, and after trying some different things I found out that it is caused because in the Tilemap I have Cell gap set to (x: -0.0001, y: -0.0001) And the reason why i have cell gaps because Anti Aliasing wont work on my Pixel art game i have disabled it in my Renderer and I am still getting the Lines which are caused when anti aliasing is On.

 

Hello. Me have same bug when using:

Code (CSharp):

1. UnityEditor.AssetDatabase.LoadAssetAtPath(path, type) as T;

When we load asset from editor some files are broken. On Player everything works fine. Attached full log. We use: Unity 2019.3.6f1, Odin. On Unity 2019.2.21f1 everything was fine.

 

What is the status of this? Many of my scriptable objects see this error in Editor. It doesn't seem to affect runtime though as far as I can tell. Im on Unity 2019.3.12f1. I recently upgraded from 2018.4 LTS

 

I am getting this error as well in Unity 2019.3.13f1. Luckily I have github to go revert back.

 

@harryr I've had this error with a single animation asset in 2019.4.5f1 after upgrading from 2019.2.22f1. I've just submitted a bug for this with the asset attached, mentioning this forum thread - case number: 1268628.

 

For anyone else that comes across this, here is my bug for this: https://issuetracker.unity3d.com/is...-a-specific-animation-file-to-a-unity-project

@harryr Making a random change to the animation then undoing it resolved the issue.

 

error still present in unity 2019.3.15f1

 

Mine happen while I'm trying to apply prefab on my tilemap asset.

 

Just encountered this for the first time in 2019.4. I've been working in this project for two months without issue, until now.

 

Same for me first time since 8 mont of work on my project on Unity 2020.2.1f1, after remove unused keyword shader

 

Doing the 2d game kit tutorial and Ellen keeps falling through the ground on one of my maps and I fear I have to create this level from the ground up again if this doesn't have a fix..

 

Oh and one more thing, the colliders work if I remove one tile from the map, then if I go to the Start scene and press start then the first scene loads and has the problem again.

 

error still present in unity 2019.4.9f1

 

Hello I am gill.

Today I faced a very weird problem when I opened my project . I see all my gameobject in my (city 1 scene) are merged and all the child objects are detached from the parent game object and some are deleted . I don't know how this happens.
And this error is shown in the console
( parser failure at line 134041: expected closing )
But it was my luck that I had saved the copy of the same scene with another name.
So pls help me to solve this problem and I don't know about this error
Pls help me