Hello, I have a question regarding Apple's policy on third-party SDK signatures. I have reviewed the official documentation here: https://developer.apple.com/support/third-party-SDK-requirements/ Our app is developed in the following environment: Minimum Target: iOS 15 Xcode: 26.2 Engine: Unreal Engine 4.27.2 We are integrating the Firebase SDK into our project. However, we are experiencing app crashes caused by an issue within the GoogleAdsOnDeviceConversion.xcframework included in the Firebase SDK (related to a memory optimization issue in UE4). According to an official response from the Firebase team, this crash can be resolved by wrapping the Firebase SDK in a dynamic XCFramework. We have confirmed that this solution does indeed fix the crash. The problem is that wrapping the Firebase SDK in a custom dynamic XCFramework removes all of the original Firebase SDK signatures. The documentation on third-party SDK signatures, which I referenced earlier, states that a signature is required for the Firebase SDK, and this requirement also applies when repackaging it. This leads me to the following questions: Question 1: When we wrap and repackage the Firebase SDK, is it mandatory for the resulting XCFramework to still include the original Google LLC signature? Question 2: To resolve the crash, we intend to use the Firebase SDK by wrapping it in our own dynamic XCFramework (e.g., FirebaseWrapper.xcframework). When we do this, the resulting XCFramework loses the Google LLC signature, and consequently, the final built IPA's signature list does not contain any Firebase-related signatures. Will this be a reason for rejection during App Store review? Question 3: If we wrap the Firebase SDK in a dynamic XCFramework and then sign it with our own developer certificate, would this be a reason for rejection during App Store review?

Hello everyone, I’m facing a persistent App Store rejection under Guideline 2.1(b) – App Completeness, related to In-App Purchases, and I’m unable to reproduce the issue on my end. Issue reported by Apple Review Apple Review team reports: “No action occurred when we attempted to buy the subscription.” Device: iPad Air 11-inch (M3) OS: iPadOS 26.4.1 What I have verified from my side I have thoroughly tested the subscription flow under multiple scenarios: Sandbox Testing Using sandbox test accounts Product loads correctly Purchase flow completes successfully Apple payment sheet appears properly TestFlight Testing Installed app via TestFlight Logged in with real Apple ID (Beta tester) Successfully completed subscription purchase Device Testing Tested on multiple iPhones Tested on iPad as well Purchase flow works correctly on all devices App Store Connect Configuration Paid Apps Agreement → Active Banking & Tax → Completed (no pending warnings) In-App Purchase status → “In Review” Product is correctly configured and attached to app What Apple is experiencing Based on their feedback and screenshots: Subscription screen loads correctly Product price is visible When tapping “Subscribe Now” → no action occurs No error message, no purchase sheet Is there a recommended workaround or reviewer instruction to avoid this deadlock? Any insights or real-world experience would be greatly appreciated. Thanks in advance.

Dear Developer, We are writing to notify you that the Ministry of Industry and Information Technology (MIIT) has identified your app as in violation of the Regulation on Personal Information in Mobile Apps. If your app is not compliant by April 20, 2026, MIIT will find your app to be illegal in China, and demand that Apple remove it from the China App Store. The App Review Guidelines require apps to comply with all legal requirements in any location where they are offered. Legal Apps must comply with all legal requirements in any location where you make them available (if you’re not sure, check with a lawyer). We know this stuff is complicated, but it is your responsibility to understand and make sure your app conforms with all local laws, not just the guidelines below. And of course, apps that solicit, promote, or encourage criminal or clearly reckless behavior will be rejected. We ask that you refer to the directions included in the document attached to this message. If you have any questions, we advise you to get in touch with MIIT within 24 hours of this notice by submitting your feedback via https://app.caict.ac.cn/. Thank you for your prompt attention to this matter. Best regards, App Review Message Attachments: Directions.docx

Hello Apple Developer commuinty! We have been developing a VPN client app with unique protocol for quite a while, and now it have come to publishing it in App Store/Google play. I know that publishing a VPN service requires organization(which i cant register because of my life situation), that why i have choosen to make a client. User is NOT necessarily required to use official hosting, theres an option of importing external key. App itself, doesnt contain any hardcoded server credentials and such, but it does have option to get free config from website by click. For some reason, my app review have not gone well. Apple have claimed my app have violated Guidelines 4.3(a) and 5.4. In all of my respect for App Review Team, but claim on Guideline 4.3(a) - Spam is completely ridiculous! App was completely written from the ground, not only including protocol, but the design itself. The "MONOGON" style, is unique application style which no other app on app store have seen(featuring dotted ASCII style, with blooms and contrast colors). In a million years, i would never guess what they have seen "identical to other apps on app store". Claim on Guideline 5.4 though, is a lot more reasonable, yet still not exactly correct. My app is mainly a client, not a service. The main function of it - bringing secure d1mension protocol to live on iOS and iPadOS platforms. The first setup, has both link to get official config(completely free without login, similar to AmneziaWG app), or to import own config. The code secures and encrypts packets such a way, that no external server could listen/decrypt it except for the original user destination, which makes it completely secure for the user. The main goal of DrochVPN app, is to bring users freedom in how they connect, to which server they connect. Any sort of help with publishing our app would be greatly appreciated, and we are ready to introduce changes, if they are required. App review identificator: 2f59adfb-ec49-4431-91c0-8e9b1984ad2e

Hi, I’m looking for clarification from folks familiar with CoreHID rather than App Review, as the guys there have not responded to my post (https://developer.apple.com/forums/thread/820676) We have a sandboxed macOS app that creates a virtual HID device (HIDVirtualDevice) as described in Creating virtual devices https://developer.apple.com/documentation/corehid/creatingvirtualdevices To work at all, the app requires the entitlement: com.apple.developer.hid.virtual.device With this entitlement present, macOS shows the system prompt requesting Accessibility permission App would like to control this computer using accessibility features. Grant access to this application in Security and Privacy preferences located in System Preferences. when HIDVirtualDevice(properties:) is called. There is no mention of Accessibility in the HIDVirtualDevice documentation, but the behavior is reproducible and seems unavoidable. My question is therefore: Is creating a virtual HID device from userspace via HIDVirtualDevice considered inherently incompatible with Mac App Store distribution? In other words: Is the Accessibility prompt an expected side‑effect of this API? And if so, does that mean using HIDVirtualDevice is only practical for direct (non–App Store) distribution unless the app is explicitly an accessibility tool? I’m not asking about review policy details—just whether, from a technical/system point of view, HIDVirtualDevice is actually intended to be usable by App Store apps. For context, there seem to be public, non‑accessibility uses of Apple’s virtual HID infrastructure, like this recent post: https://developer.apple.com/forums/thread/820708 and corresponding Github repo this project. I don't know if these intend to use the App Store, but they might end up in the same situation. Any insights from people who’ve worked with CoreHID would be greatly appreciated. Thanks, Magnus

Received email from Apple with title "notification of apple Developer Program License Agreement (“DPLA”) violation." 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. Same day i response that do not did any actions from this list or similar to them, describing every point. Next day i received response Thank you for your reply. As noted in the original notification, manipulating App Store chart rankings, user reviews, or search index is a violation of the Apple Developer Program License Agreement (DPLA) and may result in the loss of your Developer program membership. We suggest you conduct internal investigations to ensure you and any third-parties you may work with are in compliance with the DPLA and App Store Review Guidelines. We also encourage you to closely monitor your app activities. If you notice any unusual activity in the future, please follow these steps: Sign in to App Store Connect > Contact Us > Report a Concern > Report a Fraud Concern. We are unable to provide additional information at this time. Thank you for your efforts to make the App Store a safe and enjoyable experience for users and a great opportunity for all developers to be successful. I made response, that i checked everything, only one problem was in backend functionality working badly, but already fixed it (it was not about Apple license rules, it is just one of app functionalities returns error instead of answer. And it was fixed) Also i asked if current problem is solved and write emails if something else needs to be fixed. But no any responses was, and in 20 days i received email "Notice of Termination" Pursuant to Section 3.2(f) of the ADP Agreement, you agreed that you would not “commit any act intended to interfere with any of the Apple Software or Services, the intent of this Agreement, or Apple’s business practices including, but not limited to, taking actions that may hinder the performance or intended use of the App Store, Custom App Distribution, TestFlight, Xcode Cloud, Ad Hoc distribution, or the Program…” Apple has good reason to believe that you violated this Section due to documented indications of fraudulent conduct associated with your account. ... "AppStoreConnect -> Contact Us" page not working, because i cannot log in for it. Please help to resolve this problem: How to contact with apple in a fast way to describe that i did not do any actions that are not in compliance and find a way to fix and restore account and app. App used Auto-renewable subscriptions, so we have maximum 1 week to restore app before subscriptions automatically canceling At least, how to get payments for subscriptions that was already collected by app. Apple wrote "If applicable, no further payments will be made to you pursuant to Section 7.1 of the Paid Applications agreement (Schedules 2 and 3 to the ADP Agreement)." But i ready to prove and discuss that I am not at fault, and if there is fault in the third-party companies promoting my app - the promotion will be stoped

Hello, Our application has been stuck in the "In Review" status for 17 days now, and we are looking for guidance on whether this is a known technical stall or an extended policy audit. The Issue: The app moved from "Waiting for Review" to "In Review" on March 25th. Since then, there has been no change in status and no messages in the Resolution Center. App ID: 6753868146 Thanks

ID 6758008521, Dear App Review Team, I submitted my app review and it got rejected for inaccurate screenshot. I have revised the app screenshot and also resubmitted. But it has been 8 days and no response. We look forward to completing the review, thank you.

Hi, My app is waiting for review since Saturday at 5:42 PM, so is TestFlight. It has been rejected a couple of times, and errors were fixed with each update. Is this normal?

I am writing to share my frustration regarding the app review process for my application. My current submission has been stuck in "Waiting for Review" for nearly 7 weeks, starting from February 5th. Although I have attempted to cancel and resubmit periodically, there were significant gaps of 10 and 21 days between submissions where no action was taken. Currently, I am stuck again. The situation is critical for the following reasons: Critical Bug: The update includes a necessary fix for an In-App Purchase bug that is preventing users from accessing paid features. No Communication: I have sent four inquiries regarding this delay. I received only one generic response asking me to wait, and my subsequent follow-ups have been completely ignored. Expedited Review Request: My requests for an Expedited Review have also gone unanswered. Apple’s standard review time is typically 24-48 hours, but my experience is far from that. I am not asking for special treatment; I am asking for basic transparency regarding why my app has been stalled for nearly two months. Could anyone from the review team please look into this or provide an explanation? This prolonged silence is causing significant issues for my service and its users. Apple ID: 6752595582 First Submission Date: Feb 5th

Hello Apple Developer Community and App Review Team, I'm writing to seek guidance regarding my app Lookify: AI Virtual Try-On (App ID: 6757718224), which has been caught in an ongoing review cycle since February 15, 2026 — nearly two months ago. Submission History: Date Version Status Feb 15 iOS 1.1.0 Removed Feb 19 iOS 1.1.0 Removed Feb 21 iOS 1.1.0 Removed Apr 3 (2:21 AM) iOS 1.1.0 Removed Apr 3 (1:17 PM) iOS 1.1.0 Removed Apr 6 (current) iOS 1.1.0 Waiting for Review Each submission was either self-removed after extended waiting periods with no reviewer feedback, or removed to address potential issues — only to re-enter the queue with the same outcome. The current submission has now been in "Waiting for Review" status since April 6 with no activity, no messages, and no indication of progress. What I've done to comply: Updated the Privacy Policy to be fully GDPR and KVKK compliant Provided clear demo account credentials and usage instructions for the AI try-on feature Ensured all metadata, screenshots, and descriptions accurately reflect the app's functionality Reviewed Apple's App Review Guidelines thoroughly before each resubmission I understand that AI-powered apps — especially those involving visual try-on technology — may require closer scrutiny, and I fully respect that process. I'm not asking to bypass any review step. I simply ask for transparency: if there is an issue with the app, a rejection with specific feedback would allow me to address it immediately. This app represents months of development work. As a small independent developer, prolonged uncertainty without communication makes it very difficult to plan or improve. My request: Could anyone from the App Review team or community provide insight into: Whether there is an active flag or concern on this submission What the expected timeline might be for accounts with this submission history Whether an Expedited Review would be appropriate given this timeline I have also submitted a contact request through the official App Review contact form. I am fully committed to making any necessary changes — I just need to know what they are. Thank you sincerely for your time and assistance. Mustafa Bilgiç Developer, PlayTools

Apple review usually takes a couple hours or even 2 days or less to review my submissions but it’s taking them 4 days to review it I submitted on a Wednesday. should I re-submit?

My app requires Google or Apple login. The App Store requires an active email for review. How can the App review team access my email if it required 2FA? I don't understand how I can get an app reviewed it they need me to provide a code after they login? It seems ridiculous that I need to supply them with a test email, why can't they test with a dummy email? Is it just not possible to get an app reviewed if the app requires Apple or Google logins? Should I temporarily add the option for any email to setup an account and just make a dummy email and then after review asap remove the email login from the app? that seems like a lot of unnecessary programming just because they the need me to provide an email address and login.

I’m trying to find out whether anyone has seen this kind of App Store Connect issue remain unresolved for this long. This is for a first auto-renewable subscription. Timeline: Original support case opened: Feb 27, 2026 Support initially repeated the normal guidance that the first subscription must be submitted with the app version I explained that the issue was not the process itself, but a stuck review state On Mar 25, 2026, I was told the case had been escalated to the appropriate internal team Since then, I have sent follow-up emails asking for status / owner / ETA As of Apr 12, 2026 (KST), there has still been no meaningful update Current state in App Store Connect: App version 1.0.10 is still “Prepare for Submission” Previous 1.0.10 submissions show as “Deleted” There is no active app review submission for 1.0.10 The subscription previously showed “Waiting for Review” Now the subscription itself shows “In Review” But its localization still shows “Waiting for Review” So the state looks inconsistent: no active app review submission app version still draft subscription partially moved into review anyway At this point I’m not asking about the normal first-subscription submission flow. I already understand that. What I’m trying to understand is: Has anyone seen a case like this stay stuck for 6+ weeks? Has anyone had Apple say it was escalated internally and then go silent for weeks? Did Apple eventually fix it manually? Is this something that can remain stuck indefinitely unless the internal team intervenes? Any comparable experience would be helpful.

Hello everyone, I am currently developing a smart camera app for iOS that recommends optimal zoom and exposure values on-device using a custom Core ML model. I am still waiting for an official response from Apple Support, but I wanted to ask the community if anyone has experience with a similar workflow regarding App Review and the DPLA. Here is my training methodology: I gathered my own proprietary dataset of original landscape photos. I generated multiple variants of these photos with different zoom and exposure settings offline on my Mac. I used the CalculateImageAestheticsScoresRequest (Vision framework) via a local macOS command-line tool to evaluate and score each variant. Based on those scores, I labeled the "best" zoom and exposure parameters for each original photo. I used this labeled dataset to train my own independent neural network using PyTorch, and then converted it to a Core ML model to ship inside my app. Since the app uses my own custom model on-device and does not send any user data to a server, the privacy aspect is clear. However, I am curious if using the output of Apple's Vision API strictly offline to label my own dataset could be interpreted as "reverse engineering" or a violation of the Developer Program License Agreement (DPLA). Has anyone successfully shipped an app using a similar knowledge distillation or automated dataset labeling approach with Apple's APIs? Did you face any pushback during App Review? Any insights or shared experiences would be greatly appreciated!

Hola, el día 20 de enero de 2021 a las 7:26 p. m. hice la compra del programa para desarrolladores y Apple quedo de enviarme un correo cuando todo este listo, ya han pasado las 42 horas y no tengo respuestas, ya le escribí a soporte espero me ayuden. De igual manera quisiera saber cuanto tiempo les demoro a ustedes todo el proceso de compra y verificación, espero me ayuden. Gracias

Hi everyone, I’m looking for advice on a repeated App Store rejection under Guideline 2.5.1. Background: We initially explored using Family Controls for a planned feature. That feature has now been fully removed from the app. We no longer provide any Screen Time related functionality. What we already cleaned up: Removed all FamilyControls / ManagedSettings / DeviceActivity code usage. Removed commented-out code and all related references from the project. Removed related capabilities and entitlements from targets. Removed related frameworks/dependencies. Performed a clean rebuild and submitted a new archive. However, App Review still says the app includes ScreenTime API in an unapproved manner and suggests removing those APIs. Questions: What are the most common hidden places where Screen Time / Family Controls traces remain? Has anyone seen this triggered by transitive dependencies or stale build artifacts? What evidence/details should I provide in App Review Notes to help the reviewer verify cleanup? Is there a recommended way to ask App Review to share the specific symbol/framework/target they detected? Any practical checklist or experience would be greatly appreciated. Thank you.

Hello, I submitted my app for review and it was rejected under Guideline 4.2. I believe the rejection was a misunderstanding of my app's functionality, so I filed an appeal through the Resolution Center explaining why I believe my app meets the minimum functionality requirements. It's been passed almost two weeks since I filed the appeal but I've received no response or update on the status. My app is directly tied to an event launching next week, and without a resolution, I will miss the launch window entirely. I'd greatly appreciate any visibility into where my appeal stands, or any guidance on what steps I can take to move this forward. Thank you for your time.

I’ve had an issue with all of my apps. Where I push my build to TestFlight and then the image pops up. I’ve troubleshooted EVERYTHING. My account has no issues on it, no payment or compliance issues. I’ve looked to reddit for advice, one user says they need there app to get approved by apple, i got a couple apps to have there update approve, still the bug persist. Whether the app is on the App Store or a work in progress nothing works.

I submitted an app build and filled out the expedited review form, they quickly replied: “The issues we've identified below are eligible to be resolved on your next update. If this submission includes bug fixes and you'd like to have it approved at this time, reply to this message and let us know. You do not need to resubmit your app for us to proceed.” I replied with “Yes, please accept the current version now as it contains bug fixes, will resolve that issue later lalala” I replied again 1 day after the letter. And nothing. 2 days total have passed. So the replies do not go to the Expedited Review queue? What should I do? Reply again? Or resubmit the build with a comment “Important bug fixes, please accept immediately”? Or maybe call them, will a call help? Thank you so much!