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?

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.

The app I submitted has been waiting for review. APP Name:小马AI美术 BundleID:com.hangzhouyq.art.xmai

Our app was recently rejected during review under the Guideline 2.5.1 - Performance - Software Requirements, with the reason that we’re using a non-public API: "pacga" However, based on our investigation: We are not explicitly calling this API in our code or in any linked frameworks. We ran the suggested checks (strings, otool) on the app binary and included frameworks, and found no private API usage. From what we understand, "pacga" is not an API at all, but an ARM64e instruction (Pointer Authentication Code Generate Address) automatically generated by the compiler for devices with ARM64e support (A12 and newer). This is part of Apple’s Pointer Authentication (PAC) security mechanism introduced in iOS 12. Sharing a few references: https://developer.apple.com/documentation/security/preparing-your-app-to-work-with-pointer-authentication https://www.usenix.org/system/files/usenixsecurity23-cai-zechao.pdf https://clang.llvm.org/docs/PointerAuthentication.html#id9 Given this, we suspect the rejection might be a false positive triggered by the presence of this instruction in the compiled binary rather than actual private API usage. Has anyone else run into a similar rejection recently? If so, how did you resolve it with App Review? Thanks in advance.

Dear Apple Review Team, The app I submitted has been pending for several days and hasn't entered the review process yet. Could you please help check if there is any issue causing this delay? APP Name:小马AI美术 BundleID:com.hangzhouyq.art.xmai

I submitted my app for review on August 5, 2025, but as of today, August 25, the status is still “Waiting for Review.” I have already contacted support twice regarding this matter (Case Numbers: 102664827493 and 102670984940), but the only replies I received were that the app is under expedited review and that the review is delayed due to high submission volume. Unfortunately, the status has not changed at all, and I am still left waiting helplessly. I am truly desperate at this point, as the long delay is causing significant difficulties. I kindly and sincerely ask if there is anything more that can be done to help me with this matter. Any support you can provide would mean so much to me.

Guideline 3.1.1 - Business - Payments - In-App Purchase, as my app currently allows users to purchase digital content (courses) using an external payment system. I am working to comply with Apple’s requirements by integrating In-App Purchase for all digital content within the app. My app contains approximately 100,000 individual courses, and I am seeking guidance on how to effectively implement In-App Purchase for such a large number of items. Creating 100,000 separate In-App Purchase products in App Store Connect seems impractical due to the scale and potential limitations. I would like to explore feasible solutions, such as: Using a subscription model to provide access to all courses. Creating category-based bundles (e.g., Programming, Design) to group courses. Implementing a dynamic purchase system where users can select specific courses after a single In-App Purchase transaction, managed server-side. Could you please advise on the best approach to manage In-App Purchase for 100,000 individual courses? I am happy to provide additional details about my app’s functionality or work with your team to ensure compliance. Please let me know if a consultation or further documentation is needed to proceed. Looking forward to your guidance. Best regards, Shuvajit Maitra

Recently we've faced an issue when submitting the new build for reviewal. It was rejected with following reasoning: Your app's binary includes the following call-to-action and/or URL that directs users to external mechanisms for purchases or subscriptions to be used in the app. Complain was related to phrase To discover our products please visit our website We're going to to rephrase it as Our website can help you to learn more about our products Will it solve the issue? According to ChatGPT following phrasing should not be considered a call-to-action. What's your opinions?

Description: Hello, I recently received the following email from Apple: We're writing to inform you that your company isn't in compliance with the Apple Developer Program License Agreement (DPLA). Section 11.2 (Termination) states: (g) if You engage, or encourage others to engage, in any misleading, fraudulent, improper, unlawful or dishonest act relating to this Agreement, including, but not limited to, misrepresenting the nature of Your Application (e.g., hiding or trying to hide functionality from Apple’s review, falsifying consumer reviews for Your Application, engaging in payment fraud, etc.). Be aware that manipulating App Store chart rankings, user reviews or search index may result in the loss of your developer program membership. Please address this issue promptly. I’m trying to understand how other developers handled this warning. Could you please share your experience: Did you identify what triggered the warning? Did you need to remove or change anything in your apps? Did Apple require a formal response or evidence? How did you confirm that the issue was resolved? Any guidance would be greatly appreciated.

Hello All, It’s been almost a month, and I’m trying to submit my app’s first version, but I keep getting rejections with the reason “App Completeness – No Connectivity.” Here’s the timeline: • Initially, the app was rejected for app completeness. • I scheduled a review appointment, and during that session, the reviewer confirmed the app was working fine. • The reviewer only asked for permission policy changes, which I implemented and resubmitted. • After resubmission, the app was rejected again with the same “App Completeness – No Connectivity” issue. The reviewer in the first session mentioned it might have been a connectivity issue on the device during testing. So, I scheduled another review appointment, but that appointment request was declined. To date, I have made 13 submissions, and 10 were rejected for the same reason. I have also raised multiple appeals, but haven’t received any response. The app works perfectly on multiple devices and iOS versions, and TestFlight testing is successful. Has anyone faced this issue before? How can I resolve this and prevent repeated rejections? Any suggestions would be appreciated. Thank you.

Hello everyone, I am building a React Native (Expo) application where the customer requested a simple “Add to Wallet” button. However, instead of handling Wallet provisioning or passes, the requirement is just to open the Apple Wallet app when the user taps this button. My questions are: Is it allowed by App Store Review Guidelines to have a button that simply launches the Wallet app, without actually adding a pass (.pkpass) or card? After navigation to the Apple app user just can manually add the card to the Apple Wallet. If so, should I avoid using the official “Add to Apple Wallet” badge, since nothing is being added? Would a custom label like “Open Wallet” be more appropriate to comply with Apple’s branding rules? Could my app risk App Store rejection if I implement this simplified behavior? I want to make sure I follow the guidelines and avoid misleading users or violating branding rules. Any clarification or experiences from others who have submitted apps with similar functionality would be greatly appreciated. Thank you!

Hi guys, Is there any good up-to-date tutorial about publishing a Python based app on Apple Store? Now, I have developed a standalone Python app from PyCharm, and it's using Pyside6 for UI and some major Python libraries. It's a productivity app with a little A.I. features. I used PyInstaller to prepare the app. Currently, I am stuck at the stage of codesign and Apple Review process, because I am manually doing codesign and building the package from command-line. Without using Xcode, things can get messy or miss easily. It would be nice to follow a up-to-date tutorial about how to complete the codesign and Apple Review process for a Python based app. For example, what to do, how to do, what to be careful during the Apple Review process, etc. Thanks!