Overview

Hello, We are a Russian developer attempting to enable the StoreKit External Purchase Link Entitlement for our app. According to Apple’s documentation, this entitlement is required to provide external purchase links in Russia. However, the official request page consistently returns a 500 Internal Server Error: https://developer.apple.com/contact/request/storekit-external-entitlement-ru Steps we tried: Different browsers (Safari, Chrome, Edge) Different networks and VPNs Multiple developer accounts The error persists in all cases. We have already opened a support case (Case #102864703080), but Developer Support advised us to post here for technical guidance. Questions: Is there an alternative way to submit the entitlement request while the page is unavailable? Can Apple confirm whether this is a known issue and if a fix is in progress? Are manual submissions via the general Contact Us form accepted for this entitlement? Screenshots of the error are attached. Thank you in advance for any guidance.

Our compliance with the Digital Services Act is still under review after more than a month. We have sent several emails to Apple, but have received no response. Furthermore, we cannot find any information or links to submit new information or restart the review. What should we do? We need to publish our application in Europe.

i made payment. for the apple membership of 99$ 5 days ago, till now i didnt got access for the membership, it shows pending payment, please help me in this

I'm trying to test using different icons in the product page optimization section, with each page using a different icon. However, even though I've added the icons to "Resources" and checked "Include all app icon resources" in "General," the icons still don't display when creating a test in the App Connect section after official review. How can I make this feature work correctly?

Hi, My app is waiting for review since Saturday at 5:42 PM, so is TestFlight. It has been rejected a couple of times, and errors were fixed with each update. Is this normal?

Hi there I am trying to get to app store connect but it simply tells me "You must be an individual or team member in the Apple Developer Program, or invited by an individual to access their content in App Store Connect." I have since realised i've paid the enrolment/membership fee for developer membership twice, yet still don't have access. Any help greatly appreciated.

I am writing to share my frustration regarding the app review process for my application. My current submission has been stuck in "Waiting for Review" for nearly 7 weeks, starting from February 5th. Although I have attempted to cancel and resubmit periodically, there were significant gaps of 10 and 21 days between submissions where no action was taken. Currently, I am stuck again. The situation is critical for the following reasons: Critical Bug: The update includes a necessary fix for an In-App Purchase bug that is preventing users from accessing paid features. No Communication: I have sent four inquiries regarding this delay. I received only one generic response asking me to wait, and my subsequent follow-ups have been completely ignored. Expedited Review Request: My requests for an Expedited Review have also gone unanswered. Apple’s standard review time is typically 24-48 hours, but my experience is far from that. I am not asking for special treatment; I am asking for basic transparency regarding why my app has been stalled for nearly two months. Could anyone from the review team please look into this or provide an explanation? This prolonged silence is causing significant issues for my service and its users. Apple ID: 6752595582 First Submission Date: Feb 5th

Starting somewhere around macOS 26.3, my sandboxed file manager spontaneously loses access to ~/Library/Mobile Documents mid-session. Setup: at launch, the user grants access to '/', '/Users', or '~' via NSOpenPanel; I store a security-scoped bookmark and call startAccessingSecurityScopedResource(). This works fine - including iCloud Drive - until some point mid-session. When it breaks, two things happen simultaneously: Enumeration fails: NSCocoaErrorDomain Code=257 (NSFileReadNoPermissionError)< NSPOSIXErrorDomain Code=1 (EPERM) Console shows the kernel refusing extension issuance: couldn't issue sandbox extension com.apple.app-sandbox.read for '/Users//Library/Mobile Documents': Operation not permitted And probing NSFileProviderManager confirms the process has been rejected system-wide: NSFileProviderManager.getDomainsWithCompletionHandler > NSFileProviderErrorDomain Code=-2001 "The application cannot be used right now." (underlying Code=-2014) What makes this specific to FP-backed paths: regular paths under the same '/' bookmark (~/Library/Application Support, etc.) stay accessible and recover normally with a fresh startAccessingSecurityScopedResource() call. Only ~/Library/Mobile Documents and its subtree fail - the entire tree, including the parent directory itself. Relaunch always restores access. What I've tried and ruled out: Re-resolving the bookmark + startAccessingSecurityScopedResource() - returns stale=false, granted=true but access is not restored; the kernel still refuses extension issuance for FP-traversing paths. NSFileCoordinator coordinated read - doesn't help; the coordinator depends on the same sandbox extension the kernel is refusing. Instantiating NSFileProviderManager(for: domain) per domain - fails with -2001 for every domain, confirming the rejection is process-wide, not path- or domain-specific. My working theory: when a FileProvider daemon (bird/cloudd/fileproviderd) restarts mid-session, the process's FP-client XPC registration is invalidated, and the kernel subsequently refuses to issue sandbox extensions for any path served by FP - even with a valid bookmark. The process seems to have no API path to re-register its FP-client identity without relaunching. Current workaround: I detect the -2001 response and prompt the user to relaunch, then do a programmatic self-relaunch if they confirm (which is obviously horribly intrusive). Questions: Is there an API that lets a sandboxed consumer app reconnect its FP-client identity mid-session, short of relaunching? Is there an entitlement or capability that would make the kernel's extension issuance resilient to FP daemon restarts? Has anyone else hit this on 26.x and found a workaround? Filed as FB22547671.

Hello, We are facing an issue with In-App Purchases (subscriptions) in two iOS apps built with React Native + react-native-iap. Issue Some users receive the error: E_CONNECTION_CLOSED during the purchase flow. However: The payment is successfully deducted via the App Store. The subscription appears in the user's Apple ID subscription list. But on our side: The app does not receive the StoreKit transaction callback No receipt or transaction ID is delivered Our backend cannot validate the purchase. Restore Purchases When affected users try Restore Purchases, StoreKit returns: No purchases found even though the subscription is visible in their Apple ID. Most affected users are from India, and many payments are made via UPI through App Store billing. Has anyone experienced a case where: *the user is charged *the subscription exists in Apple ID *but StoreKit never returns the transaction or receipt? Any suggestions on how to recover these transactions would be greatly appreciated. Thanks!

Hi Support Team, I am writing regarding my enrollment which is currently showing as Pending. The payment of 99USD was from other Apple account, but the enrollment was submitted from my account. Case ID is 102866900911. Payment details: Date: 11 April 2026 Order ID: MT5786ZXVV Document: 716118431350 Could any Apple staff please activate my account? Thank you, Alisher

Developer Help says: Do I need to enroll in the Apple Developer Program to install apps on a device? No. You can install apps on your personal device with Xcode. Yet Xcode 26.4 says: Signing for "Never Forget" requires a development team. Select a development team in the Signing & Capabilities editor. Can someone help me understand this? A developer account isn't required, yet a development team (in a developer account) is? 🤷

I am trying to understand whether this is expected behavior or a configuration issue. My app has an auto-renewable subscription set up in App Store Connect. Current setup: Subscription type: Auto-Renewable Subscription Duration: 1 year Status: Approved Introductory offer: Free for the first week Introductory offer is active for the relevant storefront(s) Problem: On the App Store product page, the subscription only shows the normal price. There is no mention anywhere of the free 1-week trial. I tested this using a clean Apple ID that has never subscribed before and is in a region covered by the introductory offer. When trying to subscribe directly from the App Store flow (not the in-app paywall), the Apple purchase popup says “one-time payment”, even though this product is an auto-renewable subscription. What I thought would happen: The App Store page would show that eligible users get a free 1-week trial The purchase sheet would clearly indicate that this is a subscription, not a one-time purchase What I have already checked: Subscription is definitely created under Subscriptions, not as a non-consumable or one-time IAP Subscription status is Approved Introductory offer is active Product mapping appears correct Question: Is it normal that the App Store page does not mention the introductory free trial even for eligible users? Is it normal for the App Store purchase popup to say “one-time payment” for an auto-renewable subscription? Or does this suggest that something is misconfigured? If anyone has seen this before, I would appreciate guidance.

Hello, I am researching the technical feasibility of developing a Default Dialer App for the EU market using the specific entitlements granted under the Digital Markets Act (DMA). Our primary goal is to implement a Cellular/VoLTE-based calling system—not mVoIP—and we need to clarify whether it is possible to provide features such as STT (Speech-to-Text) and Call Summarization, which require In-call Audio Recording. Regarding the Default Dialer App Entitlement in the EU, I would like to clarify the following: Access to Raw Audio Stream: When an app is granted the Default Dialer status in the EU, does it gain programmatic access to the downlink and uplink audio streams of a cellular/VoLTE call for recording purposes? LiveCommunicationKit & Recording APIs: Does LiveCommunicationKit (or any related framework for iOS 26) provide specific APIs for a third-party dialer to capture native telephony audio? Entitlement Scope for Partners: If an EU-based partner obtains the necessary entitlements, can those entitlements be used to grant our application the authority to process cellular calls and access the associated audio data? Recommended Implementation: Are there any Apple-sanctioned methods or specific frameworks for implementing call recording for AI-driven services within the scope of the new EU-specific regulations? We need to confirm these technical boundaries to establish the implementation scope with our EU partners. Any guidance on whether a third-party app can technically and legally record cellular calls under these specific conditions would be greatly appreciated. Thank you.

I renewed my membership today, April 20, 2026, which had previously expired on November 5, 2025. The payment of KRW 129,000 was successfully processed, and the credit card transaction has been approved. However, my account still shows the message "Your Apple Developer Program membership has expired," and the renewal has not been applied. I have tried various troubleshooting steps, including logging out and back in, and clearing my browser cache, but the issue persists. Could you please look into this and apply the renewal to my account?

Since April 6 I’m waiting for review. No updates. They usually say that takes 24-48hrs to be reviewed. I'm at 10 days already. And I get no response on my emails and ticket.

My app is for a client that facilitates construction draws for construction companies. The app is stuck in a rejection loop for this reason: Guideline 3.2.1(viii) - Business - Other Business Model Issues - Acceptable Issue Description The app still provides loan services but does not meet all the requirements for apps providing these services. See below for additional information. These requirements give App Store users confidence that apps offering financial services are qualified to provide these services and will responsibly manage their data. Next Steps It would be appropriate to take the following steps to resolve this issue: The app facilitates loan or credit applications but you have not provided loan or business license documentation that demonstrates the app is authorized to provide these services. The client does not lend to consumers, nor individuals, and the client operates in states that do not require a lending license (including NMLS) to provide financing (such as construction draws) to construction companies. What documentation would app store review accept? I've tried written explanations in response to no avail.

Something happened with my Xcode 26.4 install, I've never had this happen before. I get Xcode 26.4 installed, but the simulators aren't installed. And nothing pops up to "install required simulators". In Devices & Simulators I click the + to install a new simulator, and the beachball just spins and Xcode becomes unresponsive. I've tried quitting and restarting Xcode, reinstalling it (using both xcodes command line tool and the app store), removing Xcode and reinstalling, rebooting after removing Xcode and before reinstalling. Not sure what to try next. Feels like something is left over from uninstalling that's hanging it up. But I've no idea what. I could use some Apple Xcode team help here.

Hi everyone, My app transfer (individual → company account) has been stuck since February 6th (68+ days), and I’ve been completely blocked from shipping any updates during this time. Impact: Cannot release bug fixes or improvements iOS app is now out of sync with Android Paying users are affected Developer Support has confirmed it’s with engineering, but there’s been no ETA or workaround. Has anyone experienced this before or found a way to: Regain the ability to push updates during a transfer? Escalate this internally? This is starting to significantly impact my business, so any guidance would be hugely appreciated. Thanks.

I file a lot of bug reports. I also ask a lot of third-party developers to file bug reports about problems they see. This post is my attempt at collecting together some hints and tips about Apple’s bug reporting process. To file a bug report, use Feedback Assistant. To file an enhancement request (ER), use Feedback Assistant. In the “What type of issue are you reporting?” popup, choose Suggestion. If you’re filing a bug against an API, choose Developer Technologies & Resources at the top level. The technologies popup should then list familiar items, from Accelerate Framework to XPC. If you can’t find the correct item, select “Something else not on this list”. Feedback Assistant is both a website and an app. For details on how to access the app, see Opening the app on the Developer > Bug Reporting page. For lots of great hints and tips about filing bugs, see File effective bug reports. I may repeat some of the info covered by that article, but only where I think it’s particularly important. After filing a bug report, please include the bug number in your DevForums post. Feedback Assistant shows the bug number in both the bug list and the bug detail view. Bug numbers start with FB and continue with a sequence of digits. For example, a recent bug report posted here on DevForums was FB11357055. Including the FB prefix avoids any confusion as to what type of bug number this is. Occasionally you’ll see other types of bug numbers. In release notes they are just in parens, so (99071807), and in DTS documents they have an r. prefix, so (r. 99071807). These are Radar numbers. Radar is the internal bug system here at Apple. Other developers can’t see your bug report. However, posting the bug number is still important for a couple of reasons: It allows Apple folks to quickly track down your issue. If another developer wants to file a related bug, they can reference your bug number in their bug report. You can share bug reports with other members of your team. For details on how to do that, see Collaborating with your team on the Developer > Bug Reporting page. Otherwise you can’t see a bug report filed by another developer, or one filed internally at Apple. One option here is to file your own bug and request that it be marked as a duplicate of the original bug. You’ll then be notified when the original bug is closed. The File effective bug reports article discusses the importance of including a sysdiagnose log with your bug report. I have a few additional tips: Include a sysdiagnose log from the machine that’s having the problem. Sometimes I see folks with an iOS problem include a sysdiagnose log for their development Mac )-: Include a sysdiagnose log even if you attach a test project that reproduces the problem. The contents of the log help with screening, making sure that your bug gets to the right person quickly. And that person will be very grateful to have your test project! If multiple machines are involved — for example, you’re reporting a Handoff problem — include a sysdiagnose log from each machine. Trigger the sysdiagnose log as soon as possible after you see the problem. The sooner you trigger the log, the more likely it is to capture relevant info. If the problem is hard to reproduce, see Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem for hints on how to capture an actionable sysdiagnose log. If you install a debug profile, install it before you reproduce the problem. These profiles typically enable more logging, and you want that logging to be active at the time of the problem. Most profiles activate immediately but some require that you restart. Follow the instructions that came with the profile. When reproducing the problem, make a rough note of the time and include that in your bug report. This doesn’t have to be super precise. Just note down the time, with seconds, shortly after you reproduce the problem. If the bug involves a crash, reproduce the crash outside of Xcode and then take your sysdiagnose log. This means running your code as the user would, so running an app from the Finder on macOS, running an app from the Home screen on iOS, and so on. If you reproduce the crash inside Xcode, the Xcode debugger catches the crash and prevents the system from generating a crash report to include in the sysdiagnose log. File focused bug reports. Imagine you’re seeing two problems, A and B, related to the same API. Don’t file a single bug that covers both A and B. Rather, file separate bugs for A and B. Feel free to reference your A bug in your B bug, and vice versa. Finally, some personal notes: DevForums is not an official support channel. Mentioning a problem here is not the same as filing a bug about it. That’s true even if you’re discussing your issue with an Apple person. Apple is a big company, and it’s very unlikely that the person you’re talking to is directly responsible for fixing your bug. Historically I used to post a lot of Radar links, of the forms rdar:nnn, where nnn is the bug number. I no longer use these links because I’ve found that they confuses folks. They click the link and wonder why it does nothing. If you post an FB number here, DevForums automatically turns it into a link. However, that link is only useful to you. Other folks can’t access the bug via that link. I’ve filed a bug against DevForums requesting that it only generate this link for the bug’s originator (r. 92946014). In the meantime, I work around this by putting FB numbers in code style, which disables this link generation. If you want to share bug information outside of DevForums, one popular option is Open Radar (https://openradar.appspot.com/). Apple uses a lot of open source and many open source projects maintain their own bug tracker. Two big examples are Swift and WebKit. If your bug originates in such an open source project, consider filing it in the project’s bug tracker. You can then go on to submit a pull request with the fix (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Revision History 2026-04-20 Added ER as a shortcut for enhancement request. 2025-08-07 Updated “Developer Technologies & SDKs” to “Developer Technologies & Resources”. 2024-03-07 Made minor editorial changes. 2023-10-26 Added a link to Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. Added a recommendation to file focused bug reports. 2023-06-28 Updated the advice on how to file an API-level bug based on recent changes to Feedback Assistant. Corrected some link titles. 2023-03-21 Added a bunch of bullets to the personal notes section. 2023-03-13 Extended the discussion of seeing other folks’ bugs to make it clear that you can’t see bugs filed internally at Apple. 2022-12-13 Added advice about the “Something else not on this list” option. 2022-09-01 Added a personal notes section at the end. Added a new bullet in the sysdiagnose section about running your app outside of Xcode. Made other minor editorial changes. 2022-08-29 Added a note about filing duplicate bugs. 2022-08-24 First posted.

Hi everyone, yesterday i installed some package in my ios app , but i had a lot of problems to compile , due to reset my branch and get started from 0. My project have pods with firebase, lottie, instana and truskit but now, when a i try to run my project, xcode show "Unable to resolve module dependency" into LOTTIE, INSTANA, TRUSKIT, FIREBASE . I visited a lot of forums and websites, and i tried the followings steps: Pod deintegrate pod repoupdate pod install Clean build folder Delete derived data but isnot working. Also,I reinstalled xcode , 2 versions , i "re"clone my repository and the issue persist. Sorry, my english is basic only