Search Issue Tracker

Active

Votes

0

Found in

Issue ID

1214122

Regression

No

Investigate why .meta files are sometimes not parsed right

Asset Import Pipeline

-

The FileHasher.cpp emits an error whenever particular entries in a .meta file are mistaken for something which is not a Scalar value.

It has been noticed that when a .meta file ends with two spaces (the YAML standard for indentation) it sometimes mistakes the entry above it as being a mapping node.

One example can be found in this file:

https://github.cds.internal.unity3d.com/unity/xr.sdk.magicleap/blob/master/Packages/com.unity.xr.magicleap/Runtime/Compatibility.cs.meta

Where assetBundleVariant: is followed by a new line, and then 2 space characters (ascii value 32) before reaching the EOF marker.

Comments (2)

  1. 428404f48972ec0efee6294c49d972f6?d=mm

    michlaw

    Jan 28, 2020 07:29

    Thanks for the post and nice to see this here. You explained in a detailed way. Get more about the best apps here. https://www.turnpdf.com

  2. 158d8669d5f870dffd65e181cc498546?d=mm

    anoush678

    Jan 25, 2020 09:08

    The main purpose behind this MyNikeVisit is to get your genuine feedback about your recent visit experience. This feedback is really important to provide better service and products.

    https://mymenuprice.com/nike-survey-mynikevisit/

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.