Hi, We are facing an issue where Universal Links are working for most users but failing for some of our clients. For affected users: Links open in Safari instead of the app, or Universal link routing does not work as expected For other users: The same links open the app correctly What we verified Associated Domains capability is configured correctly AASA file is valid and accessible App configuration and bundle ID mapping are correct AASA: https://www.gartner.com/apple-app-site-association Issue Since the problem is only affecting a subset of users, we are unable to: Reproduce the issue consistently Identify when or why the association breaks Ask Has anyone experienced: Universal Links failing only for certain users/devices? What are the possible causes and how can we debug or proactively identify the root cause in such cases? Any guidance would be helpful. Thanks!

Hi, I added two new auto-renewable subscriptions to an existing subscription group: 50GB Monthly 50GB Yearly The other subscriptions in the same group (200GB and 500GB monthly/yearly) have already been approved. However, these two new subscriptions have remained "In Review" for over 3 days without any updates. Is this normal, or could the review be stuck? Has anyone experienced the same issue? Thanks!

Hi, I am working on integrating In-App Purchases (IAP) into a React Native app using the Expo managed environment. I would appreciate guidance on the complete implementation steps for setting up and handling IAP in this context. Specifically, I am looking for: How to configure In-App Purchases in App Store Connect (product IDs, pricing, etc.) Which libraries or Expo modules are recommended for IAP in a managed Expo workflow (e.g., expo-in-app-purchases or react-native-iap)? Step-by-step integration guide — installing the library, adding necessary permissions/entitlements, and any required app.json / app.config.js configuration. How to fetch available products, initiate a purchase, and handle purchase callbacks/receipts in code. Server-side receipt validation — best practices and recommended approach. Handling edge cases such as purchase restoration, subscription renewals, and failed transactions. Any sandbox testing setup required for testing IAP before going live. Any official documentation, sample code, or recommended resources for React Native Expo managed workflow would be greatly appreciated. Thank you!

We have changed app icon a while ago, it displayed correctly on distribution page and on other pages - with an exception of analytics - https://appstoreconnect.apple.com/analytics No matter what time range is selected it still displays old icon. Can I make something with it? It's been more then a year and it's definitely not a cache issue.

My account is invited to a team as admin I already accept the invitation but I can't find the team on developer.apple.com, appstoreconnect.apple.com even on XCode. My colleagues also cant find my account on the user and access tab on apple store connect but when he tried to invite me again it throw an error (A user with this email address already exists on this team.) What should I do to fix this?

I recognize that Apple has put out documentation on how to do things with the new Age APIs, but I have no idea what my apps are supposed to do to be in compliance with this law. Most of the law sounds like it applies to App Store developers like Apple, more than it pertains to individual app devs. If the age rating of an app changes, wouldn't we just put it in App Store Connect and have Apple disable those apps on the devices of the underage kids?

Case ID: 102924093872 Case ID: 102924089648 Hi Apple Support Team, I’m reaching out regarding a critical issue that is blocking my app testing and affecting hundreds of users. I cannot receive the two-factor authentication code for my Apple Developer account. My mobile operator has confirmed that SMS messages from Apple are not reaching their network at all. I also receive no calls. Since my account is not logged in on any device, SMS is the only way I can verify my identity - and it’s not working. I have already submitted two support cases but have not received any response yet. Here is the impact this is having right now: • 250+ people are waiting to get access to test my app • 400 users are already using the app • I cannot sign the new agreement that appeared in App Store Connect • Because of this, TestFlight is completely blocked - both the 10,000 user limit and the 100 user internal testing • Even when I add someone to my team and grant them access, it still doesn’t work for them either I have been building this app for almost 7 months. We are in the final testing stage before I plan to release it for sale. Every day without access is a day my users are waiting and I cannot move forward. I am asking you to please help me resolve this as quickly as possible. I really need your support right now. Thank you so much for your time. Best regards, Tata

Hello, I have a problem with the Retention Message API. The default message is not displayed to users when they try to cancel their subscription in the device's Settings app. The API configuration was made with Revenue Request. The request to use this API was approved by Apple for our account. After configuring it for the Sandbox environment, everything worked as expected the image and text were displayed to users. Later, I applied the same configuration to the Production environment. I received the Approved status for the message, but after purchasing the subscription from the App Store, although I can see the subscription in Settings, the retention message is not displayed when I attempt to cancel it. I have tried different Apple accounts from different regions (both EU and non-EU) and tested from physical locations without using a VPN. Also, for clarification, we do not use real-time communication only the default retention message. For additional information: I also tried configuring this message from App Store Connect, as shown in WWDC 2026, but this section is not available under the Subscriptions category. When I deactivate and then reactivate the message, I notice that the deactivated state shows the text status "Waiting for sync (0/9)", while the active state shows "Approved". All other assets have an Approved state. In my case, the message is configured for all subscription types without any filters or other restrictions. What could be causing this problem, and how can I fix it? It seems that the issue is not on my side.

Hello App Review Team, I’m writing this as a last resort after 3 weeks of an exhausting and costly review process for our app Hook — Smart Message Assistant (iOS 1.0.0). Full timeline: • May 3: First submission • June 4: Rejected (marketing language) • June 4: Resubmitted with all fixes • June 8: Rejected (Guideline 3.1.2c — subscriptions) • June 9: Resubmitted with every issue fully addressed June 17: Rejected (Guideline 2.1a — app crash + sign-in bug) • June 17: Resubmitted same day with critical fixes • June 23: Resubmitted again with additional bug fixes • Today: Still “Waiting for Review” — no movement, no communication We have submitted 4 expedited review requests — all approved. We have contacted Developer Support multiple times. Every time we are told “it will begin shortly.” It never does. Business impact: We have a contractual launch deadline and active paid marketing campaigns running. Every week of delay costs us thousands of dollars in direct losses. We have already lost over $10,000 in sunk marketing costs and missed revenue. We have addressed every single issue Apple raised — promptly, thoroughly, and without complaint. We are not asking to skip the process. We are asking for someone to actually look at our submission and tell us if something is blocking it. Apple ID: 6766006483 This is not a normal delay. This is 3-4 weeks of a small team’s work being held hostage with no explanation. Thank you.

Hello, I am 16 years old and have built my first iOS app using Expo and React Native. Since Apple requires developers to be 18 or older, my mom needs to enroll in the Apple Developer Program using her Apple ID on my behalf. I have a specific question about the tax and payment setup inside App Store Connect: When setting up the banking and tax information in App Store Connect, whose SSN should be entered — my mom's or mine? Or would it make more sense to obtain a free EIN (Employer Identification Number) from the IRS to use instead of either personal SSN? Whoever's SSN or tax ID is entered in App Store Connect — is that the person Apple sends the 1099-K to at the end of the year? Has anyone dealt with this situation before as a minor developer with a parent's account? How did you handle the tax reporting correctly? I have already spoken with a SCORE tax mentor who confirmed my mom will not be taxed, and I called Apple Support who redirected me to the IRS. I am looking for practical advice from developers who have actually been through this setup. My app has a Pro subscription at $4.99 per month so understanding the payment and tax flow before launch is important to me. Thank you in advance for any help.

Hi when I try to login to apple connect I get Compliance Screening and after trying to upload my passport and info I get "An error has occurred. Try again later."

Hi everyone, I’m looking for advice on the best escalation path for an App Store Connect tax issue that is blocking our Paid Apps / In-App Purchase setup for a live app. Timeline: Jun 18, 2026: Opened a Finance Support case for tax information submissions. Since then: No update from Apple Finance. Current impact: Paid Apps / IAP cannot be completed, and users are already trying to purchase the Pro upgrade. I have also submitted a new Finance contact request under Tax information submissions. Has anyone dealt with a similar App Store Connect tax issue where Finance Support went quiet? Is there any escalation path beyond the Finance contact form and replying to the original iTSPayments email? Any guidance from Apple staff or developers who have been through this would be appreciated.

Hello Apple Developer Community, I am seeking advice from developers who may have experienced a similar situation. My Apple Developer Program membership was terminated on May 22, 2026 under Section 3.2(f) of the Apple Developer Program License Agreement. Apple stated that there were "documented indications of fraudulent conduct" associated with my account. I submitted an appeal, but it was denied and Apple informed me that the decision is final. I am trying to understand what may have triggered this decision because my situation does not appear to match the common cases I have found online. Some background: Apple ID created in 2022. Enrolled in the Apple Developer Program since 2022. Membership renewed every year without issue. Renewal payment was made using my personal Visa card. Individual developer account. Personal Mac purchased new and used only by me. No account sharing. No account purchase, sale, transfer, or rental. No additional team members. My apps and backend services were developed and maintained by me. Main application is an IoT device control app for hardware that I personally own. No app updates, metadata changes, or TestFlight activity shortly before the termination. No prior warnings, verification requests, or communications from Apple regarding policy violations. I fully understand that Apple may have information that I cannot access and I am not asking anyone to speculate about Apple's internal investigation. However, I would appreciate hearing from developers who have experienced a termination under Section 3.2(f): Were you ever able to obtain additional clarification from Apple? Did the issue turn out to be related to account activity, identity verification, payment information, device associations, or something else? Has anyone encountered a similar situation despite having no recent account or application activity? Thank you for any insights or experiences you can share.

My developer account is a US single-member LLC owned by a non-US individual. The LLC is a disregarded entity with a valid EIN. App Store Connect only shows me the W-9 workflow. But the IRS instructions for W-9 say: ▎ "If the owner of a disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9" So I legally cannot submit a W-9. I need the W-8BEN workflow enabled. Apple Finance told me all US legal entities must complete a W-9, then suggested I get an EIN (I have one) or change my address. When I sent the IRS guidance, they said their system can't make the change and forwarded it to the tax team. That was May 14 (Case-ID 19771345). Over 15 business days later: no reply, no timeline, and my paid agreement is still inactive. My business is on hold. Has anyone with a foreign-owned single-member US LLC gotten the W-8BEN workflow enabled? Is there any escalation path beyond iTSPayments and the Finance contact form? Both have gone quiet.

App: MahjCheck (Apple ID for app available on request) Subscription Group: MahjCheck Ad-Free (Group ID 22087052) Products: Ad-Free Monthly — com.celebrateeverything.mahjcheck.adfree_monthly (Apple ID 6769124896) Ad-Free Annual — com.celebrateeverything.mahjcheck.adfree_annual (Apple ID 6769126263) Summary of the problem: Both subscriptions were live and fully functional in my approved app version 1.2.1. Customers were able to subscribe successfully. Then, without any changes on my end, both subscriptions reverted to "Missing Metadata" status, and customers can no longer subscribe (the purchase screen spins indefinitely because no offerings can be loaded). I have since completed all metadata: Both individual subscriptions have localizations, pricing, and availability (US and Canada) set I added the subscription group localization that was missing Both products now show "Prepare for Submission" The problem: App Store Connect displays the message "Your first subscription must be submitted with a new app version," but there is NO In-App Purchases & Subscriptions section on my version page to attach them to. I have submitted new app versions (1.2.2 approved, 1.2.3 in progress) and the section never appears, so I have no way to resubmit the subscriptions for review. These subscriptions were already approved and live previously, so they should not be in a "first submission" state. I believe they are stuck in an inconsistent backend state that I cannot resolve from the App Store Connect interface. Request: Please reset or re-approve these two subscription products so they return to "Approved/Active" status, or advise how I can resubmit them given that no In-App Purchases section is available on my version page. Thank you.

Hi has anyone had there app rejected for Guideline 4.3(a) - Design - Spam? my app is a cyber security app which has a VPN and I had this rejection message.. the reasoning was very vague and i am unsure what this means.. I had submitted an appeal and also replied to the reject message but have had no response for over a week. anyone had this and if so, how did you resolve ?

I'm registered as a legal business entity and using an Apple Developer Organization account (successfully migrated from Individual Developer account). The two apps I have live on the App Store show seller as my business (SMPLPXLS LLC), but the developer field, which is extremely prominent throughout the purchase flows, shows my actual name. The two apps are: SnapSpots: https://apps.apple.com/us/app/snapspots-save-your-spots/id6781947475 SMPLNVST: https://apps.apple.com/us/app/smplnvst/id6776138290 Please help. The whole point of migrating to an Organization account was to avoid this issue.

I started the process to transition my account from personal to business. I -think- I submitted everything. A couple days ago, I found an agreement that needed to be signed. It still says "Developer Information Update In Process." How long is the review? How can I tell if I'm still missing something? I can't add a new app or update my existing apps until this completes and I didn't know it would take weeks (it it was so obscure that it would take me weeks). Please help! Thanks Rob

Hello, I’m looking for guidance from the community and/or Apple staff regarding an app that has been stuck in review for an unusually long time. App details App name: IQPOOLS AR Platform: iOS Version: 1.1 Apple ID: 6775523951 Bundle ID: AR01.iqpools Developer account type: Individual Current status App Store Connect status: Waiting for Review There is no Resolution Center thread for this version Submission history: First submission: June 1, 2026 After ~1 week with no review progress, I updated the app, removed the previous submission (Developer Rejected), and resubmitted Current submission date: June 8, 2026 at 18:31 As of today, the app is still Waiting for Review Background I previously had an app that was approved and published as Unlisted Apple later removed it from sale due to regional restrictions on unlisted/custom app distribution for developers in my region (Russian Federation) Apple Developer Support advised that to switch from unlisted/private to public distribution, I must create a new app record and resubmit the binary I followed that guidance: new Bundle ID, new app record, new build, public distribution (not unlisted) What I’ve already tried Submitted Expedited App Review request(s) — no response Contacted App Store Connect support via the contact form — no useful response Replied to previous Developer Support case about unlisted → public transition Confirmed DSA/trader settings and EU availability where applicable Did not remove the current submission again to avoid resetting the queue App characteristics (for context) Free AR app for product visualization (composite swimming pools) No login required No in-app purchases, subscriptions, ads, or user-generated content Uses camera for ARKit only My questions Is a 2+ week wait in Waiting for Review (with no Resolution Center message) normal in this situation? Could the delay be related to the previous unlisted app removal / new app record after regional restriction? Is there any additional compliance step I might be missing (account-level, DSA, agreements, etc.)? What is the recommended channel to escalate when Expedited Review and Contact forms produce no response? Any guidance would be greatly appreciated. I’m happy to provide more details if needed. Thank you, Artem Lesik

Summary After setting a single auto-renewable subscription product (not the app) to "Developer Removed from Sale" in App Store Connect, the next scheduled renewal for an existing active subscriber failed with DID_FAIL_TO_RENEW v2 and expirationIntent = 5 ("expired for some other reason"). I expected expirationIntent = 4 ("product wasn't available for purchase at the time of renewal"), since the product was, in fact, not available for purchase. I would like to confirm whether 5 is the documented/expected value for this scenario, and how to deterministically distinguish "developer removed product from sale" from other renewal failures using the notification payload. Reproduction / observed sequence Day 15: Changed product annual_promo (auto-renewable subscription) status from "Approved" to "Developer Removed from Sale" in App Store Connect. The app itself remained Approved and on sale. Other subscription products in the same group remained Approved. Day 16: An existing active subscriber on that product had a scheduled automatic renewal date. Result: Renewal did not occur. We received a DID_FAIL_TO_RENEW v2 notification. Payload (relevant fields): JWSRenewalInfoDecodedPayload.expirationIntent = 5 JWSRenewalInfoDecodedPayload.autoRenewStatus = 0 Questions Is expirationIntent = 5 the correct/expected value when a renewal fails because the developer removed the product from sale? Or should it have been 4 ("product wasn't available for purchase at the time of renewal")? If 5 is intentional, what is the engineering rationale for not using 4 in this scenario? Given that expirationIntent = 5 is documented as a catch-all ("some other reason"), which other fields in the DID_FAIL_TO_RENEW payload (e.g., subtype, autoRenewStatus, gracePeriodExpiresDate, signedTransactionInfo) should we inspect to deterministically classify the failure cause and isolate "developer removed product from sale" from billing failure / customer cancel / price-increase not accepted / etc.? Context I'm aware of the docs page In-App Purchase statuses and Set availability for an auto-renewable subscription, but they describe the status semantics, not the resulting notification payload. Product has been reverted to "Approved" to avoid further impact on subscribers while this is clarified. Thanks in advance.