Hello, I am planning to develop an iOS app that performs on-device inference using machine learning (ML) models. To improve accuracy and user experience, after the app is installed, I would like to download and update .mlmodel files from a separate cloud server and use them for inference within the app. The .mlmodel files will be provided by the cloud server in a compiled format, compressed as zip files. The app will download the zip file, extract it, and use the model. No executable code, scripts, or dynamic libraries will be downloaded—only model data files will be used. All code is fully contained within the app bundle, and the downloaded model files are strictly used as data and are never executed as code. I have previously consulted with DTS (Developer Technical Support), who confirmed that, to their knowledge, this approach does not violate the guidelines and that there are existing apps that rely on this functionality. However, for official assurance and to avoid any potential issues during app review, I would like to request confirmation from the App Review team. Specifically: Is it permitted under App Store guidelines to download or update compiled .mlmodel machine learning model files (compressed as zip files) from a remote cloud server after app installation, as long as no executable code is downloaded or executed? Thank you.

Hi everyone, Our app (Apple IDs: 6744840952 and 6746964086) has been under review for three weeks now, and during this time we’ve made several attempts to follow up: We submitted an expedited review request We used the Contact Us form to inquire about the status We tried reaching out by phone We spoke with Apple representatives during a Meet with Apple Experts event Unfortunately, none of these actions have resulted in any progress. The responses we received have all been variations of “please wait patiently,” and we haven’t been proactively contacted through App Store Connect either. We are feeling deeply discouraged, and the emails from our users have shifted from initial understanding to increasing frustration and complaints. We fully understand that the review process can vary in complexity, but the app has now been in review for 20 days. We would deeply appreciate any assistance or suggestions that might help move the process forward. Original feedback link

Should I have gotten an email for my submission of an appeal for a rejected app? It's pretty clear from the rejection reason that there was a misunderstanding about the purpose of the app, so I filled out the appeal form. But I never got a confirmation email. It's been roughly 28 hours since I sent the appeal. I DID get a confirmation page for the appeal... Do I just keep waiting? Thanks!

My application (App ID: 6746629090) has been in “Waiting for Review” for nine (9) days without any status change. To investigate, I opened a support case via App Store Connect 4 days ago, but I have not yet received a response or update. Because the delay is now impacting our release timeline and customer commitments, I respectfully request: A status update on the current review of App ID 6746629090. Confirmation that there are no outstanding compliance items or additional information required from my side. If possible, expedited processing or guidance on next steps to resolve the hold-up. Key details • App ID: 6746629090 • Current version / build: 1.2.1(22) • Date submitted: Jul 6, 2025 • Support Case #: 102641999315

Our app has been in the "In Review" status for over 48 hours. During this time, we have: Submitted an expedited review request; Contacted the App Review team through the “Contact Us” form with an explanation. However, the review status has remained unchanged, and we have not received any further feedback or response. We understand that review times may vary due to different circumstances, but as we are approaching our planned release schedule, we’re hoping to receive some assistance or clarification on whether any additional action is required on our end.

Hi, My app has been approved a week ago, but Digital Services Act is still under review. How long it usually takes to do this review? I assume that this is blocking my app release as I'm trying to release my first app in Finland.

Hello App Review Team, We submitted our long-awaited app for review on July 8 and are starting to feel a bit anxious, as we haven’t heard back in several days despite submitting all requested changes and an updated build. To be fully transparent, the review process so far has been somewhat confusing, and we’d really appreciate your guidance: First Rejection: We were told the demo login credentials were missing and that our developer account wasn’t linked to our company domain. However, the demo credentials were included in the Notes section, and the email associated with our developer account had already been updated to reflect our company domain before submission. Second Rejection: The reviewer appeared to misunderstand the purpose of a simple in-app game, despite the fact that the description was clearly shown in the screenshot they shared. We’ve tested this feature extensively with real users, and no one has encountered similar confusion. Third Rejection: The app reportedly failed to load on a specific device. We genuinely appreciated this feedback and promptly addressed the issue in a new build. Since then, we’ve been waiting several days for the next step, but it seems the review may be stalled. We understand how busy the App Review Team is and truly respect the high standards of the App Store. That’s exactly why we want to be sure we’re doing everything right. We’re fully committed to delivering a high-quality experience that aligns with Apple’s guidelines and will genuinely benefit users. If there’s anything else we can provide to help move things forward, we’d be more than happy to do so. Thank you so much for your time and support.

Hello Apple Developer Support & Community, I’m reaching out regarding the unexpected termination of my Apple Developer Program account, associated with App ID: 6744330283. Recently, my app was flagged under Guideline 4.3 - Spam, and I was asked to make necessary changes. I followed all guidance provided by Apple, including a phone call with an App Review team member, who clarified the steps I should take. I did not submit any further update after that call. However, before I had the chance to upload the new, compliant version of my app, my entire developer account was terminated without a clear explanation or additional warning. I believe this was a misunderstanding, as I was actively working on compliance and fully committed to resolving the issue. My app is not spam I only followed Apple’s instructions I never uploaded a new version after my call with App Review No specific violation or example of “spam” was shown to me I’ve submitted an official appeal via the App Review Board, but I’m hoping someone here can also assist or escalate this matter. My developer account and years of effort are at risk over what seems to be a miscommunication. Thank you for any guidance or assistance you can provide.

My app published 6 hours ago this is first version and IAP is still in review. My app is hard paywall app so people cannot continue in app and this is all happening during initial boost. I contacted with apple but they say they send message to review time and hours passed nothing changed. People downloading the app and I'm watching it without able to do anything :( Are there anyone experienced same thing ? Do you have any advice ?

Hi all, I submitted a healthcare-related iOS app on June 19 that integrates with a health monitoring device. It had a few prior rejections due to compliance concerns, which we addressed. Apple Developer Support confirmed the review is still in progress and that it requires additional time. I'm wondering if others have experienced similarly extended review timelines for healthcare or medical device-integrated apps, and how long it took for resolution. Would appreciate any advice or shared experiences on this. Thanks!

Hello, I’ve received feedback from the App Review team for my app, indicating that the auto-renewing subscription violates guideline 3.1.2 due to inappropriate use of the service. They noted that such subscriptions should provide dynamic, ongoing value over an extended period and requested a revision or removal. My app offers cloud backup for user app data and cross-device sync via Apple Sign-In and Google Sign-In, with unlimited uploads and downloads. Additionally, we limit free users and provide premium features like more stylish cosmetics to paid users and more upcoming. Despite my previous response, the feedback remains unchanged. I’d like to ask: Does a simple cloud backup for user app data suffice to meet the ongoing value requirement of 3.1.2? I also suspect that providing clear instructions for reviewers to test this cloud feature—such as screenshots and a step-by-step guide—might help clarify its value. I zeroed in on the cloud aspect based on reading that it could address this issue, but I’m unsure if mentioning the user limits and premium features is relevant here. Any guidance or suggestions would be greatly appreciated. Thank you! Jack

I have an issue with my app trying to get it live and i have a deadline. I have sent multiple emails and service tickets to Apple with zero response over the last 2 weeks. Is there anyway I can get some assistance. i have made the payment for the app developer $99 13 days ago and thereafter no info has been given, i have a serious deadline for the app and still need to add on new events and listings. however i have sent multiple emails, commented on multiple forums, doen multiple support cases, but no response. I need to know if this will be completed soon and if there is anything else i need to do. Regards

Hello App Review Team, Our app has now been in “In Review” for 7 days. Could you please advise on the expected timeline for completion or let us know if any further details are needed to move forward? Thank you for your assistance.

Hello everyone, We are building an iOS app using React Native that connects to a custom Bluetooth Low Energy (BLE) accessory. The accessory continuously sends small chunks of audio data to the app through BLE (basically every time the user speaks), which are then streamed in real time to our server via WebSocket for transcription and processing. We need to know if the following behavior is allowed by iOS runtime and App Store review policies: Can the app open a WebSocket connection in the background (not permanently, just briefly, several times a day) triggered by BLE activity from a registered accessory? Is there a limit to this? Clarifications: The app is not expected to remain permanently awake. Only during accessory-triggered events. WebSocket is required due to the real-time nature of streaming STT and delivering quick responses (via notifications). If allowed, are there any specific Info.plist declarations or entitlements we must include? Thanks in advance! Fran

Hi, Our recent security scans, performed by Data Theorem, have flagged a potential App Store blocker related to the use of a private iOS class, NSBlock. We are concerned that this identified warning may lead to our apps being rejected during the next App Store submission. Issue Summary: We integrate a library, this SDK is developed using Kotlin Multiplatform, and during compilation, Kotlin automatically generates Objective-C/Swift interoperability code. As a result of this code generation, the compiled framework includes a reference to a private Apple class, NSBlock. It’s important to note that: No methods or functionality from NSBlock are being invoked or used. This reference is auto-generated by Kotlin’s ObjCExport.mm module. For additional context, you may refer to a related discussion on this issue: https://github.com/ricohapi/theta-client/issues/98 https://github.com/JetBrains/kotlin-native/issues/1642 https://github.com/JetBrains/kotlin-native/pull/1652/files We would like to confirm whether the presence of this unused reference to NSBlock will result in the rejection of our application during App Store review. Thankyou

Hi everyone, We just received another App Store rejection under Guideline 3.1.3 - Business - Payments - Other Purchase Methods, stating that we are using in-app purchases to sell physical goods — specifically, a physical QR code sent to the user. However, in our latest build, this issue was already addressed: All physical QR code purchases are now handled entirely through Stripe Checkout, outside of the app. No consumable IAPs are used for physical goods. The purchase flow is completely optional - users can tap “Continue” to skip it and still use the app without ever engaging with Stripe or purchasing anything physical. We’re a small team trying to launch and are stuck in a loop where it seems like the rejection feedback might not reflect the latest build with not clear feedback from Apple. Has anyone experienced something similar? Would really appreciate any guidance or insight — or if anyone from Apple is here, we’re happy to jump on a call to clarify. Thanks in advance!

Hello Apple Team, We're reaching out as part of a wider group of developers and businesses who have seen repeated App Store rejections under Guideline 5.0 - Legal, specifically related to U.S. sanctions on Syria. However, as of July 1, 2025, the U.S. Department of the Treasury (OFAC) has officially lifted those sanctions for commercial activities. This is clearly stated in the latest OFAC FAQ. Also visiting the link that we get from apple reviewers https://www.treasury.gov/resource-center/sanctions/Programs/pages/syria.aspx is not any more there and dose not include Syria at all. Despite this, rejections continue for those apps :( . Question: Has the App Review system been updated to reflect the July 1 OFAC decision? If not, is there a timeline for when Apple will begin processing these changes in the review flow? Our community is trying hard to work and build apps for middle east zones and Syria is part, this rejections brin heavy burdens on our community and makes unable to bring great apps for those markets. Thank you for your support.

Hello, i am having issues getting my iOS app through review. The problem seems to be that the reviewer is never able to purchase my IAP. The app has a non-consumable IAP that unlocks premium game features. however, I have not been able to able to reproduce. The IAP works for me in Xcode testing, as well as Sandbox (TestFlight) I had heard initially the problem was that I submitted the IAP for review alone, instead of having it auto submit with the app itself. but in my latest submission, I actually deleted and recreated the IAP, and allowed it to be auto submitted along with the app itself. again, all local and sandbox testing is successful, but the app reviewer sees an carrot stating that the product could not Be loaded from the App Store. i built the app using Capacitor, and am using revenue cat. does anyone have any ideas where I am going wrong? Thank you

Hi everyone, We’re building a hybrid mobile app using Capacitor and Vue.js, and we’re integrating web components hosted on a CDN. These components are developed and maintained by another internal team (e.g., BlueCross) and are shared across multiple platforms. We want to ensure this architecture complies with Apple’s App Store Review Guidelines. Here’s how we’re using the CDN: The CDN serves static web components (HTML/CSS/JS) used in the app UI All content is delivered over HTTPS No executable code is downloaded that alters app behavior post-install The app remains functional even if the CDN is temporarily unavailable The CDN content is versioned and controlled internally We’ve reviewed sections 2.5.1 and 2.5.2 of the App Store Review Guidelines, but would appreciate clarification or feedback from Apple or other developers who’ve submitted similar apps. Is this approach acceptable for App Store submission? Are there any additional precautions we should take? I submitted a build to App review 8.4.1 Blueconnect NC. Thanks in advance!

Hello Apple Developer Community, We’re running into a challenge with App Review related to Guideline 5.1.1 (Data Collection and Storage), and are hoping to get insights from others who may have encountered something similar. Our app is built entirely around account-specific functionality. Each user is issued a unique QR code tied to their account, which enables and disables core functionality. This QR code is not generic - it’s unique to the user and is securely stored in our Firebase backend to support cross-device use and persistent access. App Review has flagged that requiring login violates Guideline 5.1.1, despite the fact that we have already moved the login step to occur after the user completes an in-app purchase, as per their previous guidance. Login is not used to gate purchasing, but it is critical for generating and linking the unique QR code to the user’s account. Beyond the QR code, our product roadmap includes multiple account-dependent features like usage tracking, goal setting, emergency unlocks, and cross-device sync. None of this is technically possible without a persistent user account. We’re struggling to understand how to reconcile this rejection with the way our app is fundamentally architected. Account-bound functionality seems essential for delivering a secure and reliable user experience. Is anyone else facing similar confusion with this guideline? Thank you for your time and assistance.