Overview

Hi, we made a strange discovery that might be helpful to other developers. This week, we released a universal app (Mac/iOS/iPadOS) on the App Store. Normally, when the app is "Ready for Distribution", it takes around 10 to 30 minutes to be available on the App Store using the direct url/link – but not this time. We waited 12 hours and the app was still not available using the direct link to our app. We noticed that in the "Pricing and Availability" section, it showed "175 (Countries) Processing" instead of the usual "175 (Countries) Available". Upon digging through the sections on App Store Connect, we noticed that we forgot to fill out the "App Accessibility" features. Upon filling out the "App Accessibility" features, the app went live a few minutes later and the "Pricing and Availability" section changed to "175 (Countries) Available" the same minute. There was no warning or indication of anything missing on App Store Connect. In case your app is "Ready for Distribution" and is not showing up on the App Store, please remember to check the "App Accessibility" section.

Since updating to MacOS 26.5.1, about 50% of Simulator launches from Xcode 26.3 produce this error: Mach error -308- (pic/mig server died) which is some trouble but I can get past it sometimes. I considered updating to Xcode 26.5 for a possible fix BUT there is a SERIOUS Swift 6.3.2 compiler bug that can violate MainActor isolation and the app I am close to finishing uses MainActor extensively. Also according to Dev Community, there's "also an active bug where SKTestSession cannot use the selected StoreKit configuration during unit tests, causing test actions to fail — relevant if you work on subscription-based apps." Frankly, IMO, Xcode 26.5 seems like a poor point upgrade that needs patching and soon. Is there any news when Apple might patch Xcode to fix both these issues (both reported using Feedback Assist that shows No Similar Reports).

I applied for the Apple Developer Program as an organization (Xentrix Code LLC) over a month ago. I have completed all requirements including D-U-N-S verification. The status is still showing “Pending Review” with no updates. I have already contacted support via email but received no response. Has anyone faced this issue or found a way to escalate it?

Hello, I’m trying to enroll in the Apple Developer Program, but I accidentally entered my name incorrectly during the enrollment process. It seems the mistake may have been caused by autocorrect on my iPhone, and I noticed it only after the enrollment had already started. Since then, I have contacted Apple Developer Support several times, but each time I receive a email with standard instructions that do not actually resolve the issue. I am not trying to bypass any verification process — I simply need the current enrollment attempt to be reset or deleted so I can start again with my correct legal name. At the moment, I seem to be stuck: I cannot complete the enrollment correctly, and I also cannot restart the process properly. Has anyone experienced a similar issue? Is there any way to request a manual reset of an Apple Developer Program enrollment attempt, or to have the incorrect enrollment information removed so I can submit a new enrollment with the correct name? Any guidance would be greatly appreciated. Thank you.

Hi, One week ago our Developer Program Subscription expired, and the Renew button is not showing. I've tried contacting support via phone, email, chat, etc. but no success. I'm the account holder, our Team ID is 5J74W2J3S3 and our organization is GA Trading LLC. This is causing serious issues to our business since new customers are coming every day, and they can't see the app. We just want to pay the $99/year and get our app back on the store. Can you guys help unblocking this ASAP? Thanks, Giovanni

Could you help clarify the expected behavior in downgrade scenarios during a Free Trial period? Does Apple trigger billing immediately for the downgraded plan, or does the change take effect only after the Free Trial window completes?

I'm trying to get a promo code for my app, and get vectored off to DevConnect to checkout the updated "Apple Developer Program License Agreement". Trouble is is that it shows no "updated" flag, button or whatever it is that I should be able to click to accept it. Bug?

Has anybody had encountered these build fail issues in xcode: Type ‘Constants’ has no member ‘AdmobinterstitialID’’; type ‘Constants’ has no member ‘admobadstriggerurls’;type ‘Constants’ has no member ‘fbadstriggerurls’, cannot find ‘cancelbutton’ in; cannot find ‘autoInjectVariable in scope; cannot find ‘enableBioAuth’ in scope;cannot find ‘statusBarBackgroundColor’ in scope;cannot find ‘deletecacheonexit’ in scope; cannot find ‘loadingIndicatorColor’ in scope; cannot find ‘status ‘statusBarTextColor’ in scope;cannot find ‘bottombar’ in scope; And they are all tied to AppConfig. swift And if so, how did you resolve it?

Hi, My iOS app (MatchLogr) version 1.0 has been approved and is currently in “Pending Developer Release”. Before submitting the app version for review, I created a subscription group and one auto-renewable subscription. I then selected the subscription from the app version’s “In-App Purchases and Subscriptions” section before submitting the app version to App Review. The app version has now been approved, but the subscription and subscription group localizations are still showing “Waiting for Review” almost 12 hours later. Since this is the first subscription for the app, my understanding is that it must be submitted with a new app version, which I believe I did. I’m holding the app release until the subscription is approved, because it is required for the app’s Pro features. Is this delay/status combination normal, or is there any additional action required on my side? Thank you.

With Xcode 26.5, I've switched from using SwiftLint in a "Run Script" phase to using the SwiftLintPlugins package and running it as a build plugin. This works fine on one Mac, in a small project, where the warnings from the build plugin show up in the issue navigator as expected. But on another Mac, in a large project, I can see the SwiftLint build plugin warnings in the build log but they don't appear in the Xcode issue navigator. Is there some Xcode setting that could influence this, or what else can I check?

Hello, I am unable to complete my Apple Developer Program enrollment. The enrollment fails with the generic message: “Your enrollment in the Apple Developer Program could not be completed at this time.” I contacted Apple Developer Support, followed the requested steps, completed a callback, and uploaded the requested government-issued ID and official address certificate through Apple’s secure upload link on Friday, May 22, 2026. I was told that the case would be escalated to the operations / enrollment review team, but I have not received confirmation that the documents were received or that the manual review is in progress. I have also tried the callback option again, but I have not been able to reach support successfully. Could Apple Developer Support please advise on the correct escalation path for an enrollment case that remains blocked after the requested documents have already been submitted? I can provide the case number privately through an official Apple Support channel if needed. Thank you.

This issue keeps cropping up on the forums and so I decided to write up a single post with all the details. If you have questions or comments: If you were referred here from an existing thread, reply on that thread. If not, feel free to start a new thread. Use whatever topic and subtopic is appropriate for your question, but also add the Entitlements tag so that I see it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Determining if an entitlement is real In recent months there’s been a spate of forums threads involving ‘hallucinated’ entitlements. This typically pans out as follows: The developer, or an agent working on behalf of the developer, changes their .entitlements file to claim an entitlement that’s not real. That is, the entitlement key is a value that is not, and never has been, supported in any way. Xcode’s code signing machinery tries to find or create a provisioning profile to authorise this claim. That’s impossible, because the entitlement isn’t a real entitlement. Xcode reports this as a code signing error. The developer misinterprets that error [1] in one of two ways: As a generic Xcode code signing failure, and so they start a forums thread asking about how to fix that problem. As an indication that the entitlement is managed — that is, requires authorisation from Apple to use — and so they start a forums thread asking how to request such authorisation. The fundamental problem is step 1. Once you start claiming entitlements that aren’t real, you’re on a path to confusion. Note If you’re curious about how provisioning profiles authorise entitlement claims, read TN3125 Inside Code Signing: Provisioning Profiles. There are a couple of ways to check whether an entitlement is real. My preferred option is to create a new test project and use Xcode’s Signing & Capabilities editor to add the corresponding capability to it. Then look at what Xcode did. You might find that Xcode claimed a different entitlement, or added an Info.plist key, or did nothing at all. IMPORTANT If you can’t find the correct capability in the Signing & Capabilities editor, it’s likely that this feature is available to all apps, that is, it’s not gated by an entitlement or anything else. Another thing you can do is search the documentation. The vast majority of real entitlements are documented in Bundle Resources > Entitlements. IMPORTANT When you search for documentation, focus on the Apple documentation. If, for example, you search the Apple Developer Forums, you might be mislead by other folks who are similarly confused. If you find that you’re mistakenly trying to claim a hallucinated entitlement, the fix is trivial: Remove it from your .entitlements file so that your app starts to build again. Then add the capability using Xcode’s Signing & Capabilities editor. This will do the right thing. If you continue to have problems, feel free to ask for help here on the forums. See the top of this post for advice on how to do that. [1] Xcode 26.2, currently being seeded as Release Candidate, is much better about this (r. 155327166). Give it a whirl! Commonly Hallucinated Entitlements This section lists some of the more commonly hallucinated entitlements: com.apple.developer.push-notifications — The correct entitlement is aps-environment (com.apple.developer.aps-environment on macOS), documented here. There’s also the remote-notification value in the UIBackgroundModes property. com.apple.developer.in-app-purchase — There’s no entitlement for in-app purchase. Rather, in-app purchase is available to all apps with an explicit App ID (as opposed to a wildcard App ID). com.apple.InAppPurchase — Likewise. com.apple.developer.storekit — Likewise. com.apple.developer.in-app-purchase.non-consumable — Likewise. com.apple.developer.in-app-purchase.subscription — Likewise. com.apple.developer.app-groups — The correct entitlement is com.apple.security.application-groups, documented here. And if you’re working on the Mac, see App Groups: macOS vs iOS: Working Towards Harmony. com.apple.developer.background-modes — Background modes are controlled by the UIBackgroundModes key in your Info.plist, documented here. UIBackgroundModes — See the previous point. com.apple.developer.voip-push-notification — There’s no entitlement for this. VoIP is gated by the voip value in the UIBackgroundModes property. com.apple.developer.family-controls.user-authorization — The correct entitlement is com.apple.developer.family-controls, documented here. IMPORTANT As explained in the docs, this entitlement is available to all developers during development but you must request authorisation for distribution. com.apple.developer.device-activity — The DeviceActivity framework has the same restrictions as Family Controls. com.apple.developer.managed-settings — If you’re trying to use the ManagedSettings framework, that has the same restrictions as Family Controls. If you’re trying to use the ManagedApp framework, that’s not gated by an entitlement. com.apple.developer.callkit.call-directory — There’s no entitlement for the Call Directory app extension feature. com.apple.developer.nearby-interaction — There’s no entitlement for the Nearby interaction framework. com.apple.developer.secure-enclave — On iOS and its child platforms, there’s no entitlement required to use the Secure Enclave. For macOS specifically, any program that has access to the data protection keychain also has access to the Secure Enclave [1]. See TN3137 On Mac keychain APIs and implementations for more about the data protection keychain. com.apple.developer.networking.configuration — If you’re trying to configure the Wi-Fi network on iOS, the correct entitlement is com.apple.developer.networking.HotspotConfiguration, documented here. com.apple.developer.musickit — There is no MusicKit capability. Rather, enable MusicKit via the App Services column in the App ID editor, accessible from Developer > Certificates, Identifiers, and Profiles > Identifiers. These app services are tied to your App ID on the server side, meaning that they have no presence in your code signature. com.apple.developer.shazamkit — There is no ShazamKit capability. Like MusicKit, this is an app service. com.apple.mail.extension — Creating an app extension based on the MailKit framework does not require any specific entitlement. com.apple.security.accessibility — There’s no entitlement that gates access to the Accessibility APIs on macOS. Rather, this is controlled by the user in System Settings > Privacy & Security. Note that sandboxed apps can’t use these APIs. See the Review functionality that is incompatible with App Sandbox section of Protecting user data with App Sandbox. com.apple.developer.adservices — Using the AdServices framework does not require any specific entitlement. com.apple.security.device.audio-input-monitoring — The com.apple.security.device.microphone entitlement is what restricts microphone access on macOS. [1] While technically these are different features, they are closely associated and it turns out that, if you have access to the data protection keychain, you also have access to the SE. Revision History 2026-05-28 Added com.apple.security.device.audio-input-monitoring to the common hallucinations list (Kevin) 2026-04-23 Added com.apple.developer.shazamkit to the common hallucinations list. Added a little more info about app services. 2025-12-09 Updated the Xcode footnote to mention the improvements in Xcode 26.2rc. 2025-11-03 Added com.apple.developer.adservices to the common hallucinations list. 2025-10-30 Added com.apple.security.accessibility to the common hallucinations list. 2025-10-22 Added com.apple.mail.extension to the common hallucinations list. Also added two new in-app purchase hallucinations. 2025-09-26 Added com.apple.developer.musickit to the common hallucinations list. 2025-09-22 Added com.apple.developer.storekit to the common hallucinations list. 2025-09-05 Added com.apple.developer.device-activity to the common hallucinations list. 2025-09-02 First posted.

I'm trying to submit a first-time In-App Purchase together with a new version of my macOS app, but App Store Connect doesn't seem to provide a way to do this. Setup: macOS app (Bundle ID: de.andreasmaser.Screenshots) Marketing version: 1.2, Build 1 (uploaded, processed, attached to version) IAP "Screenshots Pro" (Product ID: de.andreasmaser.Screenshots.pro) is fully configured: status "Waiting for Review", App Review screenshot present, both English + German localizations, pricing set Previous 1.1 submission was rejected under Guideline 2.1(b) because "the associated In-App Purchase products have not been submitted for review" Per Apple's documentation (https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase), step 3 says: "On the right, scroll down to the In-App Purchases and Subscriptions section." The problem: This section does not exist on the macOS app version page. I scrolled through the entire page; the sections are: App Previews & Screenshots → Promotional Text → Description → Keywords → URLs/Version/Copyright → Build → Added Content → Game Center → App Review Information → App Sandbox Information → Version Release. There is no "In-App Purchases and Subscriptions" section anywhere. What I've tried: Both Version 1.1 and a fresh Version 1.2 with a freshly-uploaded build Cancelling/withdrawing the previous submission and starting a new draft Editing the IAP and re-saving (no status change) The IAP's "Submit for Review" button stays greyed out on the IAP page The submission draft panel only shows the app version, with no "+" button to add IAPs The "Submission Drafts" floating button on the IAP detail page just opens the same panel with only the app Questions: Does the "In-App Purchases and Subscriptions" section appear for macOS apps under specific conditions I'm missing? Is there a different workflow for attaching first-time IAPs on macOS apps vs. iOS apps? Is this a known App Store Connect bug, and what's the recommended workaround? Any guidance is greatly appreciated — I've been blocked on this re-submission since yesterday.

My app has been stuck in “Waiting for Review” for a very long time and I’m honestly getting really frustrated. I already fixed all previous issues and submitted everything properly, but there has been no update at all. This delay is seriously affecting my launch plans and business operations. I understand reviews can take time, but the waiting period feels unusually long compared to my previous submissions. I have not received a response to multiple support requests for weeks. This is causing me quite a bit of stress as I don’t know what else I can do or how long this is going to last for. Has anyone else experienced this recently? Is there anything I can do to speed up the review process or get an update from Apple? I’d really appreciate any advice or shared experiences. Thank you.

Our application（Apple ID：6743150642） has been stuck in the Waiting for Review status for more than 7 days. We submitted an expedited review request 22 hours ago, but have not yet received a response. We are currently under significant time pressure, as our company’s app is required to launch before the Labor Day holiday. We have recently submitted a new version (1.2.0) and provided the institutional account as requested by the review team. We sincerely hope the expedited review request can help facilitate the process and move the review forward as soon as possible. Thank you for your attention and assistance.

Hi, I’m an Individual Apple Developer Program member. My Developer account Membership Details show an incorrect street address. This incorrect address is also being pulled into App Store Connect Business and into my tax forms, including the U.S. Certificate of Foreign Status of Beneficial Owner and U.S. Form W-8BEN. In App Store Connect > Business, my Paid Apps Agreement shows “Pending User Info,” my bank account is “Processing,” and the Tax Forms section shows “Missing Tax Info.” I already submitted address verification documents to Apple Developer Support more than 5 days ago, but the address has not been updated yet. My app includes auto-renewable subscriptions, so I need the Paid Apps Agreement and tax forms completed before submitting the app properly. Is the Developer account Membership address the source used for the Business address and tax forms? And is there any way to correct this manually, or must Apple Developer Support update it? Thanks.

Hello Apple Developer Community, I’ve got a problem with the Xcode Build feature. Because when I would like to build / run my app, my iPhone won’t show up. I’ve already enabled Developer Mode and have set it up in Xcode and did the setup again. I don’t know what I can do next. Are there any possible solutions to this? Thanks for the help 😁. additional Information: Xcode Version: 26.5 Mac: MacBook Air M3 · macOS 26.5 iPhone: iPhone 16 · iOS 26.5

My organization is planning to distribute an application as an Unlisted App, the app is a rebranded Enterprise ServiceNow Mobile. Since this is a PROD version our organization can't provide Test Account and ServiceNow Mobile don't have built-in demo mode. I can't send the current application for AppReview without Test Account and Demo Mode. Do you have any suggestion, how to solve our roadblock.

Hello, We are experiencing the exact same behavior described in the following Apple Developer Forum thread: https://developer.apple.com/forums/thread/827016 The issue appears to be isolated to the App Review environment and matches our current rejection under Guideline 2.1 - Performance. On our side, the subscription system is functioning correctly and consistently in TestFlight using the exact same build that was reviewed. We tested on multiple physical devices using Sandbox tester accounts and confirmed that: StoreKit successfully returns all subscription products RevenueCat offerings load correctly Localized pricing is displayed properly Purchases complete successfully Restore purchases also work as expected However, during App Review, the review notes indicate that the product list is empty, which causes the paywall to fail loading. We would like to emphasize that: The In-App Purchases are attached to the submitted app version Product identifiers exactly match between App Store Connect and the application code Agreements, tax, and banking information are active The products are marked as available for sale The same binary works correctly in TestFlight Because the issue cannot be reproduced outside the review environment, we currently have no reliable way to diagnose or validate a permanent fix. At this point, we suspect there may be an intermittent StoreKit product retrieval issue affecting the App Review environment specifically. If possible, could you please: Verify whether StoreKit product retrieval is functioning correctly in the review sandbox environment Share any diagnostic logs related to the failed product request Confirm whether the review device successfully connects to App Store sandbox services Provide any additional guidance for reproducing the App Review behavior locally We are fully committed to resolving the issue and ensuring compliance with App Store requirements, but currently the behavior appears environment-specific and non-reproducible from our side. Thank you very much for your assistance and support. Best regards, Mert Akgün

OK hello Apple developers, and whoever else is reading, I am a quadriplegic. This means I cannot use my fingers. So therefore I cannot pick up the phone. That means I cannot pick up the phone for Face ID which is biometric, fingerprint which is biometric, I believe the eye is biometric. So is the voice. That is how I have to login to my brokerage firms multiple bank account. Anything super secure I can use my voice as a password. It's super simple. Just add and the code and write it so therefore it is as simple as saying something to the effect of "hey seri my voice is my password. A few simple lines of code written by Apple expert this should not be hard at all and should be included in an update. Just think how would you use your phone if you could not pick it up. I cannot put Apple Pay i cannot secure on my phone because I cannot lock it because I cannot pick it up. Any help would be greatly appreciated