2019.3.0b9 is missing package meta files

I am getting this error in 2019.3.0b9 which I did not get with b8.

Asset Packages/com.unity.2d.path/Editor/Handles has no meta file, but it's in an immutable folder. The asset will be ignored.
Asset Packages/com.unity.2d.spriteshape/Editor/Handles has no meta file, but it's in an immutable folder. The asset will be ignored.

I have closed down Unity, removed the Library folder, and fired Unity back up but the same error occurs.

Package versions:
2D Path 2.0.3
2D SpriteShape 3.0.6

O/S:
macOS 10.15.1

It’s also in 2020.1. To get rid of it, you need to remove the 2D Sprite Shape package.

Not much help for anyone using the SpriteShape package…

1 Like

Getting this with hdrp in b9 too

Thanks for reporting the issue. We are aware and will issue a HDRP 7.1.3 package set fixing the problem.
https://issuetracker.unity3d.com/issues/hdrp-when-installing-or-upgrading-to-package-version-7-dot-1-2-type-or-namespace-serializedscalablesetting-can-not-be-found

1 Like

I also have this happening with the LWRP/URP in 2019.3.0b9 with the same two packages:
2d.path & 2d.spriteshape

Not fixed in 2019.3.0b10

1 Like

Confirmed SpriteShape 3.0.6 not fixed in 2019.3.0b10 (for Mac at least).

Error is “Asset Packages/com.unity.2d.spriteshape/Editor/Handles has no meta file, but it’s in an immutable folder. The asset will be ignored.”
Looking at the call stack in the inspector it happens during [EditorApplication applicationDidBecomeActive] so to test just deactivate Unity editor window and activate it again.

Package version 3.0.6 has a Handles folder in the stated Library/PackageCache/… folder path, version 3.0.5 does not. Reverting to 3.0.5 does not report the error but I have been using 3.0.6 with 2019.3.0b8 so I’ll stick to that until it’s fixed.

Hi, we are aware of the issue and we are preparing a fix for it at the moment. Thanks!

1 Like

Thanks for preparing a fix. Still not fixed in b11, Sprite Shape 3.0.7 :face_with_spiral_eyes:

I just checked with b11 and 2D Sprite Shape 3.0.7 and I don’t see the issue.
StarFluke: can you confirm these were the versions you used? and if you still get the error, can you post it here?

For me its fixed after updating to 3.0.7 using B11. Thanks! does spamming errors drove me nuts.

1 Like

i keep getting exactly same error for probuilder:
Asset Packages/com.unity.probuilder/upm-ci.log has no meta file, but it’s in an immutable folder. The asset will be ignored.
looks like someone else have it also:

unity 2019.3.11
probuilder 4.3.0 p8

not fixed still. 2019.3.12 trying to use one of the tutorials

Is this related to SpriteShape?

Can confirm - I’m also going through a tutorial and having this issue. It actually made it so some of the functionality of the demo no longer work because the packages are no longer importing properly into the Scene. I thought I somehow broke the camera, but then realized the Cinemachine camera was missing all the scripts on it because it couldn’t find the package contents anymore. I’m working through the Ruby’s Adventure: 2D beginner. FWIW, I have the following packages and only have the audio tutorial left:
2D Sprite
2D Tilemap Editor
Cinemachine (not empty)
Custom NUnit (now empty)
Rider Editor (now empty)
Test Framework (now empty)
TextMesh Pro (now empty)
Timeline (now empty)
Unity Collaborate (now empty)
Unity UI
Visual Studio Code Editor (now empty)

I left the project up on my mac and let the machine go to sleep - been working on it for the past 3-4 days, so not sure if that impacts this or not. I’ll try quitting and re-opening the tutorial for the audio tutorial tomorrow to see if that helps, but would be great to get this resolved though I’d like to see my final product working throughout the tutorials!

Update - I’m a noob! Quitting Unity asked me to save my project - I guess the whole time I haven’t had it saved. In doing so and re-opening the project, all the packages have been found. So anyone else who runs into this issue when running the tutorials give that a go! Hope this helps someone!

This is happening with the Pusher Unity package as well: GitHub - pusher/pusher-websocket-unity: Pusher Channels Unity Client Library

Is this something the package owner needs to fix or is this a Unity issue?
Using 2019.4 on Windows with URP.

Missing .meta files are usually a package issue. They are not blocking issues as the Asset Database from Unity will generate a default one (internally) but it should be fixed on the package to avoid any problems.

1 Like

Getting this with the Shader graph package now, very annoying as it spams my console with this:

Asset Packages/com.unity.shadergraph/ValidationConfig.json has no meta file, but it's in an immutable folder. The asset will be ignored.
1 Like