We are unable to process your request

The new Apple Developer account is encountering the following error: “The bundle uses a bundle name or display name that is already taken. (90129)” We used Expo to build the apps and tested several bundle identifiers and app names for the new group, following the same procedure that has worked for our other groups. However, this specific group continues to trigger the same error — “The bundle uses a bundle name or display name that is already taken. (90129)” — every time we submit a successful build through Transporter. Even after experimenting with different bundle identifiers and creating a completely new Expo project, the issue remains unresolved.

I'm working on integrating Passkey functionality into my iOS app (targeting iOS 16.0+), and I'm facing an issue where the system dialog still shows the Save to another device option during Passkey registration. I want to hide this option to force users to create Passkeys only on the current device. 1. My Current Registration Implementation Here’s the code I’m using to create a Passkey registration request. I’ve tried to use ASAuthorizationPlatformPublicKeyCredentialProvider (which is supposed to target platform authenticators like Face ID/Touch ID), but the Save to another device option still appears: `// Initialize provider for platform authenticators let provider = ASAuthorizationPlatformPublicKeyCredentialProvider(relyingPartyIdentifier: domain) // Create registration request let registrationRequest = provider.createCredentialRegistrationRequest( challenge: challenge, name: username, userID: userId ) // Optional configurations (tried these but no effect on another device option) registrat

Hello Apple Developer Community, We’re building an MDM product (SaaS, multi-tenant). I’d like clarification on the APNs MDM push certificate usage model for service providers (MSPs). Question: Is it acceptable for an MDM vendor to use a single APNs MDM push certificate owned by the vendor to manage devices for multiple, independent customer organizations? Or is it required/recommended that each customer (company) must obtain and use its own APNs MDM push certificate (issued under the customer’s Apple ID) for their tenant? Why we’re asking: We understand that many guides show the process where each customer logs into the Apple Push Certificates Portal with their own Apple ID, uploads a CSR provided by the MDM, and then renews yearly. Practically, for a small team and early-stage deployments, using one vendor-owned certificate across multiple tenants would be simpler. We want to ensure we’re not violating any policy, terms, or technical requirements (e.g., certificate ownership, topic binding, device t

Hello everyone, I am the developer of a small app studio that has been creating and publishing apps on the App Store since 2017. Our main app recently reached the Top 5 in the Lifestyle category, serving thousands of paying subscribers and gaining around 15,000 new downloads per day until it was suddenly removed from the App Store along with our other apps. On October 11, 2025, I received a Pending Account Termination Notice for my main developer account. A few months earlier, on August 15, 2025, another account registered under my name had also received a pending termination related to Guideline 4.3(b) for a duplicate binary submission. That app was never live on the App Store. Once I realized the issue, I rejected the binary myself and stopped all activity on that account. I believe both accounts became linked because the same Apple ID and bank information were briefly used during setup. This may have caused Apple to associate the two accounts. Both accounts are fully verified legal entities. Since then, I

I added a new device and it's not recognizing the device model. This causes a message saying Unable to verify when signing an app. Has anyone else encountered this issue? This only happens with this one device, not others.

We got Advanced Commerce API and the generic product identifiers approved. When I was try to migrate a sandbox subscription to ACA enabled subscription I hit an error Request payload (Hid some info but the requestReferenceId is the real) { descriptors: { description: Migrated, displayName: Migration }, items: [ { sku: product_1mo_999, description: description, displayName: Product } ], requestInfo: { requestReferenceId: 3b0b8e67-d8a0-45f4-8f6d-06bffa9a2c08 }, storefront: USA, targetProductId: com.company.generic.subscription, taxCode: C003-00-1 } Response { errorCode: 5000000, errorMessage: An unknown error occurred. }

The problem is the following: We create a keychain item called NotaryTool (There are multiple accounts that use Notary tool and we created it for all of them ) This is created in the following way: $ xcrun notarytool store-credentials This process stores your credentials securely in the Keychain. You reference these credentials later using a profile name. Profile name: NotaryTool We recommend using App Store Connect API keys for authentication. If you'd like to authenticate with an Apple ID and app-specific password instead, leave this unspecified. Path to App Store Connect API private key: //AuthKey_ABCDEFGH.p8 App Store Connect API Key ID: App Store Connect API Issuer ID: ABCDEF-ABCD-1234-1234-1234567 Validating your credentials... Success. Credentials validated. Credentials saved to Keychain. To use them, specify `--keychain-profile NotaryTool` The key is downloaded from Apple and some other IDs are provided alongside. These should remain in the keychain for as long as the user process i

I’m calling the Apple Music API server-to-server using a developer token (ES256) created under my Developer account. Storefront probe succeeds: GET /v1/storefronts/us -> HTTP 200 All catalog endpoints return 500 (search, artists, charts) across multiple storefronts: GET /v1/catalog/us/search?term=rema&types=artists&limit=1 -> HTTP 500 GET /v1/catalog/us/artists/1359441424 -> HTTP 500 GET /v1/catalog/us/charts?types=songs&chart=most-played&genre=0&limit=5 -> HTTP 500 GET /v1/catalog/gb/... same results (500) I created the Media Services key ~48–72 hours ago. Media Services is enabled and associated with my Media ID. Developer token uses alg ES256, kid=, iss=, exp ~6 months. Clock is NTP-synced. Sample request (curl) and recent response headers: curl -i -H Authorization: Bearer https://api.music.apple.com/v1/catalog/us/search?term=rema&types=artists&limit=1 Response (truncated): HTTP/2 500 x-apple-jingle-correlation-key: NBZFUP7RVJBZOWVPIBVGUFMBLI x-apple-applic