Hi everyone, Our game has been stuck in "Waiting for Review" status for 2 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!

When attempting to submit our application for review, I encountered an error message that does not specify the actual cause of the failure. Since the error message provides no indication of the underlying issue, I am unable to identify what is preventing the submission. Could you please advise what should be done? Noting that all app information is accurrate and filled and this is the first time I face such an issue.

We have a React Native iOS app where we are planning to adopt a micro-frontend architecture using Re.Pack. Some modules of the app would be hosted on a CDN and loaded on demand at runtime instead of being bundled fully inside the app. Is this approach compliant with Apple’s App Store Review Guidelines? Specifically, would loading JavaScript bundles or features dynamically from a CDN (instead of shipping all modules within the app binary) be acceptable for App Store approval? If there are any restrictions or best practices we should follow for this type of setup, please advise.

I have ceated a new version, and the status of it is "Prepare for submission", is there a way to delete it, kindly check the attached image.

Hello, PrivacyInfo.xcprivacy Is primordial and without it the app is rejected from the Store I believe. All 5 ressources I had found related to it, mention XCODE, or explain how to add the code to langages that I don't use (Switf i think?) etc. I am building the app thought CI/CD, so prior to building it the app does not have privacy manifest and there is not way to generate it automatically without xcode it seems. My app is written in Flutter prior to becoming an iOS app. I am seeking for a method to do that. Thanks.

Hello everyone, We've had our app rejected twice under Guideline 3.2.2 regarding charitable donations, and we're seeking clarification on the correct implementation. We've read the guidelines but want to confirm the technical approach with the community's experience. The Rejection Reason: Apple states: "We still noticed that your app includes the ability to collect charitable donations within the app..." They specify that since we are not an approved nonprofit, we must use one of the alternatives, primarily: "provide a link to your website that launches the default browser or SFSafariViewController for users to make a donation." Our Current (Rejected) Implementation: User taps a "Help" button in our native app. A native modal appears inside our app where the user enters their donation amount and email address for the receipt. The user clicks "Donate," which then opens an SFSafariViewController to our website's payment page (e.g., Stripe, PayPal). The amount and email are passed as URL parameters to pre-fill the form. Our Questions for the Community: Is the issue solely the fact that we have a native modal for data entry? We understand we cannot process the payment in-app, but we thought collecting the intent (amount, email) was acceptable before handing off to Safari. What is the definitive, compliant flow? Option A: Should the "Help" button do nothing more than open an SFSafariViewController to a generic donations landing page on our website (https://ourwebsite.com/donate), with no data pre-filled? The user must then navigate and enter all information on the website itself. Option C: The rejection also mentions SMS. Has anyone had success implementing a "Text-to-Donate" link instead of a web flow? Wording: The button in our app currently says "Donate". Should this be changed to a more passive call to action like "Visit Website to Donate" to make it absolutely clear the transaction is external? We want to ensure our next submission is successful. Any insight, especially from developers who have successfully navigated this exact rejection, would be immensely helpful. Thank you.

Apple must comply with U.S. laws. Under U.S. sanctions regulations and export controls, Apple cannot do business with certain apps or developers connected to U.S. embargoed countries or regions. We have recently identified that the app is subject to U.S. sanctions regulations or export controls. Therefore, we are unable to approve the app at this time. This area of law is complex and constantly changing, and should changes be made to U.S. law in the future you can resubmit the app. You can contact the U.S. Department of the Treasury or the Bureau of Industry and Security of the U.S. Department of Commerce should you have questions. Our app we did is for mainly for syria , Any idea how it can be solved , its a classified app

Hi. My friend and I are new to app developing. We made an app together and I made one alone on the side. But we are not joined. we each pay seperate taxes and not som scam design post of apps. Apple flagged both with spam design, so we assumed it was related. but not sure anymore. app1 is a travel related app operating globally. we have IAP but also destination inspirarion and global food information, which is free in the app. app2 is about one single country and has a lot of information about travelling in that country and some IAP too. IAP in both app are the same product, but unique in appstore. it only exists on websites apart from these two apps. both are made in adalo so even though the colours are different they are made in the same system. we have tried so much to get app1 through but they keep rejecting with spam design. they approved app 2 after a while they suddenly approved app2. we are trying hard to figure out what the issue is, we dont see any other apps with this. does anyone know what it can be? we have changed name, re designed, made sure text is not generic, added value for the users. explained we operate seperate even though we know each other. Also my name is in app1 apple id and bundle id, as well as in app2. if that could be an issue?

Hi. My friend and I are new to app developing. We made an app together and I made one alone on the side. But we are not joined. we each pay seperate taxes and not some scam design post of apps. Apple flagged both with spam design, so we assumed it was related. but not sure anymore. app1 is a travel related app operating globally. we have IAP but also destination inspiration and global food information, which is free in the app. app2 is about one single country and has a lot of information about travelling in that country and some IAP too. IAP in both apps are the same product, but unique in appstore. it only exists on websites apart from these two apps. both are made in adalo so even though the colours are different they are made in the same system. In app1 IAP is the main product, in app2 its not. we have tried so much to get app1 through but they keep rejecting with spam design. After a while they suddenly approved app2, after renaming it, changing colours and highlighting the information about the country is a demand. But we did the same to app1. It very frustrating not to know exactly whats wrong. we are trying hard to figure out what the issue is, we dont see any other apps with this. does anyone know what it can be? we have changed name, re designed, made sure text is not generic, added value for the users. explained we operate seperate even though we know each other. This is the message: Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Review Environment Submission ID: fa7d0e0a-661b-4101-afc4-b0d6cee7e648 Review date: September 05, 2025 Version reviewed: 1.0 Guideline 4.3(a) - Design - Spam We continue to notice your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality.

Hi I am a developer working on an enterprise app. I was recently rejected from the Apple Develop Enterprise Program. So I'm thinking of distributing Unlisted App as an alternative. The app I want to review is as follows Authentication App Requires installation of external security solution for login (Screen Protect, OTP) Sign in with an account managed by your organization Forward authentication to the integration app Groupware requires installation of an authenticator app login by forwarding authentication from the authenticator app View intranet information I want to know if the above type of app can pass through Unlisted App.

Hi, We’re reaching out to the community because we’re stuck in a situation that’s becoming critical for our launch timeline and could really use some advice. We submitted our app on August 11, 2025. Over the following days, we worked closely with App Review, made revisions, and provided every piece of information they requested. On August 19, 2025, we finally received this message: “Your submission’s review will require additional time as we take this new information into account. We do not require any further information at this time. Once we have thoroughly reviewed your submission, we will either contact you in App Store Connect to communicate any issues found, or your submission will be approved.” We followed up days later and got this response: “We apologize for the delay. Your submission is still in review but is requiring additional time. We will provide further status updates as soon as we are able.” It’s been 12+ days with no updates, and the app is still stuck in “Unresolved Issue” status. This delay has now pushed us past our launch deadline, and we’re unsure why the process is taking so long. We completely understand that expedited reviews aren’t always possible, but given the urgency and importance of this project, we’re doing everything we can to move forward. If anyone from App Review happens to see this, or if any developers have gone through something similar and can share advice, we’d really appreciate it. Thanks in advance!

Hello everyone, I’ve been struggling with App Store Review regarding my delivery app, and I’m hoping someone here can shed light on whether my app actually requires In-App Purchase (IAP) under Apple’s guidelines. Here’s my situation: My app connects riders with delivery jobs. We have two rider payment models: Commission Plan (10%) – Riders don’t pay upfront, but 10% is deducted per completed delivery. Fixed Subscription Plan – Riders pay a fixed monthly fee in advance, which allows them to keep 100% of their delivery earnings. The challenge: Apple Review has rejected my app multiple times, insisting that I must use IAP for these payments. I’ve written back and forth with them several times explaining that: The commission plan isn’t a digital feature, it’s simply a revenue share from physical delivery work. The fixed plan is more like a business service fee for using the platform, not for unlocking content or digital features. Despite this, the Review Team continues to state that my app “requires IAP.” My questions are: Based on Apple’s official guidelines, do apps like mine (delivery/logistics with commission/subscription for riders) really fall under IAP rules? Has anyone here had a similar issue with a marketplace or service-based app? If this does require IAP, what’s the reasoning — since the payments are tied to real-world services, not digital content? I’d appreciate advice, shared experiences, or even clarification from someone who has successfully passed review with a similar model. Thanks in advance!

Hi everyone, I currently have two apps stuck in TestFlight beta review for over 30 days without any progress: App ID: 6749024874 — Case ID: 102673603146 App ID: 6749025418 — Case ID: 102673604516 I contacted Apple Support, but they told me this situation is “normal.” From my experience, TestFlight reviews usually take a day or two, sometimes up to a week, but not this long. Has anyone else experienced such long delays with TestFlight beta reviews? Is there anything I should do (cancel and resubmit, escalate further, or just wait)? I would also like to request support from the App Review team to look into these case IDs and provide clarification. Thank you.

Most ASO tools I’ve found, like Appfigures, are effective but too expensive for my current app income. I’m exploring cheaper alternatives such as Astro—has anyone used it or compared it with tools like Appfigures or Appvector?

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. 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? Hopefully get help. Best regards!

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?

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.

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, 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!

When submitting an app for review, will any unreviewed auto-renewing subscriptions within the app be reviewed simultaneously? I own an app that has passed review and offers an auto-renewing subscription A within the app that has also passed review. To test a new service, I plan to create a new auto-renewing subscription B, which I do not intend to submit for review. After creating Subscription B, I plan to submit the app for review as part of an app update. In that case, is there a possibility that Subscription B will also be reviewed?