Skip to main content
klassobanieras
New Participant
May 3, 2026
Question

Unity GUID collision

Hello!

The XR Core SDK uses GUID `a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6` in file 

Scripts/BuildingBlocks/AIBlocks/Transport/StreamingParser.cs.meta, which looks suspiciously like a placeholder someone typed in.

It turns out that mcl-unity uses the same GUID, leading Unity to endlessly complain about GUID conflicts if you import both packages.

I reported it to that project but given that two people independently typed that GUID in, it seems likely that there are more instances of it out there. Any chance you could regenerate the GUID please?

    1 reply

    Degly
    Degly
    Inspiring
    May 10, 2026

    Even though I have not experienced this, that GUID definitely looks like a manually typed placeholder rather than a generated Unity GUID.

    Unity GUID collisions can become really nasty because Unity resolves references globally, so importing both packages can silently remap references or constantly reimport assets.

    Regenerating the .meta GUID on Meta’s side is probably the correct fix here, especially if this exists in a distributed SDK package.

    For anyone hitting this, I normally recommend a temporary workaround to make things work:

    • Delete the conflicting .meta
    • Let Unity regenerate it locally
    • Reimport the package

    But obviously that becomes painful across updates/version control.

    Terms & ConditionsAccessibility statement