I received this error message every time I opened my latest version of my project, 6.1: “Asset Packages/com.mischief.markdownviewer/Tests/Editor/Samples/markdown-testsuite/tests/extensions/multimarkdown/link-idref-implicit-no-bracket.md has no meta file, but it’s in an immutable folder. The asset will be ignored.” How can I resolve this issue? If it helps, when I unzipped a folder, the window prompted an error saying that a meta file’s path is too long and I pressed the skip button in order for the unzipping to continue. I don’t know if this is related or not to the error, and also don’t have experience dealing with meta files.
When I test my project, it runs okay, but I think this meta thing could be a bigger issue in the future if I keep ignoring it, like corrupting my project.
What‘s the full path to your project? If possible try to shorten it. Windows has a path length limit of 260 chars which can easily be hit if the project path is already quite long and then a package like this is added with deeply nested paths.
Thanks for reply. "G:\Inspiron17files_main\Programming\Unity\TestGame6_1_2021_3_27", yes it is possible I can shorten it I think, but it seems this directory combined with the one above seems to still fall under the character limit, unless the meta file it is referencing is very long. In terms of the package itself, it does not contain critical meta data needed for the project? Can I delete/reimport the package or use the package from a previous version of my project? I have already made changes on it (the project in general not in the package itself).
The meta file is named the same as the asset file plus “.meta”. I’m not sure what your exact workflow is, but (please correct me if I’m wrong) my understand is that you had a project which you unzipped from a zip file, and when you did this, there were errors popping up about a meta file whose path was too long, and you chose to skip that file. If I got that right, then perhaps the max path length could have been hit if the project folder was extracted by the unzip software into a temporary folder that’s actually longer than the final destination path, or you extracted it in a folder with a longer path before moving it to its current location. In any way, skipping the meta file would then directly be the cause of what you’re seeing here: Unity expects to see a .meta file for every single asset file, and this specific asset file does not have one, so it complains.
The suggested solution would be to try to put the .zip file in a folder with a shorter path (say, “G:\Temp”) then try to extract the project there. If the problem was caused by a temporary folder with a long path being used, this won’t help - in that case, you might need to try other unzip software, like 7-zip.
Again, this is based on a couple of assumptions so please forgive me if any of them are wrong. Keep us informed if you could solve the problem.
Hi Maxime, thank you for explaining how the meta file works and how it is tied to the issue I had. Yes, it seems what you had explained is correct. I felt I wanted to use a blanket solution rather than for each project so I moved my entire projects directory to G:\Inspiron17FilesMain, changed my Unity Hub project directory in the settings, and I had no more issues. I appreciated your help.