Overview

Hello everyone: I paid the $99 requested to publish an app on Saturday around 3 PM (Paris time). They asked me for my French ID card shortly after, around 5 PM (Paris time). I sent it around 8 PM (Paris time), but I haven't heard back since. I emailed support around 10 AM (Paris time). Still no response. Can you help me?

Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?

Hello, I submitted a request for Family Controls (Distribution) approval, and it has now been over 12 days without any update on the status. I understand that review times can vary, but I wanted to check if this delay is expected or if there’s anything I might need to do on my end to help move the process forward. Could anyone from the Apple team or the community provide insight into: Typical processing times for Family Controls distribution requests Whether delays beyond a few days are common Any steps I should take to follow up or expedite the review For reference: Status: Submitted Submission time: April 29, 2026 Any guidance would be greatly appreciated. Thank you!

Since 28 April, we have seen some bizarre behaviour where iOS 26.3 and 26.4 are intermittently not loading some CSS and JS resources from our CDN. This is only reproducible when our CDN has HTTP/3 enabled. When reproduced in the Simulator, Safari's HAR shows that it is not even attempting to request those resources; it does not appear to be a network issue. Oddly enough switching to a different CDN with HTTP/3 enabled appears to resolve the issue. As far as I can tell, this hasn't been reported on the Webkit tracker; we'd be happy to provide Apple with additional data in a formal bug report but it would be helpful to know what data would be useful to provide.

Hello, I'm hoping someone from the App Review team can look into this situation, which has specific context that I believe makes it worth a careful look. Thank you in advance for your time. I'm hoping someone from the App Review team can look into this situation, which I believe has specific context that makes it worth a careful look. My app YADA: You've Already Met (App ID: 6759586097) has been in "Waiting for Review" since Wednesday May 6 at 7:44 PM ET - now over 96 hours. I have an open support case (20000112508151) filed Friday with no response yet. I'm not writing simply to flag the wait - I want to explain why this submission deserves a thoughtful second look on the merits. When YADA was submitted for TestFlight beta review, it was flagged under Guideline 4.3(b) for the same reason as the App Store rejection. I appealed, explained the differentiating mechanic, and an Apple reviewer evaluated the argument and approved the app for external testing. That approval is on record. I'm asking for consistency with that prior decision. YADA's core mechanic is genuinely unlike any dating app currently on the App Store. A user privately adds someone they already know to a list. That person receives no information about who added them. A match is only revealed when both people have independently and privately added each other. If the feeling isn't mutual, nothing is ever disclosed. There is no browsing of strangers, no algorithmic recommendations, no swiping, and no rejection possible because neither party knows they've been added until both have added each other simultaneously. Critically, YADA does not ask users to declare their gender or sexual preferences - because the mechanic doesn't require it. This makes YADA the only interest-discovery platform on the App Store that works entirely without those declarations, which creates a uniquely safe experience for LGBTQ+ users and young people who are not ready to publicly disclose their orientation. No equivalent experience exists on the App Store. The App Store rejection also included 5.1.1 and 2.1 issues, both of which I fully resolved - redesigning the contacts permission flow with a proper in-app explanation screen and directly answering Apple's question about data handling - with a new build submitted alongside my Resolution Center reply. I'm not asking for special treatment. I'm asking for the opportunity to have the full argument evaluated by a reviewer with the time to consider it, consistent with how the TestFlight review was handled. Support case: 20000112508151. App ID: 6759586097. Submission ID: abdf8b5b-5ea0-46a4-8a0b-fb58320fa701. Thank You

Hello, I'm reaching out regarding my app AUREX (App ID: 6761672161), which has been in "Waiting for Review" status for 17 days with no movement or communication from App Review. Submission details: App: AUREX AI — Investment Portfolio & Crypto Tracker Version: 1.0 (Build 17) Status: Waiting for Review since April 24, 2026 Category: Finance Support Case: 20000111960192 (opened 13 days ago, no response received) Context: All agreements, tax, and banking information are active. There are no messages in the Resolution Center, no warnings, and no visible issues in App Store Connect. The build was uploaded successfully and no further action appears to be required on my side. I understand that review times can vary and that the queue may currently be experiencing higher-than-usual volume. I'm not trying to escalate — I simply want to confirm whether: There is any specific issue or blocker with this submission Any additional information or documentation is required from my side Or whether the app is simply still pending reviewer assignment I would sincerely appreciate it if someone from the App Review team could take a look. Thank you very much for your time.

Bonjour a tous : J'ai payé Samedi à environ 3h PM (Paris) les 99 $ demandé pour publié une APPS, il m'ont demandé très peut de temps après ma carte d'identité Française vers 05h PM (Paris), je l'ai envoyé vers 20 Heure (Paris), hors depuis je n'ai aucun retour. J'ai envoyé un E-mail au support vers 10h AM (Paris). Hors depuis aucun retour, pouvez-vous m'aidé ?

Hello Everyone, Like probably several other Enterprise customers and more, we have been bitten by a bug with regards to VPN and Endpoint Security and the new M5 / M5 Pro SoCs shipping in the latest MacBook devices. I have raised the following feedback IDFB22753954 (which itself references an internal issue I believe, if we need to mark it as a dupe: 172793638 ). The technical sequence leading to the crash is as follows I believe: The macOS system process neagent successfully initializes the GlobalProtect network extension. The GP Network extension transitions from an 'inactive' state to a 'running' state. As network traffic begins flowing through the extension, a critical flaw in the macOS kernel's memory allocation (specifically related to the Apple Network Extension framework) is triggered. This memory management failure at the kernel level results in a kernel panic at an unpredictable point during packet processing. Because this is a core operating system vulnerability, any third-party application or security solution that leverages Apple's Network Extension framework is susceptible to these crashes. This has been confirmed across multiple vendors within the cybersecurity industry from what I understand. Crashes_M5Pro_1.txt Thank you in advance for your help! Kind Regards, Goffredo

I cant sign up for an Apple Developer Accnt. Error Screenshot attached

Hi everyone, I am working on an iOS app with a subscription-based model, and I need some clarification regarding App Store Review Guideline. The app allows one account holder to manage access for multiple people under the same account. Each person may need subscription-based access to certain digital features within the app. In this scenario, the subscription requirement is not limited to a single user under one Apple ID. The account holder may add multiple members/dependents, and access may vary based on the subscription status associated with those people. My question is: If the subscription is managed through our backend and the app locks or unlocks digital features based on that subscription status, would Apple consider this a violation for not using In-App Purchase? I would like to understand whether Apple expects In-App Purchase to be implemented in this type of multi-person subscription model, even when the subscription is managed at the account/member level rather than as a simple single-user plan. Any guidance or experience with similar review scenarios would be helpful. Thanks.

Issue: Sandbox test account stuck in a loop when trying to access account management Environment: iOS version: [iOS 26.4.2] Device: iPhone 12 Steps to Reproduce: Created sandbox test credentials on Apple Developer site (App Store Connect → Users and Access → Sandbox → Testers) On iPhone, navigated to Settings → Developer → Sandbox Apple Account Clicked "Sign In" and entered sandbox test email and password Successfully verified using verification codes (both email and phone number) Clicked on the signed-in sandbox account A popup appears with "Manage" option Clicked "Manage" Expected Behavior:- Should open sandbox account management interface Actual Behavior:- Popup immediately closes and the same popup reappears. Clicking "Manage" again produces the same result - an endless loop preventing access to account management. Has anyone encountered this issue with sandbox test accounts? Is there a known workaround or fix for this behavior?

there are a ghost touch bug for iphone 11. Its so annoying, i haven't seen a bug like this before ios 26.4.2 update

In Xcode (26.4.1), when using Coding Assistant, in new project, one can reference files by @fileName, but it does not work for projects that have been created e.g. 8 months ago. How can I make the @fileName feature work for previous projects as well? Project it fails with (@ does not show any files from the Project Navigator, and when e.g. manually referencing the @fileName and then clicking on the file in the Coding Assistant chat, macOS shows): Project it works with (FriendsFavoriteMovies project from this tutorial: Navigate sample data | Apple Developer Documentation) I'd be very happy to know a solution to my question: How can I make the @fileName feature work for previous projects as well? Thank you very much, Tim :)

Hello, I submitted an update for my app for review on April 27th. Since then, the app has remained in the “Waiting for Review” status. I contacted support by email after one week and again after two weeks, but both of my messages were left unanswered. Please provide me with an overview of what is going on with my app submission for review. Thank you.

My Apple Developer Program enrollment is still pending after payment and identity document upload. I enrolled on May 4, 2026. My payment was completed, I received the official invoice, and I uploaded the requested identity documents the same day. Apple also confirmed that my documents were received. However, my Apple Developer account still shows “Buy your membership” / “Complete your purchase”, and my membership has not been activated after several business days. Order ID: MN7Q04OBDY Apple ID: vargasserje Invoice date: May 4, 2026 Product: Apple Developer Program — Annual Amount paid: $459.900 COP Support Case ID: 102888644582 Could Apple Developer Support please review or escalate this enrollment?

Hey! App is approved for Advanced Commerce API and have generic product id (Consumable) for digital items purchasing. Uncertain on ho to test flow of pending purchase changing it's status to failed. As by docs BE side handling creating jws for purchase (also creates order to keep track of which items user bought) app with signed jws initiate purchase via product.purchase (send data for advancedCommercialData in options). If product purchase returns status .pending (still no transaction created) I notify BE that for that item (using item SKU) user has pending status for purchase, so that when user attempts to buy this exact item we do not create order duplicate. So the first question - do we need to check if user already made an attempt to buy this item and if item purchasing is pending decline another attempt of buying it? If user sends several requests to buy item under similar SKU for advanced commerce api do all of them will be charged or only one (does apple check SKU value when making a purchase of consumable product via advanced commerce api)? Another question is how to test purchase returns pending status for consumable item via advanced commerce api and then for that item (by SKU) changes status from pending to success? How to know (and eventually) test that after purchase of item via advanced commerce api firstly returns .pending status and then changes to .failure? I want to prevent users from trying to create order duplicates for single item, so when product purchase returns pending status I sent to BE id of item and order for this item on BE side will be marked as pending. So if user tries to buy this exact item once more and status of order on BE still .pending no new purchase will be initiated. So I need to know when purchase changes it's status to failed and then delete pending order on BE side, so that user will have an ability to initiate purchase for this item once more. How to tell whether .pending status for item changes to failed, will I be able in case of failed gather SKU that I previously passed in advancedCommercialData)?

Hi everyone, I am trying to complete my enrollment in the Apple Developer Program from Argentina, but I've encountered a blocking issue in the billing information section. When I reach the "State/Province" dropdown menu to enter my payment details, the province of Formosa is missing from the list. All other Argentine provinces are visible, but I cannot select mine, which prevents me from completing the purchase. What I have tried so far: Clearing browser cache and using different browsers (Safari, Chrome). Attempting the enrollment through the Apple Developer App on iOS. Checking my Apple ID personal information to ensure the region is correctly set to Argentina. Has anyone else from this region experienced this? Is there a way to manually bypass the dropdown or a specific contact department that can handle manual billing overrides for the enrollment fee? Any help would be greatly appreciated!

API Keys cannot be created due to an invalid Program License Agreement. Please update this agreement and try your request again. i don't see any pending license agreement in the business section

Hi Team,   We were using the API, ' https://itunes.apple.com/search?entity=tvSoftware&term=digital+signa&limit=10&country=US' for searching and fetching apple TV applications within our product. But we found that the API response is null currently. When going through iTunes Search API: Constructing Searches, we found that 'tvSoftware' is no longer an entity.   Could you please let me know what's the 'entity' value that we need to use for fetching Apple TV applications?

Hi, I’m trying to understand the availability of previousOriginalTransactionId in App Store Server Notifications. According to Apple documentation, the field exists here: https://developer.apple.com/documentation/appstoreservernotifications/previousoriginaltransactionid And the App Store Server Notifications changelog indicates it was added in March 2025: https://developer.apple.com/documentation/appstoreservernotifications/app-store-server-notifications-changelog However, I cannot find this field in practice. What I checked I’m using the Java App Store Server Library version 5.1.1 (latest on Maven Central). JWSTransactionDecodedPayload does not expose a property/getter for previousOriginalTransactionId. Example: JWSTransactionDecodedPayload payload = verifier.verifyAndDecodeTransaction(signedTransaction); There does not appear to be something like: payload.getPreviousOriginalTransactionId() I initially assumed this was an SDK lag issue, so I decoded the raw JWS payload JSON manually. However, I also do not see previousOriginalTransactionId in the decoded payload. Questions Is previousOriginalTransactionId only included for specific transaction/subscription migration scenarios? Has anyone actually observed this field in production or sandbox payloads? Is the Java SDK simply behind, or is the field conditionally emitted and I’m testing the wrong flow? Environment: App Store Server Library Java: 5.1.1 Dependency source: Maven Central Class: JWSTransactionDecodedPayload Verified by inspecting decoded raw JWS payload as well