This is the error that I get when I build for the iOS App Store or run on my connected iPad (with App Store release). This is my first iOS app that i have developed. When I build for development I get no errors and runs fine on my iPad (also simulator ipads). I have several Mac apps on the app store. The embedded.mobileprovision file is in my app bundle. com.nawctsd.riotpad is the Bundle Identifier in the app and in the App ID Configuration.

My team created an initial app bundle ID called Sendi from the front end of the app store connect account, and created a test app which hasn't been published to App store. Then we also created a second app programmatically using expo go which generated a new app bundle ID. What we need is to link the second configuration generated programmatically to the first Apple Bundle ID as that is the original name of the product, so we can maintain the same name for our App when we eventually go live. Any ideas on how we can achieve that?

I’m working with two Apple Developer Organization accounts and ran into an issue with Bundle ID reuse. In Account A: I created an App ID: com.example.app Created an app in App Store Connect using this Bundle ID Uploaded builds and used it only for TestFlight (never submitted for App Store review) Now I want to move development to Account B. However: When I try to create the same Bundle ID (com.example.app) in Account B, I get: “An App ID with Identifier 'com.example.app' is not available.” What I’ve considered: The app has never been submitted or approved It has only been used for TestFlight testing I have not yet attempted App Transfer (since it requires an approved app) Questions: Is a Bundle ID permanently locked to the original account even if the app was never submitted for review? If I delete the App ID and app from Account A, will the Bundle ID ever become reusable? Is submitting the app once and then using App Transfer the only way to move this Bundle ID to another account?

We are planning to distribute our app outside of TestFlight because our testing period exceeds the 90-day limit. Since we have an Apple Developer account, we are considering using Unlisted App Distribution for long-term testing. I have a few questions regarding this approach: After completing testing via Unlisted Distribution, is it possible to switch the same app to a public App Store release, or would we need to create and submit a separate app for public distribution? If a separate app is required, are there any restrictions from Apple on releasing essentially the same app under a different bundle identifier through another distribution channel? (Additionally, once testing is finalised, we plan to discontinue the Unlisted App version.) Are there any potential complications or limitations we should anticipate (e.g., app review concerns, versioning, or policy compliance) related to this matter? Any guidance or best practices in this matter would be greatly appreciated.

I’m running into an App Store Connect issue and I’m trying to figure out whether this is a build configuration problem on my side or a backend issue in App Store Connect. When I try to save my app version after selecting a build, App Store Connect fails and DevTools shows this request failing: PATCH /iris/v1/appStoreVersions/ with a 409 Conflict. The response body is: Json { "errors": [ { "id": "af484f56-8f7d-4338-a04a-2aeda858ace1", "status": "409", "code": "ENTITY_ERROR.RELATIONSHIP.INVALID", "title": "The provided entity includes a relationship with an invalid value", "detail": "The specified pre-release build could not be added.", "source": { "pointer": "/data/relationships/build" } } ] } A few details: The issue seems to happen with all uploaded builds, not just one The builds finish uploading and appear in App Store Connect I’ve already checked and corrected my version/build number setup I created a fresh Release archive I uploaded a new build I removed the previously attached build and tried attaching the new one App Store Connect still refuses to save the version once a build is selected I’ve already verified that the app version and build number in the project appear to be set correctly. At this point I’m trying to understand: Any suggestions on specific things to check would be appreciated. Thanks.

forum-post-v2-evidence.log MCRestrictionsPayload (allowListedAppBundleIDs) breaks Apple Watch app enumeration — nanotimekitcompaniond reports "Missing .app from directory: /Watch/" Summary Installing a Configuration Profile with com.apple.applicationaccess payload containing allowListedAppBundleIDs causes native Apple Watch apps to disappear from the paired Watch — even when their bundle IDs are explicitly in the whitelist. Log analysis shows this is not a bundle ID matching problem: nanotimekitcompaniond on the iPhone fails to enumerate the <companion>.app/Watch/ subdirectories where native watchOS app stubs live. Follow-up to https://developer.apple.com/forums/thread/745585 — community-confirmed but received no official response. Environment iPhone 16 (iPhone17,3), iOS 26.4.2 (23E261), supervised Apple Watch paired via Bridge.app Profile installed locally via Apple Configurator (no MDM server required) Smoking gun Within ~5 seconds of profile install, two processes (nanotimekitcompaniond and NTKFaceSnapshotService) log identical errors for eight companion-app paths: nanotimekitcompaniond[1498] <Error>: Missing .app from directory: file:///Applications/MobilePhone.app/Watch/ nanotimekitcompaniond[1498] <Error>: Missing .app from directory: .../Calculator.app/Watch/ nanotimekitcompaniond[1498] <Error>: Missing .app from directory: .../Bridge.app/Watch/ nanotimekitcompaniond[1498] <Error>: Missing .app from directory: .../MobileTimer.app/Watch/ nanotimekitcompaniond[1498] <Error>: Missing .app from directory: .../Camera.app/Watch/ nanotimekitcompaniond[1498] <Error>: Missing .app from directory: .../VoiceMemos.app/Watch/ nanotimekitcompaniond[1498] <Error>: Missing .app from directory: .../MobileMail.app/Watch/ nanotimekitcompaniond[1498] <Error>: Missing .app from directory: .../FindMy.app/Watch/ NTKFaceSnapshotService[3758] <Error>: Missing .app from directory: <same 8 paths> The Watch's app icons and face complications both go through these processes, which explains the symptoms users see. iOS itself flags the payload as Watch-incompatible — but applies it anyway profiled[179] <Notice>: Payload class MCRestrictionsPayload (com.apple.applicationaccess) is not supported on any Watch version profiled[179] <Notice>: Payload class MCRestrictionsPayload (com.apple.applicationaccess) is not available on HomePod profiled[179] <Notice>: Beginning profile installation... profiled[179] <Notice>: Profile "...v2..." installed. So profiled knows the payload doesn't target watchOS — yet its side effects clearly manifest there. Tests performed Test Bundle IDs in whitelist Result v1 249 (every installed iOS app: Apple + 3rd party) Walkie-Talkie, Messages, Find My + more disappear from Watch v2 295 (v1 + every Apple extension/Nano* daemon seen in syslog: *.MessagesActionExtension, *.FindMyNotifications*Extension, *.FindMyWidget*, com.apple.NanoBackup, com.apple.NanoMusicSync, com.apple.NanoPreferencesSync, com.apple.NanoTimeKit.face, com.apple.NanoUniverse.AegirProxyApp, com.apple.tursd, com.apple.FaceTime.FTConversationService, com.apple.Bridge.GreenfieldThumbnailExtension, etc.) Identical Missing-.app errors. Same apps disappear. Conclusion: this is not a bundle ID matching issue — adding more IDs doesn't help. The system fails to enumerate <companion-iOS-app>.app/Watch/ regardless of whitelist contents. Many users in my prior thread reported trying 100+ bundle ID combinations without success; this evidence explains why. Reproduction (no MDM required) Pair Apple Watch with iPhone normally. Generate a Configuration Profile with com.apple.applicationaccess + any non-empty allowListedAppBundleIDs array. Install via Apple Configurator's cfgutil install-profile, or AirDrop + Settings → Install. Within ~5 s, nanotimekitcompaniond errors appear (visible via idevicesyslog). Native Watch apps backed by an iOS companion stub disappear from the Watch's app grid and from face complications. Hypothesis MCRestrictionsPayload applies an enumeration filter that does not descend into .app/Watch/ subdirectories when computing visible apps. nanotimekitcompaniond consequently sees those directories as missing, the Watch's Carousel (SpringBoard equivalent) hides the apps, and NTKFaceSnapshotService can't load corresponding complications. Because profiled itself logs the payload as "not supported on any Watch version", this appears to be unintended bleed-through. Questions for Apple Is MCRestrictionsPayload / allowListedAppBundleIDs officially supposed to affect Apple Watch apps? profiled says no. Is there an undocumented bundle ID pattern (e.g. <companion>.watchapp, or a Bridge.app/Watch/ prefix) that needs whitelisting to keep native Watch apps visible? Is the recommended workaround to use blacklistedAppBundleIDs instead? Should the enumeration error (Missing .app from directory: .../Watch/) be tracked as a separate watchOS framework bug? Artifacts Curated evidence log with timestamps, profile installer events, and the eight Missing-.app errors is attached as forum-post-v2-evidence.log. Full idevicesyslog captures (multiple install/remove cycles, ~2M log lines) and the .mobileconfig files are available on request. Thanks — looking forward to guidance.