GUID Conflict Occurs When Importing Unity IAP Package 4.12.0

Hello,

I am using Unity 2020.3.25f1.1418. After creating a new project and importing the Unity IAP package version 4.12.0, I encountered the following error in the console:

Upon opening each of the meta files, I confirmed that they indeed have the same GUID. Is there any way to resolve this issue other than manually assigning different GUIDs? (Since the package contents are set to be ignored by Git, local changes are not shared with the team.)

Additionally, is it possible to release a fixed version of this package that addresses this issue?

Thank you!

Hello,
Thank you for your report, I was able to reproduce the issue on 2020.3.25f, but noticed it wasn’t happening in a later version.

After some investigation, this seems to be a Unity editor issue related to this bug:

This was fixed in 2020.3.48:

If updating editor version is not an option, is deleting the PrivacyInfo.xcprivacy and it’s .meta file a viable option?
This file is only used in the following editor versions and above : 2021.3.35f1, 2022.3.18f1 and 2023.2.7f1

Hello!

Thank you for your answer.
I can indeed confirm that the error no longer occurs with Unity 2020.3.48f1.
We will look into the Unity version upgrade.

Thank you very much.

1 Like

2021.3.18 has the same issue

GUID [b4326c66a9f464640b9457cbd6237bf6] for asset ‘Packages/com.unity.purchasing/Plugins/UnityPurchasing/iOS/PrivacyInfo.xcprivacy.meta’ conflicts with:
‘Packages/com.unity.purchasing/Plugins/UnityPurchasing/unitypurchasing.bundle/Contents/Resources/PrivacyInfo.xcprivacy.meta’
We can’t assign a new GUID because the asset is in an immutable folder. The asset will be ignored.

GUID [b4326c66a9f464640b9457cbd6237bf6] for asset ‘Packages/com.unity.purchasing/Plugins/UnityPurchasing/unitypurchasing.bundle/Contents/Resources/PrivacyInfo.xcprivacy.meta’ conflicts with:
‘Packages/com.unity.purchasing/Plugins/UnityPurchasing/iOS/PrivacyInfo.xcprivacy.meta’
We can’t assign a new GUID because the asset is in an immutable folder. The asset will be ignored.

1 Like

Did you manager to fix the issue?

did you manage to solve this?

Is it directed to me? If so, the issue was resolved by upgrading to Unity 2020.3.48f1.