Hello App Review Team, We kindly seek your assistance regarding our app, which has remained in the “Waiting for Review” status since our initial submission on July 30. In order to refresh the process, we have submitted several new builds. We also reached out via email and submitted an expedited review request, but unfortunately, there has still been no progress. It has now been close to a month, and this extended delay is starting to impact our app’s revenue. We would greatly appreciate it if you could let us know whether there are any issues with our submission, or if additional materials are required from our side to help move the review forward. Our Appid: 6630392320 Thank you very much for your time and support.

Hello fellow devs and Apple engineers, I want to discuss with everyone about App Preview videos on the App Store. My app NFC.cool is an NFC reading and writing app which interacts with NFC tags that need to be held to the top of device frame of an iPhone. As you can see, this is how my app works and I would like to show that to users on the App Store and present my app in the best way possible. However I keep fighting with app review about device frames and/or "real" hands in my app preview videos. Sometimes I get a reviewer that is ok with the video and sometimes not. In screenshots device frames are accepted and very common. Why are they not allowed in app previews? It doesn't make a lot of sense to me. And to be honest, I regularly see app previews with device frames on other AppStore pages. Here is the app preview that got rejected lately: https://www.youtube.com/shorts/qTDBGecK0w0 I can easily agree with the hands (even though they are not real, they are a render). But the device frame helps the user to understand what my app does and how it works. Ideally I would like to have some Apple staff to see this post here and hopefully start a small wave that will change the guidelines in the future. Here the message from the reviewer: Product Page Optimization Guideline 2.3.4 - Performance - Accurate Metadata The app preview for NFC Read Write Socials Video includes content that does not sufficiently show the app in use. Specifically, the app preview: Includes device images and/or device frames. Displays real hands. App previews should allow users to see what the app does and how it will >appear on their device when the preview is played in full screen. My answer: Hello, these are not real hands. These are renders. The video is accurately showing what the real use of my app. Please keep in mind that an NFC tag has to be held from the outside to the device to interact with my app. The guidelines definitely support what I did in my video. Please take another look. Thank you. Following the guidelines: 2.3.4 …You can add narration and video or textual overlays to help explain anything that isn’t clear from the video alone. https://developer.apple.com/app-store/review/guidelines/#accurate-metadata Use graphics and transitions. If you need to demonstrate how interaction or navigation works within your app, you may add graphic elements, such as touch hotspots. We recommend capturing the native UI resolution rather than zooming in on the view. Ensure that any transitions between scenes don’t imply functionality that your app doesn’t include. Aim to use straightforward transitions, like dissolves and fades. https://developer.apple.com/app-store/app-previews/ What's your opinion on this topic?

Hello, I submitted an app on August 6th, and it is still in the "Waiting for Review" status. I contacted Apple a week ago, and they politely advised me that this is a normal situation and that I should continue to wait. Has anyone else experienced a similar delay? If so, I would appreciate it if you could share how it was resolved. App ID: 6749074330 Thank you.

Olá, pessoal! 👋 Estou implementando a solicitação de avaliação no meu app e percebi um detalhe que pode gerar um problema na experiência do usuário. A mensagem exibida atualmente diz: "Toque em uma estrela para classificar na App Store." O ponto é que essa tradução pode induzir o usuário ao erro. Ao ler "uma estrela", o entendimento natural é tocar justamente na estrela de número 1, o que resulta em uma avaliação baixa — mesmo que o usuário estivesse satisfeito com o app. Creio que uma tradução mais adequada e neutra seria algo como: "Toque nas estrelas para classificar na App Store." ou "Escolha quantas estrelas deseja para avaliar o app." Isso evitaria o viés negativo e refletiria melhor a intenção da funcionalidade. Alguém mais já percebeu isso? Existe algum canal oficial para sugerir ajuste nessa tradução? Obrigado! 🙏

Product Page Optimization reviews sometimes take longer than app updates and it is normal to wait a few days so no action is needed yet.

Hello, We're working on an application using (https://developer.apple.com/support/hce-transactions-in-apps/) We have some questions App review with this capabilities: There are 4 mains points written on the page, does all are required? Test login details Does it need to be production or testing environnement? Can it be a URL/Deeplink or is it a mandatory login/password credential kind? At least one test payment credential that can be provisioned and used in your HCE app for the purposes of making an NFC transaction That's the difficult part, can we have more details about this condition? Does it need to be a production card or a testing card? Screenshots or video of your app being used at a terminal for an NFC transaction OK, make sense Video of your app demonstrating an implementation of the Presentment Intent Assertion API OK, make sense Thanks François

Hi, our app is in waiting for review status for more than a week, we again have uploaded one 2 days ago, hoping the status would change, it is still in waiting for review status, we have another version which needs to be uploaded apart from the one waiting for review, as our SSL is expiring on the beginning of next month, please help as this will make our app inaccessible to our customers.

Hello, I’m new here. I'm developing an iOS app and I’d like to know whether it is possible to detect if a phone call is being recorded by another app running in the background. I’ve already reviewed the documentation for CallKit and AVAudioSession, but I couldn’t find anything related. My expectation was that iOS might provide some callback or API to indicate if a call is being recorded (third-party apps), but so far I haven’t found a way. My questions are: Does iOS expose any API to detect if a call is being recorded? If not, is there any indirect, Apple's policy compliant method (e.g., microphone usage events) that can be relied upon? Or is this something that iOS explicitly prevents for privacyreasons? Expecting solutions that align with Apple’s policies and would be accepted under the App Store Review Guidelines. Thanks in advance for any guidance.

Hi everyone, Our game has been stuck in "Waiting for Review" status for 7 days now and we’re starting to get very concerned. Details: Game category: Games/Puzzles Version 1.0 All required metadata completed Age rating: 4+ We’ve tried the following steps multiple times: Removed and re-submitted the build four times to draw attention to the submission Submitted an expedited review request (no response or movement) It seems unusually long considering that the typical review time is just a few days. Has anyone else run into similar delays lately? Is there any other way to escalate the issue or get Apple’s attention? Thanks in advance for any help or advice!

Hi All, I am submitting my first app to App Store but unfortunately, it has been rejected 3 times in a row. Every time , same reason 2.1 App Incompleteness. My app requires login via phone number and OTP and i have provided all the demo details required for creating an account but their response is same every time that they cannot login. No error detail has been shared by the review team. The screenshot suggests that Device is not connected to Internet and i have mentioned in instructions to use a stable internet connection I have tested the app on 2 iPhones and 1 iPad and found no such issue. My server has not received any login request as well to verify if they tried logging into the app. Please suggest what i can do in this scenario or any specific reason that the problem is just with them and not with any of my testers Thanks.

My app has been stuck in "Waiting for Review" status since July 25, 2025 (24 days and counting), far exceeding Apple’s typical review timeline. Despite multiple checks, I’ve received no updates or communication from App Review. App Details: App Name: [HKCoiner] Bundle ID: [vn.app.hkcoin] Apple ID (SKU): [6747101743] Is this delay related to a known system issue? How can I escalate this to Apple’s review team? (Email/phone options?) Are there hidden rejections or metadata problems not shown in App Store Connect? I hope to get help.

Hello, My app Juicy Defend - Fruit vs Robot has been "waiting for review" for +6 days. I want to know if this hold up is because of something I need to do on my end or if this is normal. Thank you! Khoa

Not able to enable external testing of my app due to phone number validation. The error reports "Make sure the contact phone number only contains numbers and try again.". Attached is a dummy phone number with the same validation result.

Hello, My app Native Talk! has been "waiting for review" for +24 hours. I want to know if this hold up is because of something I need to do on my end or if this is normal. Thank you! Matt

Hello Apple Review Team, We truly appreciate your hard work, but our app has been stuck in “Waiting for Review” status for almost a month with no updates. During this time, we have: Sent emails explaining our situation Submitted expedited review requests Uploaded new builds to refresh the status However, we still haven’t received any response. Could you please let us know if there is any specific issue with our app, or help escalate our review manually? Our App id: 6744839843 Thank you for your attention and support.

Hi, I'm working on a large application, and the designers have proposed a new look for the tab bar. The app has been in development for 14 years, and while many views are now in SwiftUI, navigation between screens is still handled in UIKit, since most screens are still UIKit-based. Currently, we're using the native UIKit TabBar. I'm going to check if it's possible to customize the appearance of the native TabBar. However, I remember that over 10 years ago, when I changed the height of the TabBar, the app was rejected during review for not complying with Apple's Human Interface Guidelines. It looked something like this: An app rejection related to a tab bar's height update in Swift, likely due to not adhering to Apple's Human Interface Guidelines, can be addressed by ensuring the tab bar's height remains at the default 49 points and avoiding any modifications that don't align with the HIG, according to Apple's documentation. How does it look nowadays? Has anyone here submitted an app to the store with a heavily customized TabBar height and had it approved? In UIKit, I see it's possible to do something like this: https://stackoverflow.com/questions/23044218/change-uitabbar-height Would something like this pass app review without issues? Do you know of any apps that have a non-standard, significantly increased TabBar height?

Hi everyone, I'm facing a frustrating App Store rejection that I can't seem to resolve. My app was rejected under Guideline 2.1 - Information Needed with the following message: "The app uses the AppTrackingTransparency framework, but we are unable to locate the App Tracking Transparency permission request when reviewed on iPadOS 18.5." However, in my latest version (2.9 Build 18), I have: Removed all SDKs that collect IDFA or perform tracking. Removed the AppTrackingTransparency framework entirely. Removed the NSUserTrackingUsageDescription key from Info.plist. Confirmed that no third-party SDKs are accessing IDFA or similar. Not using the app_tracking_transparency package (I'm using Flutter). I included a detailed review note explaining all of this, yet the app still gets rejected for not showing the ATT prompt — even though ATT is not used at all. Also, I can't update the App Privacy section until this new version is approved, which still reflects tracking from a previous live version (2.3). Has anyone faced something similar? Questions: Is there a way to confirm what part of the build might still be triggering ATT detection on Apple's side? Could an unused pod or leftover reference be the issue? How do I fully verify that ATT is not linked anywhere in the final binary? Any guidance or tips from others who’ve resolved this would be hugely appreciated! Thanks

Hello, We are currently facing an issue where our app was removed from the App Store due to an alleged policy violation. We submitted an appeal on July 25, 2025, but we have not received any confirmation, response, or update since then. This prolonged silence has seriously impacted our operations and caused numerous user complaints and negative feedback. We would appreciate any guidance on: How to verify whether our appeal has been received and is under review. How to escalate the case to get timely attention from the App Review Team. We are fully committed to cooperating with Apple and making any necessary adjustments to comply with guidelines. Thank you very much for any assistance or advice.

Hi, I've been unable to reproduce an issue that is getting our new app flagged in App Review. Login/Registration via passkeys fails for the testers every time. We've provided an alternative sign in method, but I'm still curious why this might happen. When testing locally and in TestFlight, registration and login with passkeys has worked consistently. We receive ASAuthorizationError.Code.failed (1004): The authorization attempt failed. Do reviewers have special devices that do not support passkeys? What are some reasons that this code would fail? We've tested on the same device (iPads, iPhones, etc.) with different password managers and haven't run into this issue. We do not offer another sign in or registration for non-review users. We have a demo mode login provided to reviewers. Any help is appreciated, thanks.

Hi everyone, We submitted our app update for review on July 25, 2025, and when we didn’t hear back, we resubmitted on August 4, 2025. Unfortunately, both submissions are still stuck at “Waiting for Review.” This is very unusual for us, as our app has been live on the App Store for over two years now, and reviews have typically taken no more than 1-2 days in the past. We are a small startup urgently trying to release a new version to address critical issues our users are facing. The extended review delay is significantly impacting our users’ experience, and we’re concerned about the growing frustration among our customer base. We have tried reaching out to support but haven’t received any updates so far. We’re posting here in hopes someone can provide guidance or help escalate the review process. Thank you for any assistance you can offer.