Cannot upload MacOS build to App Store - Bundle Identifier in use

[pnostudiodeveloper]

Describe the issue Getting the following issue when trying to upload my MacOS standalone build to the Apple App Store:

ERROR ITMS-90511: "CFBundleIdentifier Collision. The Info.plist CFBundleIdentifier value 'com.renderheads.AVPro.Video-Core' of '<my app>/Contents/PlugIns/AVProVideo.bundle' is already in use by another application."

I have tried both not signing the AVProVideo.bundle, and also signing the .bundle file. Same issue both ways. Any assistance very appreciated!

Your Setup (please complete the following information):

• Unity version: 2020.3.16f1
• AVPro Video version: 2.1.8
• Operating system version: MacOS 11.3.1
• Device model: MacBook Pro 2017 3.1 GHz
• Video specs (resolution, frame-rate, codec, file size): N/A

To Reproduce

1. Create a MacOS build in Unity 2020 with AVPro Video 2.1.8
2. Try to upload the build to the App Store using the Transporter app

[MorrisRH]

The bundle is notarised so you shouldn't need to sign it or modify it but sometimes these things just don't work.

Prepend your bundle identifier to the AVPro Video bundles identifier. For example if your bundle identifier is com.mycompany.myvideoapp then change the plugin's bundle identifier to com.mycompany.myvideoapp.com.renderheads.AVPro.Video-Core. You will then need to sign it.

I appreciate this is a nuisance but we're in no way able to influence how the App Store works, sorry :(

[MorrisRH]

This may be of help: https://developer.apple.com/forums/thread/678131

[pnostudiodeveloper]

Hi Morris, When I tried your suggested solution, including with signing, I then get the following error on upload attempt: "No suitable application records were found. Verify your bundle identifier 'com.VisualMusicDesign.SeeMusicUnity.com.renderheads.AVPro.Video-Core' is correct.

• I found the solution in a closed issue suggested by a user, which is to: - Add a random numeric suffix to the identifier - like ".12345"
  https://github.com/RenderHeads/UnityPlugin-AVProVideo/issues/785#issuecomment-845817247 This does successfully upload after signing, and appears to be the only thing that works.

I might suggest this solution be added to the Platform Notes in the documentation, as anyone uploading to the Mac Store would face this.

This is all generally pretty confusing as a RenderHeads user, as AVProMovieCapture doesn't require changing the bundle identifier to upload successfully. Did you guys use a different notarization process for the two plugins? Is there a reason you can't use the same process for both? Don't worry about responding to me on this - just something to think about as it would be easier not to have to change this identifier every time I upload a build, and I don't currently have to do it for MovieCapture.

Thank you for your assistance

[MorrisRH]

The notarisation process for both AVPro Video and AVPro Movie Capture is identical so no hints to be had there. I agree this isn't best so I will be investigating.

[pnostudiodeveloper]

Just wanted to add information about my method of App Store upload:

1. Create MacOS Standalone IL2CPP build in Unity

2. Modify Info.plist identifiers as necessary in build folder

3. Codesign via Terminal

4. Build package via Terminal - productbuild --component <MyApp>.app /Applications --sign "3rd Party Mac Developer Installer: <MyName>" <MyApp>.pkg

5. Upload to Apple using Apple's Transporter app, from the App Store

• I note this, because when I was trying to accomodate the issue of Swift 5 code / MacOS 10.13, I temporarily trying building from XCode.
• I noticed that the XCode build seemed to prefer the identifiers being unchanged - no numeric suffix added.
• So it could possibly be that building from XCode and signing and uploading the package from Transporter have different identifier requirements.

Uploading through Transporter is far, far less time-intensive, and I sincerely hope it wouldn't be necessary for me to start uploading through XCode to accommodate AVPro Video.

Thank you, assistance is always very much appreciated

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.