My app has been stuck on 'Waiting for review' for over 4 days. Unlike before, I will get feedback within 48 hours, but now I have been 4 days in and no one seems to have checked the app at all. Any advice?

This is my first iOS app release and I’m a bit confused. The initial version was reviewed in under 12 hours (rejected), and the corrected version was approved just as quickly. But my Product Page Optimization with only screenshots has been stuck in “Waiting for Review” for four days. Do these get reviewed only with new versions, or should I just wait it out?

It's been more than a week since the App was validated and published. Yet, the IAP (subscriptions) are still waiting for review. I've sent an email to Apple 5 days ago on the topic and i'm still waitinf or an answer. I have to ship a complete version to my client quickly, can anyone do something, like an admin passing by by any chance ? Or does anyone have a tips/trick to unstuck me ? :') Note : I've tried to send another version with a note saying "please review my IAP", the version got accepted but the IAP are still not reviewed... Thanks in advance, Have a good day.

Hi Team, I have my app's version 1.15 available in App Store. Recently I had a new build 1.15.1 reviewed and deployed in app store. But due to some issue, i need to go back to 1.15 and remove 1.15.1 from store. What options do i have and best course of action? Regards, Sandeep

Hello, can someone share how long it takes to verify payment data? It's been more than 30 days, and it still says "under moderation".

I use import * as StoreReview from 'expo-store-review'; In my onboarding I do: const requestAppRating = async () => { try { console.log('Requesting app rating via StoreReview'); if (await StoreReview.isAvailableAsync()) { console.log('Store review is available, requesting rating'); await StoreReview.requestReview(); } else { console.log('Store review not available on this device'); // Fallback: show alert encouraging manual rating Alert.alert( 'Rate Oddible', 'Enjoying the app? Please take a moment to rate us on the App Store!', [ { text: 'Maybe Later', style: 'cancel' }, { text: 'Rate Now', onPress: () => { console.log('User chose to rate manually'); // You can add a link to the App Store here if needed }} ] ); } } catch (error) { console.error('Error requesting app rating:', error); } }; This works perfectly in my development build but my production build in the app store does not pop up to request a review from a user. Any idea why this could be the case?

Hi everyone, We’re a U.S.-registered company and just submitted our primary app for review. We tried to be proactive: our initial submission included very detailed Notes to the Reviewer to avoid back-and-forth. Despite that, our first rejection asked for items we had already covered in Notes. Within ~30 minutes we replied in the Resolution Center with expanded details. The app went back to review and about 90% of the concerns were resolved. After that, we could see from our logs that the reviewer actively tested the app and requested additional legal documentation. We provided everything promptly, but the next response was a rejection under Guideline 4.3(a) – Design – Spam. There was no additional explanation tying 4.3(a) to anything specific in our binary or metadata, and this guideline hasn’t come up for us before. Here’s what we already provided via the Resolution Center: Test credentials and clear steps to access all app areas Detailed terms and in-app disclosures Executed agreements with our partners Copies/links to partner licenses Given that context, a 4.3(a) outcome is confusing. We don’t publish template/duplicate apps, and we’re not keyword-stuffing metadata. The reviewer who requested legal docs appeared to be actively testing, but the final 4.3(a) decision didn’t include clarifying notes. We’re very concerned about this situation and would truly appreciate your advice on how to move forward.

I am trying to add webhook subscriptions for TestFlight build processing completion and TestFlight beta build review completion events. These were showcased in the WWDC25 session: https://developer.apple.com/videos/play/wwdc2025/324/ Currently, I am able to receive webhook events for distribution updates, and the corresponding checkmark option is available in the App Store Connect portal. However, there is no checkmark option in the portal to subscribe to beta build-related events. In the video, there is clearly a checkmark option for the beta review event subscription (at 4:55). The current documentation also does not mention beta processing and beta review event subscriptions. It only lists the event types that are visible in the web portal: https://developer.apple.com/documentation/appstoreconnectapi/webhookeventtype When I try to add the BUILD_BETA_DETAIL_EXTERNAL_BETA_STATE_UPDATED event (as shown in the video at 6:10) via the PATCH API request, I get the below error. "errors": [ { "id": "****-****-****-****-*********3851", "status": 409, "code": "ENTITY_ERROR.ATTRIBUTE.TYPE", "title": "An attribute in the provided entity has the wrong type", "detail": "'BUILD_BETA_DETAIL_EXTERNAL_BETA_STATE_UPDATED' is not a valid value for the attribute 'eventTypes/3'.", "expectedValues": [ "APP_STORE_VERSION_APP_VERSION_STATE_UPDATED", "BETA_FEEDBACK_CRASH_SUBMISSION_CREATED", "BETA_FEEDBACK_SCREENSHOT_SUBMISSION_CREATED" ], "source": { "pointer": "/data/attributes/eventTypes/3" } } ] } The App Store Connect web portal also does not provide a checkmark option for subscribing to this event type. My questions are: Are the TestFlight build processing completion and beta build review completion webhook events coming soon, or do they already exist? Are there any other ways to get beta build events apart from polling?

I can't accept a TestFlight invitation. I seemed to have gotten myself into some situation that I have been unable to resolve. Here's what I did: Added my work Apple Account to TestFlight. Received an email for TestFlight invitation. Opened link in browser to view invitation code. Entered that code on a device that was signed into a different Apple Account (my personal account on my personal iPhone). The app did install on my personal iPhone, but now I can't accept the invite on my test device, which is signed into the Apple Account that is actually part of the TestFlight group in App Store Connect. I have tried deleting/re-adding/re-inviting my work Apple Account to TestFlight several times. On my personal iPhone, I have tapped on "Stop Testing" in the TestFlight app and deleted the app I installed there. But I still cannot accept the invite on the test device signed into my work account. When I enter the invite code to redeem, it says: This invitation cannot be accepted because your Apple Account, , has already been asso... The full message is actually truncated, so do not know what it says after "asso...". Is there any way to get out of this situation and accept the invite on the test device using my work Apple Account?

App Store Connect rejects the build with the following error: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90058: This bundle is invalid - The value for key CFBundleVersion [iphoneos] in the Info.plist file must be a period-separated list of at most three non-negative integers. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion But we double-checked at the app level; in all places the CFBundleVersion and versions is mentioned in the correct format. Even though we tried to upload via Xcode and Transporter, both show success. but the build is not reflecting in TestFlight. Receive the above error message via mail. data: { "attributes": { "cfBundleShortVersionString": "3.25.9", "cfBundleVersion": "25", "p Validated with the delivery log, but the delivery log also shows correct versioning only.

My app (com.onon.app) consistently fails App Store Connect validation (ITMS-90207: Invalid Bundle) despite passing all local diagnostics (valid arm64 binary, correctly signed, appropriate entitlements). Is there a known issue with Apple's validation server, or are there obscure validation rules I might be missing?" Diagnosic info Architecture Check (lipo -info Runner): Non-fat file: Runner is architecture: arm64 Code Signing Verification (codesign -vvv Runner): Runner: valid on disk Runner: satisfies its Designated Requirement Local Environment Details: Operating System: macOS 15.5 24F74 (arm64) Xcode Version: 16.3 (16E140) Transporter Version: 1.3.3-13326 Flutter Version: 3.29.0 CocoaPods Version: 1.16.2 Has anyone encountered a similar issue with a Flutter app that passes local code signing checks but is rejected by App Store Connect? Are there any known edge cases or obscure validation rules that aren't covered by standard code signing diagnostics?" I've also opened a Technical Support Incident with Apple Support and am waiting to hear back from them. (Apple developers: my case number is 102647258274)

Is it ok to maintain dual langauge text on a mobile app bottom navigation tile when it cannot be localized. Will the app be acceptable from a publishing point of view?

We are currently using Swift to develop our Apple application, and we are considering switching to a cross-platform solution as part of our technical evaluation. Recently, React Native (RN) has been revitalized, and it supports application hot updates, allowing us to update the app without going through the app store release process. Additionally, we have conducted some market research and found that many apps are using RN and leveraging its hot update functionality for app updates. I would like to know whether RN's hot update feature is compliant with Apple's policies and if there is any risk of the app being removed from the App Store. I hope to receive some guidance on this matter. Please do not delete this post—this is just a help-seeking post from an iOS developer without any malicious intent.

Hi, I have an iOS app that only makes GET requests to my own API (hosted on Cloudflare Workers). The app only receives information for its settings (like whether to show a coupon code). It does not send, collect, track, or share any user data, and I do not store or process any personal information. I understand that technical details (like IP address, user-agent, device information, etc.) are automatically sent as part of the internet protocol. Since I don’t log or use this data, I’m unsure if it counts as “data collection.” However, it is possible that Cloudflare collects this information for security purposes and deletes it after some time. Question: In this case, can I select “No data collected” in the App Privacy section of App Store Connect? Thanks!

We have been developing our game “Ailem Olur Musun” for 8 months and submitted it to the App Store. However, our application was rejected under Guideline 4.1 – Copycats. Our game is a completely original project. Its story, visuals, logo, and design were all created from scratch by our team members. The main character of the game is a delivery worker, and the drawing we made for this character is used as the game’s symbol. Despite this, our application was rejected on the grounds that it was considered to be “imitating another popular game.” This game has also been published on the Play Store and has achieved a significant number of downloads and reviews. How can I best explain this to the review team?

I’m working on an iOS app and need help with ASO to find the best keywords for title, subtitle, description, and keyword field. Can anyone suggest free tools that show keyword volume, difficulty, and competitor keywords?

We are having external testers use TestFlight through a public link. Without any prior notice, all of our TestFlight builds suddenly expired, and even newly uploaded builds encounter errors before being released. We were able to resolve the issue twice through inquiries, but the same situation occurred again immediately. We are now making a third inquiry, but could you please advise us on how to avoid this problem?

Since the App Store only allows adding one native app, I want to disable my “Mac Catalyst” version app to enable its “Designed for iPad” version. How can I achieve this?

Hi everyone, I’m relatively new to the App Store and currently navigating a review situation. I’d really appreciate any advice or perspective. Here’s the timeline: Aug 11: I submitted version 1.3.0 of my app (App ID: 6742771536). Aug 12: The status moved from “Waiting for Review” to “In Review.” Since then, it has remained in In Review for about 13 working days without further updates. In the past, my submissions have typically moved through review more quickly, so I’m wondering if there’s anything I might be overlooking. I do have a pre-order release scheduled for Sept 2, 2025, so I want to make sure everything is on track. ❓ My questions: -Is it normal for some apps to remain in “In Review” for this long? My previous version was approved within a few hours. -Should I cancel the review and resubmit? I saw folks here mentioned that is a bad idea. -Could there be any metadata or review note details I should double-check? -For newer developers, is this something that occasionally just happens as part of the process? Thanks in advance for any guidance — I’d love to learn from the experience of others here.

I am a CTO and iOS app developer implementing Two-Factor Authentication (2FA) in our application. Our app now requires 2FA for all user accounts. We need guidance on how to provide test access to the App Store Review team. Since the login factors are device binding and Biometrics or password, a tester from your review team will never be able to fulfill the device binding requirement since the account has not been setup on their device. We cannot disable 2FA for some test accounts, as suggested in other forum posts, as this would introduce a major security risk for our application. What is the reccomended approach here? What information should we include in the "App Review Information" section to help reviewers access our app?