System Sequoia (15.7.2); Xojo 2021.21; dektop apps only.
I tried many times to submit my app to the AppleStore with Provisional Profiles thru AppWrapper.
After Delivering them Transporter reported an error such as (Invalid Code Signing ‘org.myapp.pkg/Payload/myapp.app/Contents/Frameworks/Appearance{akCocoa.dyli/’ must be signed 2834xxxxxxx), or “Cannot be used with TestFlight because the signature for the bundle at “myapp.app” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Etc).
The first error shows up when I creating the distribution profile I select the first button in the certificates preview; the second error happens when I create the profile selecting the last button.
I guess I have to get rid of some of the Keychain certificates. Which one? Or are there any other suggestion? Tnks.
BTW: I know that the last Xojo releases can somehow do the job (plus Ttransporter), and I have it, but at present I’d like to confine myself to AppWrapper. The I may try the Xojo way.
Thanks for answering: here is what I see from “Code Signing Diagnostic”: it seems the Apple Development certificate is not even signed. Should I request the Authority and download it again?
I noticed that the previous keychain list was missing some certificates listed in the above AppWrapper Diagnostic. So I hope this new listing is complete. It shows also the Private Key.
Although I do not see any expired “Apple Worldwide Developer Relations Certification Authority”
Meanwhile, after due request from Certified Authority, I downloaded 3rd Party Mac Developer Application (the first row in the list in the above post) and Apple Distribution (the forth one).
But both of them look the same as the old ones; i.e. the key is still Carlo Rubini, and the description of Apple Development is still H8954TDH5P).
In APT there’s an option to add an Apple Team ID in the preferences window. You’ll need to set up API access in your account, but it allows it to see all of the pieces and give more insights into what might be wrong, including its own diagnostics.
Ok. Apple moved them into a section called Integrations so it’s now:
Users and Access
Across to Integrations
Select Team Keys
+ to add.
at this point you name the key and select a role. If it’s just you, go ahead and select Admin, but if you have someone working for you (or this isn’t your account) you should be able to select Developer or App Manager. Personally I use Admin because it lets me also create new certificates in APT.
After downloading APT 3.9.2, following the second part of Help (8 and 9) I opened the Preferences window and right-clicking in the list at the top of the screen added a new item putting the 3 strings into their proper fields; but after selecting the downloaded .p8 certificate I got a message saying that the Team ID is already in use (see attached screenshot), and asking if I wanted to replace it. At present I cancelled the operation as I thought it better to first ask you and do what you suggest. Meanwhile thanks for your kind assistance.
Yeah, that probably should have automatically replaced. A new version will be available soon that will let you remove that top entry and fix the TypeMismatchException from above.
