Search Unity

Read only asset has no meta file

Discussion in 'Editor & General Support' started by Lichtone, Aug 16, 2018.

  1. Lichtone

    Lichtone

    Joined:
    Jul 28, 2018
    Posts:
    8
    Just updated Unity to 2018.2, but issue keeps existing. In the console I have the following errors:

    Read only asset Packages/com.unity.package-manager-ui/Editor/Resources/Images/Dark/Materials has no meta file.
    Read only asset Packages/com.unity.textmeshpro/Editor Resources/Materials has no meta file.
    Read only asset Packages/com.unity.textmeshpro/Editor Resources/Gizmos/Materials has no meta file.

    I have reimported all packages 2 times but the errors are still there. What should I do?


    Edit: I now include a screenshot here:
     
    Last edited: Aug 21, 2018
    tuvshee20021107 likes this.
  2. Lichtone

    Lichtone

    Joined:
    Jul 28, 2018
    Posts:
    8
  3. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Do you have Write permissions to the project directory? If on Windows, consider creating a project under C:\Users\[username]\Documents
     
  4. Lichtone

    Lichtone

    Joined:
    Jul 28, 2018
    Posts:
    8
    Hi Jeff, thanks for replying, yes my project is under that exact location!


    [solved]

    Solution, I did go to console, right click on the package.

    Then select open in explorer.

    I found that this package was not in the expected Users\[username]\Documents file structure. Also the dates were old so it seems my reimports had had no effects. So in windows explorer I deleted the complete package.

    Then I reopened the project in Unity, and at package, reimport all.

    This fixed it.
     
    Last edited: Aug 21, 2018
    sj631 likes this.
  5. dorukeker

    dorukeker

    Joined:
    Dec 6, 2016
    Posts:
    37
    Hello All,

    We are receiving the same error message with a different setup.

    The custom package is loaded from a remote GIT repo. We changed the manifest.json accordingly and add the following.

    Code (csharp):
    1. "dependencies": {
    2.     ...
    3.     "com.orbamsterdam.unitytoolkit": "https://<username>@<git url of the repo>",
    4.     ...
    When we start the project with this we dont receive any errors from the GIT.
    But the same console errors about the meta file.

    Screenshot 2019-07-31 at 11.21.12.png

    On top of this it adds the following to the manifest.json

    Code (csharp):
    1. "lock": {
    2.     "com.orbamsterdam.unitytoolkit": {
    3.       "hash": "<hash goes here>",
    4.       "revision": "HEAD"
    5.     }
    6.   }
    It is a blank project in 2019.1.4f1

    Any idea what we might be missing?

    Cheers,
    Doruk
     
  6. nyashafrank145

    nyashafrank145

    Joined:
    Sep 29, 2019
    Posts:
    4
    Hi! Were you able to find a solution to this?
     
  7. HEATH3N

    HEATH3N

    Joined:
    Jul 19, 2014
    Posts:
    17
    Bump. Having the same issue with a different Git repo.
     
  8. BadSeedProductions

    BadSeedProductions

    Joined:
    Dec 26, 2014
    Posts:
    144
  9. unity_2KM_3_nN7PzPew

    unity_2KM_3_nN7PzPew

    Joined:
    Dec 10, 2020
    Posts:
    1

    when you get the error
    "json has no meta"

    it's because the package that you are trying to load through UPM doesn't include the meta files.
    try downloading the content of this package outside of unity either through npm if it's an npm package, or clone the repo if it's a github link
    then drag n drop the folder in a new unity project to auto generate the meta files
    then rehost the package and include the meta files
    it should import fine now