I am submitting an app to the App Store. I am at the step of verifying the archive, using the "Validate App" feature to check for errors. This app uses three frameworks. The identifier for this framework, as specified in the Info.plist (configured via the target ==> 'General' ==> 'Identity' == Bundle Identifier is com.xxxyyyy.utilitykit. Where x's and y's specify all lowercase letters.
After pressing the "Validate App" button, I receive the following error:
App Store Connect Operation Error
Invalid Code Signature Identifier. The identifer "com.xxxyyyy.utilitykit" in your code signature for "UtilityKit" must match its Bundle Identifier "com.XxxYyyy.UtilityKit"
Note the presence of upper and lowercase letters in the warning message's expected Bundle Identifier. This was the original identifier that I used when creating the framework, but I changed to all lowercase letters. I understand how an app submitted to the app store could store the bundle id, but I have never submitted the framework to the app store.
I have no idea where the Bundle Identifier when upper and lowercase letters is saved. I don't see it in the App IDs listed on my developer account.
Anybody seen this before?
The ideal solution would find a file or path somewhere that would let me update what the App Store Connect is checking against and modify it there.
I never found any other place in the framework project where a bundle identifier was defined other than the Info.plist (or PRODUCT_BUNDLE_IDENTIFIER). So, I assumed something in either App Store Connect or the App project itself kept some residue information regarding the framework.
In the App project, I found a solution with the following steps:
(1) Removed reference to the framework in the App navigation pane
this removed the framework from both "Embedded Binaries" and "Linked Frameworks and Libraries" sections of General tab for target
(2) Exited Xcode
(3) Opened Xcode with App project
(4) Archived without framework
(5) Validated App
validation was successful (not sure why since the code obviously could not execute without the framework)
(6) Added the framework back to App project
(7) Archived with framework
(8) Validated App
validation was successful without any errors
This process somehow cleared memory of existing bundle identifier and accepted the new one.