Guys, I need some help. I’m trying to publish my first iOS app — and I gotta say I’m almost overwhelmed by how depressed this has got me. I’m lost and smart enough to understand all the signing and provisioning and profiles and manual download of Xcode profiles and Transporter and yada-yada-yada and all I can do is follow Claude’s step-by-step instructions. Except that we’ve failed 3 or 4 times and now even Claude admits being confused and suggests asking on this forum. And I don’t even understand the problem well enough to ask, and I had to get Claude to write this problem description:
I’m trying to publish my first iOS app (uses iCloud Documents storage via URLForUbiquityContainerIdentifier:, not CloudKit framework) and can’t get past a code-signing entitlements error during export.
Setup:
- Xojo 2026r2.1
- iOS project has iCloud capability enabled (Documents + Key-Value), custom container
iCloud.com.fortbendchessclub.beastchess - App ID has iCloud capability set to “Include CloudKit support” (required to get modern
icloud-container-identifiers/icloud-servicesentitlements — the older “Compatible with Xcode 5” option failed a separate check) - Distribution provisioning profile regenerated multiple times, confirmed to include
icloud-container-identifiers,icloud-services,ubiquity-container-identifiers,ubiquity-kvstore-identifier
Error when Building for App Store:
error: exportArchive Provisioning profile "BEAST iOS App Store Distribution" doesn't include the com.apple.developer.icloud-container-environment entitlement.
error: exportArchive Provisioning profile "BEAST iOS App Store Distribution" doesn't match the entitlements file's values for the com.apple.developer.ubiquity-container-identifiers and com.apple.developer.icloud-container-identifiers entitlements.
What I’ve found researching this: an Apple DTS engineer, in an unrelated forum thread, said com.apple.developer.icloud-container-environment “is not an entitlement supported” and should be removed rather than matched — suggesting the problem may be that Xojo is embedding this key into the app’s entitlements at Build time when it shouldn’t be, rather than something missing from my provisioning profile.
My question: Is there a project setting that controls this, or is this a known issue with how Xojo’s iOS export handles the iCloud Documents capability against current Xcode/SDK requirements? Has anyone gotten an iCloud-enabled iOS app through App Store export successfully on a recent Xojo release?
----- my note again. I think I’ve been following all of the steps that Claude gave to me, jumping around between the Xojo screens and the different Apple screens, and when I’ve sent it screenshots, it says everything looks as it expects. Note that the Publish button does not work because I get an “Make sure there is an App Store Connect record using the same Identifier that the one set for the project. http://appstoreconnect.apple.com” error message. Claude says that I’ve set up everything correctly, but I have 0 confidence.