Hi everyone, I’m facing an issue where my Apple ID still appears to be associated with a developer team even after being removed. Here’s the situation: I was part of a company Apple Developer Program team. I have already followed Apple’s official “Leave a Team” steps. I have also been removed from App Store Connect by the Account Holder. The Account Holder confirmed that my Apple ID is no longer visible under Users and Access However, when I log in to https://developer.apple.com/account, I can still see the team listed under my account. This seems like a mismatch between App Store Connect and the Apple Developer Portal. Has anyone else experienced this issue? If so: Did it resolve on its own after some time? Or did you have to contact Apple Developer Support to get it fixed? Any guidance would be really appreciated. Thanks in advance!

Previous app download metrics in App Store Connect (before the recent redesign of metrics) did provide a split of download numbers by country. This was very useful information. New metrics (after redesign) seem to only provide total app downloads numbers. The split by country is gone. How can I get figures for downloads by country? Using country/region filters seems to be no option because I would have to know which countries to filter for. If I want to see how my app downloads split by country how can I do that? Any help is appreciated.

I've published my app with subscriptions (app changed from paid to subscription model). I've have succesfully pass review process and app was published to App Store without subscription store, so no one can buy app (still working as paid, but will expire in few days forcing users to subscribe). I want to attach subscriptions to new build, but I can't - there are no options mentioned in documentation. I'm stuck. There is no any contact point to review team. I've created 3 cases, nobody reads them (oldest 3 weeks). The whole approval process looks broken, Apple team shouldn't approve app with subscriptions without subscriptions added to review. I must immediately publish my app with critical fixes, but I can't. I am devastated, i don't know what to do...

Hello, I am trying to ship the first auto-renewable subscription for my iOS app and I am facing what seems to be a workflow / availability issue involving App Store Connect and TestFlight. Product ID: seka_premium_yearly_ Current situation: The subscription exists in App Store Connect. Its status remains “Waiting for Review”. The subscription page says that the first subscription must be submitted with a new app version and attached through the “In-App Purchases and Subscriptions” section on the app version page. 4. However, this section does not appear on my iOS app version page in App Store Connect. 5. In TestFlight, when tapping “Subscribe”, the app shows: “The offer is not available yet. Please try again in a moment.” Additional context: Paid Apps Agreement is active The app uses expo-iap The product ID configured in the app is seka_premium_yearly_ We are not restricting access by storefront, region, or device configuration Sandbox testing has been attempted, but the issue remains reproducible in TestFlight Question: Is it expected that the subscription is unavailable in TestFlight while the first subscription is still in “Waiting for Review”? Does the missing “In-App Purchases and Subscriptions” section on the app version page indicate an App Store Connect issue? Has anyone encountered this specific first-subscription workflow problem? Any guidance would be appreciated.

Is it mandatory for all developers to migrate to Xcode 26 starting from April 28, 2026? What happens if a developer submits or distributes a build created using Xcode 16 after April 28, 2026? Will it still be accepted or supported? Our app is distributed only via an internal company portal (not through the App Store). In this case, are we still required to build and distribute the app using Xcode 26 after April 28, 2026? If a hotfix is required before our next planned release (July 2026), how safe is it to use the UIDesignRequiresCompatibility flag as a temporary solution, assuming Xcode 26 becomes mandatory? Are there any risks or limitations associated with this approach? What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in such a mixed environment? If the UIDesignRequiresCompatibility flag is used as a temporary workaround, what would be the impact if Apple later removes support for this flag, especially with newer iOS versions (e.g., iOS 26+)? For users who already have the app installed with this flag enabled For users installing the app for the first time after such changes

My iOS app is getting repeatedly rejected under Guideline 4.3(b) Spam. Apple says the app is astrology / horoscope category, but the app is actually a B2B partner dashboard for verified consultants and contains no horoscope content. We already: Removed astrology keywords Renamed the app Changed metadata Restricted login Removed China region Explained multiple times to App Review Still getting same rejection again and again. Has anyone successfully resolved 4.3(b) spam rejection for astrology / consultation / marketplace apps? What exact change finally worked? Should we appeal? Request call? Change bundle? New app? Different category? Need expert advice urgently.

I will keep posting this every week because I simply cannot wait anymore. 7 weeks of waiting is way too much. To me, it is absolute madness in 2026 to wait for months, especially when my passport/ID was successfully verified back in week 1 or 2. To make matters worse, I can't even call the support hotline because the phone option is unavailable and the email assistants only reply with the same automated templates. P.S. If by some miracle Apple Support reads this post or rather, this cry from the soul - and actually wants to help, I have already created two support tickets. Here are the case numbers: 20000109972460 20000109363371

I have an existing app in App Store Connect. I added the SharedWithYou functionality to the app code and tested it on several devices. Everything is working as expected. One of the first steps was to add the com.apple.developer.shared-with-you entitlement to the Entitlements.plist file. This required a round of updates for app identifiers and provisioning profiles. When I upload the production build for testing in TestFlight I receive the following error: 90919: Invalid entitlement. The “” bundle has the com.apple.developer.shared-with-you entitlement, but it doesn’t use the Shared with You framework. Please remove the entitlement and upload a new build. I'm using SWHighlight, SWHighlightCenter, and SWAttributionView in several places throughout my app... I filed an issue in the Feedback Assistant but so far, have not received any response.

Hi, My Digital Services Act compliance submission has been stuck "In Review" since February 13, 2026 — that is 41 days with no update. As a result, my app Move Together (Move Club) is completely blocked in all 27 EU App Store territories during this entire period. What I've done: Submitted DSA trader information on Feb 13, 2026 Submitted support request on March 19 → Case ID: 102848525554 → zero response Submitted second support request today (March 26) via App Setup → Availability and Pricing Phone callback option is not available for this topic App Store Connect Business → Agreements → Compliance still shows: Digital Services Act | 27 Countries | Last Updated: Feb 13, 2026 | Status: In Review I've seen multiple threads here with the same issue. One developer confirmed their DSA was already approved on Apple's backend but not reflecting in App Store Connect — this was resolved via a phone callback. I am unable to get a phone callback for this topic. Can someone from Apple please manually check the status of this submission and update App Store Connect accordingly? This has caused 41 days of lost EU distribution. Thank you.

The Welcome page of AppStoreConnect has slightly changed. Analysis section is out, with an explanation message: News Access Analytics in the Apps section Analytics is now available in the Apps section. Get access to over 100 new metrics, improved filtering capabilities, and new monetization benchmarking reports. Learn more Problem: link does not work. https://developer.apple.com/news/?id=hh6v4b55 And I found nothing in the apps section… Same for you ?

I am submitting a new app, so the subscription has to be submitted as part of the overall app review at first, I can't submit it directly on its own. I didn't know this at first, and submitted the subscription directly. It obviously got rejected with the status "developer action needed". Now no matter what I change I cannot seem to get the status to update from "Developer Action Needed" to a more favorable status. This is obviously a problem because until I can get the status to update, I cannot attach it to submit with my app. Any ideas on how to get the status on my subscription to update to "Ready to submit" so that I can attach it with my binary and submit it with my overall app submission?

Hello, I’m experiencing an unusual issue with App Store review and would appreciate any guidance. I currently have two apps in the review queue: • Tendre – submitted on February 4 • After Midnight – submitted on February 19 The first app has now been stuck in "Waiting for Review" for over a month, and the second one has also not progressed at all since submission. During this time: • I contacted Apple Developer Support multiple times • I submitted support requests (including escalation) • I requested an expedited review However, I have not received any meaningful response or update. What makes this concerning is that typical review times are usually much shorter (often within a few days), and there are no visible issues or rejections. This situation is currently blocking our release, and we are unable to move forward. As these are our first app releases, this delay is critical and is significantly affecting our planned launch. Could this be related to: • an account-level issue • a review queue problem • or something else on Apple’s side? If anyone from Apple or other developers has experienced something similar, I would really appreciate any insight or advice. Thank you in advance.

I would like to confirm this one way or another. I believe that re-downloaders are not included based on those links: https://developer.apple.com/help/app-store-connect/view-app-analytics/view-product-page-optimization-results https://developer.apple.com/help/app-store-connect/reference/reporting/app-metrics (Download metrics section). In our apps 20-30% of downloads are from re-downloaders. Thank you!

Hello, My DSA (Digital Services Act) verification in App Store Connect has been in review for over 10 days. I have already submitted all required documents, and I have not received any updates or requests for additional information. This is currently blocking my ability to update or manage my app. Has anyone experienced a similar delay? Is there anything I can do to speed up the process? Thank you.

Hello everyone, I recently submitted my iOS app for review, but it was unfortunately rejected under Guideline 2.1(a) - Performance - App Completeness. For context, my app is a healthcare application built with Ionic. According to the App Review team's message, they found the app to be incomplete. They stated they were unable to review the app because they couldn't get past the login screen. The Root Cause: Upon investigating, we discovered the issue is related to IP Geo-blocking. Because the app handles sensitive healthcare data, our API provider strictly blocks all network traffic originating from outside of Italy to legally comply with European GDPR regulations. Since the App Review team tests from the US, their requests are being entirely blocked by the firewall, causing the login to fail and the app to look broken on their end. What I have verified so far: I have provided valid demo account credentials in the App Store Connect App Review Information section. I have tested the app thoroughly on physical devices and simulators (iOS 16/17) in Italy and couldn't reproduce any crashes or login issues. My Questions for the Community: Has anyone successfully navigated this situation before? Will Apple accept a detailed video demonstration of the app functioning correctly from an Italian IP? Is it possible to request that they review it using a local VPN? Or is the only reliable solution to build a completely separate "mock" environment with dummy data just for the App Review team? Are there any common pitfalls I might be overlooking here? Any advice on how to properly address this with the App Review Board would be greatly appreciated. Thank you

Hello, I am experiencing a persistent TestFlight installation issue affecting multiple unrelated apps under the same Apple Developer account. For all affected apps: Builds upload successfully to App Store Connect Processing completes normally Builds appear in TestFlight Internal and external testing can be enabled Public links generate correctly However, when attempting to install the app via TestFlight, the installation fails with the error: “The requested app is not available or doesn’t exist.” This occurs: For internal testers For external testers Across different Apple IDs Across different devices With newly created apps After incrementing build numbers After re-uploading builds After signing out/in of TestFlight After regenerating provisioning profiles After creating entirely new app entries The issue currently affects: • TubeChat AI – Apple ID 6752591427 • Vibex – Apple ID 6756860663 • vigilAI – Apple ID 6757738356 Since multiple unrelated apps are impacted in the same way, this appears to be an account-level or App Store Connect backend issue rather than a code signing or project configuration problem. Has anyone encountered a similar situation where TestFlight distribution fails across all apps within a developer account? Any guidance would be greatly appreciated.

Hi everyone, My TestFlight build has been stuck in 'Waiting for Review' for over 32 hours and I'm hoping someone can help or share their experience. The situation: I have an External Testing group with a Public Link set up. The build was submitted for Beta App Review on March 19th but it's been over 32 hours with no update. I have 25+ testers waiting to install the app. What I've tried: Waited patiently Checked App Store Connect multiple times No rejection emails received No issues flagged by Apple Questions: Is anyone else experiencing unusually long review times for TestFlight external builds right now? Is there anything I can do to speed up the process or check if something is wrong? Has anyone successfully resolved this by contacting Apple Developer Support directly? Any advice would be greatly appreciated. Thank you! Apple Support Case ID: 102846633409

Every time I try to focus on the subtitle field in the App Clip section, I encounter an error (as shown in the attached screenshot). This is blocking us from uploading a critical version of our app. We need assistance to proceed with the submission. I’ve already tried using Chrome, Safari and Firefox, but the issue persists.

I just spent way too many hours trying to figure out why my in-app subscription was stuck in “Missing Metadata” in App Store Connect, even though I had filled out everything. If you're here because you're in the same boat, this is the solution Apple doesn't make obvious. The Problem I created an auto-renewable subscription (Kanabloom Premium) and filled in all required fields. The subscription was still marked "Missing Metadata", preventing me from submitting it. The “In-App Purchases” section wasn’t showing up in my App Store version submission, which meant I couldn't even attach the subscription to my app version. I triple-checked the metadata, pricing, tax settings, review screenshot, and even resaved everything, but nothing worked. What I Tried (Before Finding the Fix) Checked that pricing was set up correctly for all countries. Uploaded the required review screenshot for the subscription. Made sure the subscription group existed and was linked properly. Refreshed, logged out/in, and tried different browsers. Read every Stack Overflow, Reddit, and Apple Developer Forum post I could find. Even tried creating a dummy subscription to see if that would reset the system. The Solution: Localizing the Subscription Group Here’s the stupidly hidden requirement that finally fixed it: ✅ Your subscription group itself (not just the subscription) needs a localized display name. App Store Connect requires each subscription group to have at least one localized display name for it to be valid. If this is missing, all subscriptions inside that group will stay stuck in “Missing Metadata” no matter how complete they are. How to Fix It: Go to App Store Connect > Subscriptions > Subscription Group Click on your subscription group (not the individual subscription). Check if there's a localization added under "Group Reference Name." If missing, add a localization (e.g., English) and save. Refresh the page and boom – the subscription will finally be "Ready to Submit." Conclusion Apple really needs to make this requirement clearer. Now that I’ve finally figured it out, hopefully, this post helps someone else avoid losing hours of their life to the same issue. If you're still stuck, double-check that: You’ve set pricing and enabled "Cleared for Sale." You’ve uploaded a review screenshot for the subscription. You’ve signed all App Store agreements and banking/tax documents. Your app's In-App Purchase capability is enabled in Xcode. Let me know if this helped you! I wish I had found a post like this sooner. 😂 This should make for a useful and searchable post in case other devs run into the same headache. Let me know if you want any tweaks before posting! 🚀

Hello everyone, I’m submitting an iOS app to App Review and received Guideline 2.1(b) – Information Needed. Apple says it appears the app may access or include paid digital content/subscriptions and they want details about the business model. In my project, a paywall / premium UI exists in the codebase, and subscription products are configured in App Store Connect for a future release, but in the build currently submitted: The paywall is disabled (not reachable through any UI flow / feature flags are off). There is no purchase flow (no way to subscribe in-app). There is no external purchase (no website/Stripe/etc.). Users cannot access any previously purchased subscriptions (no entitlement access / restore not exposed). Questions: Can the mere presence of a paywall screen / IAP-related code in the binary (even if disabled/unreachable) block App Review or trigger repeated 2.1(b) requests? Is it recommended to remove paywall/IAP code entirely from the review build if it’s not used yet, or is a clear explanation to App Review usually enough? What’s the best wording to reassure App Review (e.g., explicitly stating “no paywall is reachable” / “no restore purchases entry point”)? If products are configured in App Store Connect but not used in the app yet, does Apple expect anything else (demo account, video, notes, etc.)? Any advice from developers who have faced a similar situation would be appreciated. Thank you!