Search Unity

  1. We are migrating the Unity Forums to Unity Discussions. On July 12, the Unity Forums will become read-only.

    Please, do not make any changes to your username or email addresses at during this transition time.

    It's still possible to reply to existing private message conversations during the migration, but any new replies you post will be missing after the main migration is complete. We'll do our best to migrate these messages in a follow-up step.

    On July 15, Unity Discussions will become read-only until July 18, when the new design and the migrated forum contents will go live.

    Read our full announcement for more information and let us know if you have any questions.

Unity changing GUIDs absolutely every time you give the editor window focus

Discussion in 'Editor & General Support' started by brokenbeta, Jun 7, 2018.

  1. brokenbeta


    Nov 20, 2013
    We use some iOS plugins which contain .frameworks, which are actually folders with a specific file structure which includes some symlinks.

    Versions/Current -> Versions/A
    Headers -> Versions/Current/Headers

    The way that Unity handles these .frameworks is complete madness. Every single time you give the editor focus, it detects multiple files with the same GUID. These are not actually multiple files, but rather the same file as viewed through two different symlinks. It detects a nonexistent GUID collision and changes the GUID, which doesn't fix the collision (since the GUID for one file cannot be made different from itself). But it does invalidate all of the .meta files inside the working directory and fills the editor log with spurious warnings:

    Multiple assets are overridden to use the same GUID: 4ab001fa6e23344a7be0c02ae1e017d1

    Note that those are not *two files*, the bottom one is the real path and the top one is just the same file again, as viewed through a symlink.

    The consequences of this is:
    - you can never have a clean working directory (Unity will crap up your working directory the moment you start to do anything)
    - if you make a commit, you have to choose between not committing the dummy guid changes (which is risky; you should always commit .meta files) or committing them and risking an unresolvable merge conflict
    - you have to disable warnings view in the editor log in order to see anything important

    A bug was filed,, but it was closed as Won't Fix without explanation. What's the right way to handle this?
  2. giangchau92


    May 1, 2016
    I still facing with this issue
  3. Lazybones94


    Sep 14, 2015
    UP please. Having the same issue, the logs are wasted because of this.
  4. bencoPB


    Jul 13, 2018
    Still facing this issue. Insane that they would mark that Won't Fix.