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 = <> {>
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.
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 🙂
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!
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! 🙂