Exception: Error while parsing: unable to parse; invalid token ">"; context =

Forums 💬 NodeCanvas ⚙️ Support Exception: Error while parsing: unable to parse; invalid token ">"; context =

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #16546
    strawberrycheesehat
    Participant

      Hello! I have a recently updated the project to unity 2020.1.a14, and all the node/flow assets we had made is having trouble deserializing with that update. I attached the output in the image. I wonder if anyone knows what is causing this or if there is any workaround? Thanks a million!

      here is the text version:

      Exception: Error while parsing: unable to parse; invalid token “>”; context = <> {>

      ParadoxNotion.Serialization.FullSerializer.fsResult.AssertSuccess () (at Assets/ParadoxNotion/CanvasCore/Common/Runtime/Serialization/Full Serializer/fsResult.cs:90)

      Also:

      Unable to parse file Assets/Canvai/Thoughts/BootThought.asset: [Parser Failure at line 20: Expect ‘:’ between key and value within mapping]

      #16553
      strawberrycheesehat
      Participant

        We might have figured it out, could be something on our end.

        #16552
        Gavalakis
        Keymaster

          Hello there,

          Did you figure this out? I would be interested to know if it was something on your end or if something on my end please.

          Thank you.

          #16551
          strawberrycheesehat
          Participant

            We changed our node assets yaml file to use “>” since it expends the lines to rows, so we could see the changes easier in version control. So it is probably not on your end. It was working fine in version 2019.2. I am not sure if unity changed how they parse yaml file that made “>” not a valid token.

            #16550
            Gavalakis
            Keymaster

              Hello again,

              Thank for the reply and the information. I would like to let you know that in v3, the json serialization is also printed in the asset file (for asset graphs) as yaml comments with multiple lines for version control diff purposes 🙂

              #16549
              strawberrycheesehat
              Participant

                Np! It is great to have customer support replies so fast as well. That is really great news, may I ask what is the approximate release date for v3? I might as well hold on the upgrade until that if it is something soonish. Thanks!

                #16548
                Gavalakis
                Keymaster

                  Hello and sorry for the late reply this time (was working hard on v3). V3 is just done and it will be sent to the asset store today or tomorrow! Yei! 🙂

                  Thanks!

                  #16547
                  strawberrycheesehat
                  Participant

                    Wooo! That is great! I am heading to asset store :D. Thanks for the hard work!

                  Viewing 8 posts - 1 through 8 (of 8 total)
                  • You must be logged in to reply to this topic.