Search Unity

  1. Unity 2020.1 has been released.
    Dismiss Notice
  2. We are looking for feedback on the experimental Unity Safe Mode which is aiming to help you resolve compilation errors faster during project startup.
    Dismiss Notice
  3. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice

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

Discussion in '2019.3 Beta' started by SugoiDev, Jun 14, 2019.

  1. SugoiDev

    SugoiDev

    Joined:
    Mar 27, 2013
    Posts:
    325
    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.
     
    all_iver and Peter77 like this.
  2. harryr

    harryr

    Unity Technologies

    Joined:
    Nov 14, 2017
    Posts:
    38
    I've given the repro a look over and this issue should be fixed up in 2019.3a6 :)

    Will pass this info onto our QA for them to confirm, thanks for submitting the bug!
     
    SugoiDev and Peter77 like this.
  3. Meepo0

    Meepo0

    Joined:
    Nov 24, 2017
    Posts:
    28
    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.
    upload_2020-2-8_17-36-37.png
     
    pkusalas likes this.
  4. harryr

    harryr

    Unity Technologies

    Joined:
    Nov 14, 2017
    Posts:
    38
    Hi @Meepo0, can you confirm if this issue is still present in the latest 2019.3 version?
    If it is could you please log a bug with the H4.unity scene attached for me to look at?
     
  5. Meepo0

    Meepo0

    Joined:
    Nov 24, 2017
    Posts:
    28
    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.
     
  6. huran438

    huran438

    Joined:
    Jun 12, 2013
    Posts:
    11
    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.



    upload_2020-3-24_20-58-34.png
     

    Attached Files:

    Last edited: Mar 24, 2020
  7. newatlanta19006

    newatlanta19006

    Joined:
    Feb 23, 2019
    Posts:
    7
    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
     
  8. harryr

    harryr

    Unity Technologies

    Joined:
    Nov 14, 2017
    Posts:
    38
    @Meepo0 @huran438 @newatlanta19006
    In order for me to help with the issue I'll need a copy of the asset(s) that trigger this console error.
    This is an "I don't know how to parse this asset" error so unfortunately we can't tell what's wrong with the file until we have a look at the contents.

    If you could please log a bug with this forum post linked that'd be great, it's not required for you to attach your whole project, just the asset(s) that cause this error and your editor version :)

    This is correct, at runtime all assets are binary
     
  9. holyfot

    holyfot

    Joined:
    Dec 16, 2016
    Posts:
    30
    I am getting this error as well in Unity 2019.3.13f1. Luckily I have github to go revert back.
     
    Last edited: Jun 14, 2020
  10. EdwinLyons

    EdwinLyons

    Joined:
    Oct 4, 2012
    Posts:
    59
    @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.
     
  11. harryr

    harryr

    Unity Technologies

    Joined:
    Nov 14, 2017
    Posts:
    38
    Thanks Edwin, we'll give it a look! :)
     
  12. EdwinLyons

    EdwinLyons

    Joined:
    Oct 4, 2012
    Posts:
    59
unityunity