Dear Apple Team, I am writing regarding our pending account termination. Timeline: January 25, 2026: Received Pending Termination Notice January 25, 2026: Submitted appeal and corrective update February 5, 2026: Responded to DPLA compliance notice February 10, 2026: Submitted follow-up via Review Board and Contact Us Current: Corrective update remains In Review, no response received We have submitted corrective updates addressing all identified issues. The corrected version is currently In Review. With the February 24 deadline approaching and no feedback received through any channel, we are concerned about the status of our appeal. We remain fully committed to compliance and respectfully request confirmation that our appeal is being reviewed. Thank you.

I recently had an app rejected for 2.1 - Performance - App Completeness and specifically, “no subscription options available“. The previous build I submitted did have the issue, but this latest one did not, at least as far as I could test. I tested on two different devices using a sandbox account as well as TestFlight and the IAP were visible and working. I also see each IAP pop up correctly within RevenueCat. One thing that may be an issue is I don’t have the section to attach the IAP onto the build before submitting to review. I’ve read through every help article I could find and have triple-checked everything with the IAP is in order. Pricing, localization, screenshot, review notes, signed agreement, etc. I’ve also tried reaching out several times through the contact us page as well as replied to the review, but haven’t received a response. Is there anything I could be missing? Is not attaching them to the build the issue and if so, how can I get them to show up without recreating the IAP with new names? Thank you.

I see many developers struggling with ASO where AI written content does not deliver results, performance analysis is unclear, localization is ignored, App Store optimization is incomplete, and keywords are often poorly chosen. I am considering running two simple group sessions to share practical tips and show clear ways to improve ASO with real effort involved, and I would like feedback on this idea whether offered for a small fee or even for free.

Hey everyone, I’ve been building iOS apps since 2011, released several, took a four-year break, and recently launched two new apps, but the ecosystem feels very different now. Earlier, new apps saw strong first-day downloads and fast Google indexing, while today my App Store pages took weeks to appear and show almost no organic traction without promotion, so I’m curious if others notice this and how developers now gain discovery.

My app has been in review state for 12 days. I have expedited it but it has still not moved. Is there anything else I can do to expedite the review?

My app has been in “Waiting for Review” since January 31. I already submitted a support case (id - 102819325365) last week, but haven’t received a response. I also requested an expedited review but with no response either. This is not a new app, and all previous submissions were completed in less than 48 hours, so this delay seems unusual.

Hey all, I am a first time publisher navigating the App Review process. I want to publish a watchOS only app, but keep getting this feedback: Regarding 4.0, Apple Watch app icon's background color is still black. Based on our investigation, you have included plain black icons. To resolve this issue, it would be appropriate to modify your app's Apple Watch app icon to include a lighter background color to ensure that it is recognizable and appears circular on Apple Watch. I set the following configs: Project -> Targets -> Apple Watch App -> App Icons & Launch Screen -> App Icon set to my Icon Composer file. Checked App Icons Source. I was able to install my build through TestFlight and successfully install on my watch, and the App Icon displays properly there. I also saw a recent Reddit post from another developer facing the same issue. I can't link that post, but will share this post with the OP. I attached what the reviewer sent me with the rejection.

Hi, Got my first submission rejected due to Design - Minimum Functionality and would like to ask for some guidance on what to do. To give some context of my app. My app is quite simple but solves a common issue in my home town. During the winter month, every street will have a certain time when parking is forbidden. This results in everyone having to move their car several times a week to avoid getting tickets. Every time you move, you need to note and remember when to move it again, etc. A parking ticket for forgetting is around 140 USD. My app aims to solve this by letting the user press a button which makes the app use the current GPS location to fetch the parking relevant parking restriction and create a notification the day before, reminding the user to move their car. Simple UI and nothing fancy. I've also created onboarding that gives relevant information the first time a user open their app. I'm a bit on the fence on what I should do to pass. In my opinion, the functionality is more than a website because it uses GPS, creates notifications, loading spinner when parking restrictions are being fetched, has onboarding, etc. I think an issue that might cause the reviewer to dismiss it is that it currently only work in my specific town - it uses certain APIs to fetch the parking restrictions. So, should I try to create more functionality (not sure what) or do I need to clearly argue my case and demo my apps functionality via recordings? Thanks in advance for any help and guidance :)

Hello, I’m looking for guidance regarding a new app submission that has been in “Waiting for Review” status for 6 days now, with no change or additional communication. This is a brand-new app submission (not an update). There have been no metadata changes or rejections — it has remained in the waiting state since submission. I completely understand that review times can vary depending on workload and complexity. I just wanted to check whether this timeframe is currently normal, or if there may be something specific I should verify on my end. The app is an educational medical application, and all content is original. There are no unusual entitlements, external payment systems, or restricted APIs involved. If anyone from Apple or fellow developers has insight into whether extended “Waiting for Review” times are currently common, I would appreciate your input. Thank you in advance.

Hello, My new app (App ID: 6757254070) has remained in the “Waiting for Review” status since February 1 (UTC+9). Because the review process seemed to be taking unusually long compared to my previous experiences, I submitted an inquiry (Reference ID: 102812788306), but I have not yet received any response. For additional context, the app was originally submitted on January 23 and remained in the “Waiting for Review” state for eight days. As I was concerned there might have been an issue with the review queue, I canceled the submission and resubmitted the app on February 1. At this point, I am wondering whether the prolonged waiting time is simply due to a heavy backlog in the App Review process. Thank you very much for taking the time to read this. I hope you have a great day.

I needed to change the bundleid in my app, so I created a new app and used the build I created with the same source code and deleted my old app completely, but my app is rejected for spam

Hi, I'm here hoping for some help or advice in terms of a critical situation I'm currently facing. I've submitted an iOS app more than one month ago, it was quickly got review and rejected twice, and when I re-submit the third time with new build, it then was stuck in the "Waiting for review" status for about 3 weeks. Then, I decided to withdraw the submission and re-submit again, but it doesn't work and remain "Waiting for review" status until now. During these waiting period, I’ve contacted Apple Support multiple times through mails, and received confirmation that my expedited review request was approved. However, no progress has been made since then. Here is a quick summary of the timeline Initial submission: July 29, 2025 Rejected due to Guideline 4.2.2 & 2.1: July 30, 2025 Second submission: Aug 4, 2025 Rejected due to Guideline 4.2.2 & 4.2.0: Aug 6, 2025 Third submission: Aug 6, 2025 Withdraw third & create forth submission: Aug 25, 2025 If anyone from the App Review team sees this post, or if any developers have experienced a similar situation and can offer advice, we would be truly grateful. Thank you in advance for your time and support.

Hello everyone, I wanted to check if anyone else has experienced longer App Review delays recently. Our recent app submission has been in the “In Review” status for more than 7 days (since Jan 15, 10:44 PM). In our previous submissions, reviews usually started or completed within a few days, so this delay feels unusual. Current situation: No messages or rejection notes from Apple No metadata or compliance issues flagged Status remains “In Review” without updates I’d appreciate guidance from the community: • Is this type of delay normal these days? • Could this indicate a manual or extended review? • At what point should we contact App Review directly? • What is the best way to contact App Store / App Review support regarding a stuck review? If anyone has faced a similar delay and can share their experience or advice, it would be very helpful. Thank you in advance for your help.

Hello, We have applied for the Apple Developer Program under a government organization account. After submitting the enrollment, we received a confirmation email stating that the request was received and that we would be contacted after verification of authorization to bind the organization to the Apple Developer Program legal agreements. However, it has been quite some time, and we have not received any further updates regarding the verification process. We would like to understand: What is the usual verification timeline for government organizations? Is extended verification common for government entities? Is there anything additional we should do from our side to help move the process forward? If anyone has experienced a similar situation or can share guidance, it would be greatly appreciated. Thank you.

I recently released the first version of my app, and it was discoverable via App Store search. After pushing an update with bug fixes and improved keywords/category, the new version went live and showed as “Ready for Sale” within hours. However, since the update, the app no longer appears in App Store search results - even when searched using its exact name. It’s still accessible through the direct link. Any insights or guidance would be greatly appreciated!

I have been exploring App Store Optimization and noticed that Apple primarily uses the App Name, Subtitle, and Keyword field as the main text based ranking signals according to official and third party sources. Are these the only factors that truly impact iOS ASO, or do elements like the app description and promotional text indirectly influence visibility, conversion, or ranking updates over time, and how frequently should subtitles and keywords be revised after launch.

Hello, My app update was rejected under Guideline 2.3.4 (Accurate Metadata) with the note that the app preview includes “framing around the video screen capture.” Apple attached four images to the review. I reviewed them carefully, and they appear to show full screen gameplay without borders or visible background. I am attaching two of those images here for reference. I am trying to understand what Apple might be interpreting as “framing” in this case. Has anyone encountered a similar rejection where the preview looked full screen but was still flagged? Any insight into what reviewers typically expect or what subtle issues might trigger this would be very helpful. Thank you.

Hello, I’m experiencing repeated rejections related to Guideline 2.1 – App Completeness for an iOS app using auto-renewable subscriptions, and I’m struggling to understand what is missing, as the purchase flow works correctly in sandbox and TestFlight. App setup: iOS app built with React Native (Expo + react-native-iap) Auto-renewable subscriptions: • Monthly: €4.99 • Yearly: €39.99 Paid Apps Agreement accepted Subscriptions configured and active in App Store Connect Privacy Policy and Apple Standard EULA included: • Visible inside the app on the subscription screen • Added in App Store metadata What App Review reports: App Review states they are unable to buy the in-app purchase, resulting in a rejection under Guideline 2.1 (App Completeness). What works correctly: getSubscriptions() returns valid products in sandbox Subscription titles, prices, and durations are displayed in the app UI requestSubscription() is triggered when tapping the subscribe button Apple purchase sheet appears and completes successfully in: • Sandbox testing • TestFlight (external testers) What I’ve verified: No conditional logic blocks purchases in review builds Purchase button always calls requestSubscription purchaseUpdatedListener and purchaseErrorListener are correctly registered No hardcoded prices; prices come from StoreKit Same behavior on iPhone and iPad Question: Is there any known limitation or requirement in the App Review environment for auto-renewable subscriptions that differs from sandbox/TestFlight when using a custom subscription UI (not SubscriptionStoreView)? If App Review requires a specific implementation detail (StoreKit 2, SubscriptionStoreView, or something else), I would really appreciate clarification, as this is not explicitly stated in the rejection. Thank you for your help.

Hi, Our app (Tenkobo) received a rejection notice after review due to the fact that we use Gemini AI since 3 builds ago. Since then, we have been improving the disclosure of the data we collect, explicitly stating all the data, introducing a new feature that checks granular consent and syncs consent state for the user to the backend, and controls for whether to send to the Gemini API service for that feature depending on consent state for the user. Moreover, this feature is a premium add-on to a module that already does most things locally on the device and sends to our cloud infrastructure to allow storage and sync when users use multiple devices. It is a multi-platform app. However, despite every improvement, we keep getting the same Rejection reason that "The issues we identified still need your attention. I have asked for help or even that the rejection reason be more specific, but nothing. I have send pictures, and in this last rejection about 8 hours ago, I had to reply with a video showing that what they are asking for is already there. Why does the system work like this? It is frustrating, especially if a development team needs to be guessing how much is too much. We feel we are now close to removing the feature completely out of frustration, and it is very useful feature for our users based on the feedback we received from the android users (the android app has been live since about 6 weeks ago.) Please, what else can we do? We have requested a review meeting with App Review, the entire product plans are now on the verge of being irredeemably disrupted, and the company could go bankrupt just because our reviewer does not deem it fit to tell us exactly what they are expecting to see. Anyone with experience in this area should kindly provide some advise on what to do now. Thank you.

I have a desktop application developed in SwiftUI that shows property locations on the map. That's NOT the main feature. IF you give the application permission to access your location, the blue dot will appear on the map. If you don't, the blue user dot won't appear. That's the only difference with location services. In other words, the application has no use of user's current position beyond showing it on the map. Since it's just the matter of showing or not showing the blue dot on the map, the application doesn't really need to use the location service. Anyway, the reviewer is talking about something else by rejecting the application in two aspects. Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage Guideline 5.1.5 - Legal - Privacy - Location Services As I said earlier, the application only wants to show the blue dot on the map so that you can see your property locations relative to your current location. In code, it's something like the following. Map(position: $propertyViewModel.mapPosition) { ForEach(propertyViewModel.properties) { property in Annotation("", coordinate: CLLocationCoordinate2D(latitude: property.lat, longitude: property.lon)) { ... } } UserAnnotation() } So I'm hit with two rejection reasons with this one line. UserAnnotation() And the reviewer is talking about something like the app is not functional when Location Services are disabled. To resolve this issue, please revise the app so that the app is fully functional without requiring the user to enable Location Services. Well, I can remove the UserAnnotation() line if I want to put this application through the review process. Nothing will become dysfunctional, though, if you decide to reject permission request. So would you remove it or would you play along with this reviewer if you were me? It's been three or four days since rejection. As you can imagine, the reviewer doesn't bother to answer as to What are the exact coordinates that the application has allegedly collected What won't work as a result of location permission request refusal. This isn't the first time I get my app rejected. I've probably had 150 to 200 of them rejected in the past 15 years. And just because a reviewer rejects your app for a bizarre reason, would you give in? Remove this feature and that feature because the reviewer is incompetent such that he or she makes his or her decision based on imagination? What do you think?