Search Unity

Feedback Unity should recognize Git LFS link files and print a more descriptive error message on import

Discussion in 'Editor & General Support' started by DrummerB, Jul 16, 2019.

  1. DrummerB

    DrummerB

    Joined:
    Dec 19, 2013
    Posts:
    41
    When you check out a Unity project that is using Git LFS to manage large binary files, there is a chance that the LFS link files are not resolved correctly. For example, if you just download a project from GitHub, instead of cloning it, you only download the link files. This results in somewhat vague asset import errors in Unity that could be improved:

    Could not create asset from : File could not be read
    Error during import of AudioClip : Failed decoding audio clip
    ImportFBX Error: Couldn't read file
    The type or namespace name could not be found ...
    The name does not exist in the current context
    I suggest that when an asset import fails, Unity should check the file if it's a Git LFS file and print a more helpful error message like "Could not import asset at path <path>. It looks like a Git LFS managed file that has not been checked out correctly."
     
    karl_jones likes this.