Search Issue Tracker
Fix In Review
Votes
3
Found in [Package]
Issue ID
1416285
Regression
Yes
"A meta data file (.meta) exists but its folder can't be found" warning thrown on 2D Sprite package import
Steps to reproduce:
1. Create a 2D project or import 2D Sprite package from Package Manager window
2. Observe console (Console "Clear flags" should be disabled, otherwise the warning will be removed on recompile)
Expected result: No warnings thrown on 2D Sprite package import
Actual result: One or multiple warnings appear in console during import:
A meta data file (.meta) exists but its folder 'Packages/com.unity.2d.sprite/Editor/Obsolete' can't be found, and has been created. Empty directories cannot be stored in version control, so it's assumed that the meta data file is for an empty directory in version control. When moving or deleting folders outside of Unity, please ensure that the corresponding .meta file is moved or deleted along with it.
Reproduced with: 2022.2.0a9
Didn't reproduce with: 2022.2.0a8, 2022.1.0b15, 2021.2.19f1, 2020.3.33f1, 2019.4.37f1
Comments (1)
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
- Multiplayer Play Mode package throws ArgumentNullException and can't be installed via Package Manager
- Video preview in the Inspector freezes shortly after the first play and does not recover until paused and replayed
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
eyebull21
Apr 28, 2022 01:21
I'm also having this issue but when I debug my game, Unity crashes. I went back to use Unity 2020.3.33f1. It doesn't give me any issues with this warning or crashes.