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

If I upload my app with included plugins with no dsyms for the bundles I get a warning message that there are no dysms. If I select DWARF + dsyms, I get a warning saying it can't find them, even though they are there in the resource file with the correct UUID For example: The archive did not include a dSYM for the BIS.bundle with the UUIDs [6481C68F-CEE4-33B5-8631-E03251E48FF2, C7482559-F72A-3510-A5B9-00C24F376CD9]. Ensure that the archive's dSYM folder includes a DWARF file for BIS.bundle with the expected UUIDs. When you choose Get Info on the dsym it shows the UUIDs that the AppStore allegedly can't find. Any ideas?

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

Hello, We have an app that appears to be stuck in waiting for review status. Another app we submitted later already got reviewed, leading us to believe this app is somehow stuck or got lost in the process. App ID is 6751250460.

Hi, For an app that is device dependent (communication through bluetooth and network) for proprietary device in specialized applications, is allowed the use of license key on app store without in app purchases? The app is useless for users without the hardware Thanks

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.

Submissions stuck for ovwe 2 hours: 812e835c-6215-44ef-b052-030f8a4ef1cd 1bae8357-7b2e-450d-bde8-87e48a02c1a1 680d3c51-3316-43b3-a50d-ec0b444f183a Is there a service issue? Normal processing time exceeded.

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.

Hi all, My Unity app was rejected for running in portrait mode on an iPad Air (5th gen) with iPadOS 18.6. My Unity Player settings are configured for landscape-only (Auto Rotation with Landscape Left and Landscape Right enabled). On my older iPad (5th gen) with iPadOS 16.7.11, the app works correctly and stays in landscape. Has anyone seen similar orientation issues with Unity builds on M1/M2 iPads running iPadOS 18? I suspect this is a bug with the new OS on specific hardware. Any insights are appreciated. Thanks.

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!

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.

App stuck in waiting for review for 12 days App id: 6748567505 I don't know what's with this app, but every version seems to get stuck for 10+ days waiting for review.

hi, I am a product manager from inspire brands and i am trying to get in touch with someone on the app review team and trying to find some time to connect during their office hours.

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