CFBundleIdentifier Collision - com.unity.purchasing.unitypurchasing

I'm too still waiting for the news that will fix this issue before uploading my app to the Mac OS store. I'm reluctant to deal with hacks of any kind. This should work like a charm out of the box.

However, I'm glad to hear that the fix is on the way

 

I have the same problem... When the fix will be released?

 

Followed those steps exactly as outlined in the links you provided. The same error persists.

It may be that I didn't do one of these steps correctly but I think that this is to be expected when the suggestion solution is a bad hack work around from 3 years ago.

This is beyond frustrating. And the fact that you guys just don't seem to care that your product absolutely cannot be used just boggles my mind.

 

Hello! I was able to fix the issue and successfully uploaded my app to Mac App Store.

https://stackoverflow.com/questions...-use-by-another-application/61367228#61367228

 

If anyone is interested in automating this process. The following code snippet works for me.

• Replace

  <app name>

  with the directory containing your generated bundle
• Replace

  <bundle identifier>

  with your unique bundle id
• Replace

  <project name>

  with the name of your .xcodeproj file
• Replace

  <app target name>

  with your app's target name.

Code (CSharp):

1. using UnityEditor;
2. using UnityEditor.Callbacks;
3. using UnityEditor.iOS.Xcode;
4.  
5. public static class InfoPlistEditor
6. {
7.     [PostProcessBuild]
8.     public static void FixUnityPurchasing(BuildTarget buildTarget, string pathToBuiltProject)
9.     {
10.         if (buildTarget != BuildTarget.StandaloneOSX) return;
11.         var plistFile =
12.             $"{pathToBuiltProject}/<app name>/PlugIns/unitypurchasing.bundle/Contents/Info.plist";
13.         PlistDocument plist = new PlistDocument();
14.         plist.ReadFromFile(plistFile);
15.         plist.root.SetString("CFBundleIdentifier", "<bundle identifier>.unitypurchasing");
16.         plist.WriteToFile(plistFile);
17.        
18.         var projectPath = $"{pathToBuiltProject}/<project name>.xcodeproj/project.pbxproj";
19.         var project = new PBXProject();
20.         project.ReadFromFile(projectPath);
21.         var targetGuid = project.TargetGuidByName("<app target name>");
22.         project.AddShellScriptBuildPhase(targetGuid, "[FIX] Remove purchasing bundle codesigning", "/bin/sh", "codesign --remove-signature \"${PROJECT_DIR}/<app name>/PlugIns/unitypurchasing.bundle\"");
23.         project.WriteToFile(projectPath);
24.     }
25. }

 

It beats me how you have such a low priority on monetization on the third largest game platform. Its ridiculous that this doesnt work, has never worked and will probably never work, while proudly advertising that the IAP works on the MacStore.

 

Hi, well, it works somehow (refer to the workaroud above). Here is my app published https://apps.apple.com/app/id1477015249

But I agree, low priority for Mac and UWP is sad.

 

I encountered the same issue when building & uploading Mac version of my game. Using 2021.1.27f1 and purchasing 4.0.3. Is this fixed now in some new version? Thanks.

 

any resolve to this issue I tried the fix mentioned by @hippogames, but with no results

CFBundleIdentifier Collision. The Info.plist CFBundleIdentifier value 'com.unity.UnitySignInWithApple' of 'app name.app/Contents/PlugIns/UnitySignInWithApple.bundle' is already in use by another application. With error code STATE_ERROR.VALIDATION_ERROR.90511 for id e9c2b22a-abe0-4e3d-9bb5-a4498b0572ef