Search Issue Tracker
Fixed in 2022.2.X
Duplicate in 2021.3.X
Votes
2
Found in
2021.2.0b8
2021.2.0f1
2022.1.0a3
Issue ID
1376258
Regression
Yes
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a2
Fixed issue where FileSystemEventArgs.FullPath did not return a fully qualified path