Search Issue Tracker
Fixed
Fixed in 2021.3.7f1, 2022.1.8f1
Votes
0
Found in
2021.3.0f1
2022.1.1f1
Issue ID
UUM-1822
Regression
Yes
[Backport] Failed to load a custom asset when using Naninovel package
Reproduction steps:
1. Open the user's project "Test.zip"
2. Select `Assets/Scripts/TestScript.nani` asset
3. In the Inspector window edit the first line (change "1" to anything else)
4. Press "Apply" button
Expected result: Asset is saved without warnings.
Actual result: A "'' does not exist" warning is logged.
Reproducible with: 2021.2.0b8, 2021.2.4f1, 2022.1.0a3, 2022.1.0a17
Not reproducible with: 2019.4.3f1, 2019.4.33f1, 2020.3.23f1, 2021.1.0a5, 2021.1.28f1, 2021.2.0b1, 2021.2.0b7, 2022.1.0a2
Couldn't test with: 2019.4.2f1, 2021.1.0a4, 2021.2.0a15 (losing the package when converting the project to these versions)
Notes:
- Couldn't test on some versions and reproductible on all the other versions with macOS (no not reproductible with versions)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
Resolution Note (fix version 2022.1.8f1):
Fixed in 2022.1.8f1
Resolution Note (fix version 2021.3.7f1):
Fixed in: 2021.3.7f1