iOS app installation fails with 0xe8008018 for company team, but succeeds with another Apple Account Hello Apple Developer Community, We are facing a persistent code-signing issue while installing iOS development builds on a physical iPhone. We have contacted Apple Developer Support multiple times, but we have not yet received a technical explanation for the root cause. Environment Xcode: 26.6 (Build 17F113) macOS: 26.5.2 (Build 25F84) Device: iPhone 12 Pro Max (iPhone12,5) iOS: 26.5 (Build 23F77) Company Team ID: T6MQ4RXG46 Development certificate: Apple Development: Muthoot Money Limited (3MH4U8W7M5) Error message When installing the app through Xcode, installation fails with: 0xe8008018 — The identity used to sign the executable is no longer valid. The full error also contains: MIInstallerErrorDomain Code=13 CoreDeviceError Code=3002 IXUserPresentableErrorDomain Code=14 ApplicationVerificationFailed Troubleshooting performed Verified that the development certificate is within its validity period. Checked the provisioning profile's expiration date and confirmed that the test device UDID is included. Verified the app signature locally using codesign --verify --deep --strict. Confirmed that the app's signing authority and TeamIdentifier match our company team. Tested both our existing application and a newly created minimal iOS project named SigningTest. Important finding The newly created SigningTest app also fails to install when signed using our company team. However, the same test app installs successfully on the same iPhone when signed using another Apple Account's team. This suggests that the issue may be related to the company team's signing configuration or another team-specific factor, although we have not identified the root cause. Questions What could cause iOS to reject a locally valid app signature with error 0xe8008018? How can we identify the specific certificate, provisioning, trust, or device-verification check that is failing during installation? Is there any additional diagnostic command or device log we should collect? Could this indicate a team-specific signing issue that requires investigation by Apple? We would appreciate any technical guidance from developers who have encountered and resolved the same error. Thank you.

Reference to app myownkeyboardPHONE myownkeyboardPHONE 1.6 is in distribution ID 6761935734 trying to replace with the latest version 1.9.1 Validate fails stating to restore an older version that was removed. I tried to restore and the response was "Cant restore right now" I would hope you could replace 1.6 with 1.9 making 1.6 the older version. What is next step? Charlie

Hi, I am currently working on an App Transfer from Company A to Company B but can't find any documentation about what happens to existing Siri Shortcuts working via App Extension intents. I have separated the rest of the post in 2 sections: one what summarizes my current understanding and the other with some questions and hypotheses. It would be great to have either someone from Apple to answer that, or someone else share their experience and possibly some documentation that I might have missed. To my understanding, when a new Shortcut is created, it stores the BundleID of the App and of the App Extension to find the application that will execute it afterwards. If I uninstall the App, I can see a message in the Shortcut app that says "This action requires APPNAME but it may not be installed", but I know that after transferring the app the BundleID doesn't change completely, only the team part does. However, it is not possible to test that as this change cannot be done in xCode as far as I know. Another part that seems to play a role here is the info.plist file, but in my situation, there are no entries related to the BundleID. All that being said, I am wondering: Is it possible to perform an app transfer and keep previously created shortcuts working? Is it possible to test this kind of things without having to perform a transfer? I haven't found a way to change the team part of the Bundle ID Is there a place in the documentation that takes care of those things in depth?

Hello Apple Developer Community, I am an independent developer and I have reached a point where I genuinely do not understand what the correct path forward is. I have invested a very significant amount of personal time and money into Zivoo. The app has never been released on the App Store. Every time App Review provided feedback, I tried to address it seriously and substantially redesign the product instead of simply resubmitting the same application. The first versions of Zivoo focused on real-time social communication. Later, the app was rejected under Guideline 4.3(b) because Apple considered the experience too similar to existing dating apps. In response, we substantially redesigned the product again. Profile browsing, swipes, likes, skips and mutual-like mechanics were removed. The current Zivoo is focused on language learning and real-time language practice through active conversation rooms, AI-assisted room discovery, entry requests, live conversations, voice/video messages, reactions, shared mini-games and invitations for future practice. The application-specific code, backend, UI system, custom assets, product logic and more than 35 custom animations were developed specifically for Zivoo. We have never purchased a white-label app, cloned another application, purchased an app template or repackaged another developer's product. We do use standard third-party SDKs such as Yandex Mobile Ads, mediation SDKs, Firebase, AppMetrica, Lottie and others. During this process, we may also have made an important mistake. Previous Zivoo submissions used: confident.zivoo, ru.zivoo.social The current submission uses: ru.zivoo.talk All of these Bundle IDs belong to the same Apple Developer Team. Zivoo has never been published on the App Store, and multiple versions of Zivoo have never been publicly distributed at the same time. After previous rejections and major redesigns, we removed previous App Store records. Because the concept had changed significantly, we mistakenly believed that the redesigned product should be submitted under a new App Store record and Bundle ID. This was never intended to bypass App Review or distribute multiple copies of the same app. The current submission has now been rejected under Guideline 4.3(a), stating that it shares a similar binary, metadata and/or concept with apps submitted by us or other developers. The most difficult part of this process is that we are never clearly told what exactly is considered wrong. With each rejection, we receive a broad guideline reference, but not a specific explanation of which code, asset, metadata element, feature or concept triggered the decision. We currently see two possible explanations: Apple's systems may be matching the current submission against our own previous Zivoo submissions under different Bundle IDs. Shared third-party SDK components may be contributing to the binary similarity signal. Our technical analysis shows that standard third-party libraries represent a substantial portion of the measured build. We fully understand that this does not prove that the SDKs caused the rejection. At this point, however, I am afraid to simply make random changes and resubmit again, especially because the latest rejection also includes an Extended Review warning. I am not asking for automatic approval or special treatment. I simply want to understand what Apple actually expects us to fix. Can 4.3(a) be triggered by a developer's own previous submissions under different Bundle IDs, even if none of them were ever released? Can common third-party SDKs contribute to the similarity determination? And if Apple believes our application-specific code, assets or concept are similar to another developer's app, how can we verify or address that? I am prepared to provide client and backend source code, Git history, original design files, dependency information, build details and a live demonstration. If anyone has experienced a similar case, especially after removing previous app records and submitting a substantially redesigned version under a new Bundle ID, I would greatly appreciate hearing how it was resolved. If Apple Staff sees this post, I would be extremely grateful for concrete guidance on what exactly we should do next. Thank you.

I have two Apple Developer accounts under different Apple IDs: a free "Personal Team" account and a separate paid Organization account. Before my organization's Program enrollment was approved, I built an app to a physical device using Xcode signed into my personal account, which auto-registered an App ID under that personal team. Now that my organization account is active, I can't register the same App ID under the organization — both the web portal and Xcode's automatic signing return "not available," since it's already reserved under my personal team. Since personal (free) accounts have no web portal access, I can't see or manage that registration anywhere to release it myself. I own both accounts. Is there any self-service way to release an App ID from a personal team, or is contacting Apple Developer Support the only option? If support is required, is there a faster route than the standard contact form (I submitted a request several days ago with no reply yet)?

Hoping someone from Apple or anyone who has hit this can help. While setting up my first app I made a mistake: the App Store Connect app record was created with the wrong identifier a Services ID I use for Sign in with Apple (com.mycompany.myapp.signin) instead of my real app bundle ID (com.mycompany.myapp). A second app record was bound to the correct bundle ID. It had no builds, no in-app purchases, and was never published, so I deleted it, expecting the bundle ID to be released. Current state: The correct bundle ID does not appear in the Bundle ID dropdown, either in my existing app's App Information page or when creating a new app. Deleting the App ID in the developer portal fails with: "The App ID appears to be in use by the App Store, so it can not be removed at this time." It has been like this for several days; all my builds are signed with the correct bundle ID, and my subscriptions live on the surviving app record, so I cannot upload builds or run sandbox purchases until the record is on the right identifier. I raised a support case with Apple Developer Support 3 days ago (Case ID: [20000129712022]) and haven't had a response yet. Questions: Is there any self-service way to release a bundle ID held by a deleted, never-published app record? Alternatively, can support change the bundle ID on my existing (never-published) app record? Typical turnaround for this kind of case?

I'm trying to register the App ID ai.mycompany.app under our company Apple Developer account, but the portal says: "An App ID with Identifier 'ai.mycompany.app' is not available. Please enter a different string." We own the domain mycompany.ai, and no app is published with this identifier (an App Store lookup by bundle ID returns no results). I believe it was auto-registered earlier by Xcode's automatic signing under my personal Apple ID while testing a build, not under our company team. So it's now holding the identifier globally but isn't in use. I have access to both accounts — my free personal Apple ID and our paid company Developer account. The problem: under the free personal account, the Identifiers list (Certificates, IDs & Profiles) is restricted — free accounts can't access it on the portal, so I can't see or remove the Bundle ID there myself. And from the company account it doesn't appear, since it's owned by the personal team. What I want: release/remove this Bundle ID so I can register it under our company Developer account. Questions: If a Bundle ID was auto-created under a free personal team, how can it be removed when free accounts can't access the Identifiers list? Is contacting Developer Support the only way to release it in this case? Once released, does the identifier become available immediately, or is there a hold period before another team can register it? Any guidance appreciated.

We have an app which was removed in 2025. We want to update it with a new version of the app, which was made in Unity. I have the app in Xcode, with the same bundle ID and SKU, using a new version number. I get App Record Creation errors: The SKU you entered is already being used The App Name you entered is already being used for another app in your account. this is the point of updates, isn't it? To have the same name, SKU and BundleID? Any idea what is going on? None of the resources I am finding resolve this.

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.

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.

Hello, I'm try to Capabilities on the Identifier but I got this error. Any help please?

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.

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?

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.

Hello everyone, I'm currently developing an iOS application and have a question regarding project architecture changes and App Store Connect submissions. My app is already uploaded to App Store Connect and is being used for internal testing via TestFlight. During development, I've realized my initial project architecture is flawed and unsustainable. The Problem and Proposed Solution I've decided the best approach is to completely redevelop the app from scratch using a new, clean Xcode project that implements a better architecture (e.g., MVVM, Clean Architecture). The Core Question If I create a brand new Xcode project for the redeveloped app, can I: Use the same Bundle Identifier (com.mycompany.myapp) in the new project? Successfully archive and upload the build from this new Xcode project to the existing app on App Store Connect? In essence, does App Store Connect require the new build to originate from the same Xcode project structure as the previous builds, or does it only validate the Bundle Identifier and Version/Build Number? Any advice or confirmation from developers who have gone through a similar complete project overhaul would be greatly appreciated. Thank you!

Tech stack: React Native + Expo. We are using two solo developer accounts (not a business or team account). Context: Friend and I set out to make an app together. Friend created app and set it up on Apple. We worked on it together. He controlled devops (builds and submission). Friend no longer can commit to development. Wants to transfer to me. I create apple developer account. After app transfer, my phone (deviceid) underwent a 14 day soft ban preventing builds. That has since been lifted. There seems to be something in place preventing me from making dev builds on the original dev bundleid. It says it's still owned by him despite the app transfer. Bottom line: what needs to happen so 1 can make dev builds? nice to have: is there a way for us to both make dev builds under the same bundleid?

Tech stack: React Native + Expo. We are using two solo developer accounts (not a business or team account). Context: Friend and I set out to make an app together. Friend created app and set it up on Apple. We worked on it together. He controlled devops (builds and submission). Friend no longer can commit to development. Wants to transfer to me. I create apple developer account. After app transfer, my phone (deviceid) underwent a 14 day soft ban preventing builds. That has since been lifted. There seems to be something in place preventing me from making dev builds on the original dev bundleid. It says it's still owned by him despite the app transfer. Bottom line: what needs to happen so I can make dev builds? Nice to have: we can both make dev builds under the same bundleid

I have an independent watchOS app, and I am a partner of the related iOS app. This means the IOS app can give me its bundle ID. So, here is the question: If I want my watchOS app be listed under the iOS app store page. Do I only need my bundle ID to be associated with the iOS project ? Is it necessary for the watchOS project and the iOS project to be in the same project?

I suddenly started to receive the following email with the error in it stating that my uploaded app is not available to be used in TestFlight: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at “MyApp.app/Contents/PlugIns/MyAppWidgetExtension.appex” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' It was all working fine and now I am not sure even where to start looking. Signing, provisioning and everything else is managed automatically.