In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Here are some tips from App Review for a smooth review experience. We’ve split them into two categories: Before You Submit and After You Submit. We’ve also made an easy-to-follow Submission Guide you can save and reference at any point on your App Store journey. Before You Submit Tips Enable a complete review. Make sure you’ve provided demo accounts or implemented an account demonstration mode before you submit. We’ll need to review the entire app experience, both with and without an account. Provide up-to-date demo account login credentials in the App Review Information section on the app version page in App Store Connect. If your app has multiple account types (such as admin and general users), use the Notes field to provide additional demo account credentials for each account type. If your app requires an authentication code in addition to the login credentials, provide the code in advance in the Notes field. Otherwise, a call may be required to complete the review. Apps that handle sensitive user information, or operate in highly regulated industries, can implement demonstration modes that exhibit full features and functionality while using demonstration data. Use the Notes field in App Store Connect to provide information to App Review. The App Review Information section of App Store Connect includes a Notes field. Provide any information that could be relevant to your submission’s review: Submitting a new app? Tell us about your app's concept, business model, and if your app is designed to only operate in certain locations. Submitting an update? Tell us about what’s changed and where to locate significant new content or features. Connecting to hardware? Attach a video, not a screen recording, that shows both the hardware and the app running on a physical Apple device as they pair and interact. Test your app on physical devices before submitting for review. Use TestFlight to distribute your app for beta testing. App Review evaluates apps the way your users will use them: installed on real devices and connected to networks with real-world conditions. Make sure your pre-submission testing includes running the app on each device platform where it could be used. Users expect the app to function on all the devices where it’s available. TestFlight will help you do quality assurance and beta testing on real devices. Share your beta app with internal testers on your Apple Developer Program account or to external users via an email invite or public link. Configure In-App Purchases for review in the sandbox environment. App Review assesses In-App Purchases in the same sandbox environment Apple provides for testing them. The sandbox lets us use real product data and server-to-server transactions, without incurring any financial charges. Take these steps to prepare your In-App Purchases for review: Accept the Paid Applications Agreement in App Store Connect. Submit the In-App Purchases in App Store Connect that you’d like reviewed. Follow the steps in TN3186: Troubleshooting In-App Purchases availability in the sandbox if your app fails to display your In-App Purchases. Note: In-App Purchases don’t need prior approval from App Review to function in review. Join a Meet with Apple event if you need assistance before you submit for review. Request an App Review appointment through Meet with Apple to chat with an App Review expert about how to prepare for review, ask questions about specific guidelines, and discuss other topics related to the review process. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays. After You Submit Tips Contact App Review if you need assistance with an ongoing submission. If your submission doesn’t pass review and you have questions, contact App Review directly by clicking Reply to App Review in App Store Connect. You’ll receive a reply from a review specialist who’s familiar with your app. You can also use the Reply to App Review message window to request a call with an Apple representative. Include your preferred time and language for the call and we’ll do our best to accommodate your requests. Use the Bug Fix Submissions process to quickly deliver bug fixes and resolve other issues on the next submission. If an update includes bug fixes and is rejected, you will be given the option to resolve the issues on your next submission, as long as there are no legal or safety concerns. App Review will let you know if your submission is eligible by including this note at the top of the rejection message: Bug Fix Submissions The issues we've identified below are eligible to be resolved on your next update. To accept this offer, simply reply to the rejection message in App Store Connect and let App Review know you’ll resolve the issues on the next submission. Share ideas with Apple about how to improve or clarify the App Review Guidelines by submitting guideline feedback. Just as the App Store is always changing and improving to keep up with the needs of customers, the App Review Guidelines may be revised to provide new and updated guidance. If you have ideas for improving or clarifying our requirements you can suggest guideline changes. If your submission was rejected but you believe it follows the App Review Guidelines, consider submitting an appeal to the App Review Board. If your submission didn’t pass review but you have reason to believe it follows the App Review Guidelines, you can submit an appeal to the App Review Board. You can also file an appeal if you think we misunderstood your app or the review was unfair. The App Review Board will contact you as soon as they complete their investigation.

Apple platforms make it easy to distribute your app to a variety of compatible devices, so it’s important to maximize your app experience on each platform you support. Here are some tips from App Review to help you understand how device compatibility impacts your app’s distribution — and how to make sure your apps shine on every platform they’re on. Understand device compatibility There are many ways an app built for one Apple device can run on other Apple devices: Apps designed for iPhone can run on iPad devices in compatibility mode if there are no dependencies on iPhone device capabilities. Compatible iPhone and iPad apps can run unmodified on Macs with Apple Silicon. Compatible iPhone and iPad apps can run unmodified on Apple Vision Pro. Xcode provides options to configure settings for apps on multiple platforms. You can specify which platforms your app’s target supports in the Supported Destination field. However, it’s important to note: People may still be able to run your app on a device even if you remove it or don't include it as a Supported Destination in Xcode. For example, as long as an app designed for iPhone doesn’t depend on a capability that’s only available on iPhone, it can be downloaded from the App Store onto iPad. Adding or removing iPad as a Supported Destination in Xcode won’t change that app’s availability on iPad. To view examples of cases where it's appropriate to restrict availability, see Restrict device distribution below. Follow compatibility best practices 1. Plan and test for compatibility modes so your app works on every device where it can be downloaded. Do: Use Xcode simulators to verify basic functionality across different device types. Leverage TestFlight with external testers who have access to a wide range of Apple devices. Don't: Don’t submit for review without testing your app’s behavior in compatibility modes. Don’t assume removing a supported destination in Xcode prevents distribution to that device type. 2. Build adaptive interfaces that work across device variations. Do: Build interfaces that respond to different screen sizes and orientations. Adapt features based on available hardware, providing alternatives for a consistent experience. Don't: Don’t design rigid interfaces that assume only one type of device or input method. Don’t let your app crash or become unusable when optional hardware is unavailable. Restrict device distribution Wherever possible, it’s best to make your app available on multiple platforms to increase its reach and provide people with a consistent experience across devices. But there are cases where it does makes sense to restrict an app’s availability. For example: iPhone apps that rely on iPhone-specific hardware won’t function as expected on iPad. Use the UIRequiredDeviceCapabilities key in the information property list file to specify hardware dependencies. Note: Apps should only use the UIRequiredDeviceCapabilities key for genuine hardware dependencies, not to indicate distribution preferences. Navigation- or camera-based apps are not well suited for visionOS. Learn more about managing availability of iPhone and iPad apps on Apple Vision Pro. Apps that rely heavily on touch inputs that can’t be replicated on a keyboard are not well suited for macOS. Learn more about restricting distribution to Apple Silicon devices. Learn more about how to configure multiplatform apps in Xcode. Support If you need more assistance, explore these support options: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review appointment through Meet with Apple. Appointments are available during local business hours on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board.

We are a development team building an application targeted specifically for the Southeast Asian market. We have been caught in a frustrating review cycle and are hoping to get some guidance on how to move forward. The Situation Our application is intentionally unavailable in the United States. Per Apple's guidance, we implemented a "We are currently not available in your country" error screen that displays when a user's location falls outside our supported regions. This is intentional, expected behavior — not a bug. The Problem Despite providing detailed testing instructions and dedicated test accounts tied to the correct region, our Reviewers consistently: Do not use the test accounts we created for them Do not follow the regional setup instructions we provided Access the app from a US-based location See the geographic restriction screen (the one Apple instructed us to build) Flag it as a bug and reject the submission We have confirmed this is the root cause, as the rejection notes reference the exact screen that Apple previously instructed us to implement. The reviewer spends fewer than 10 seconds in the app before rejecting. What We Need We are stuck in a loop with no clear path out. We are asking for: Escalation to a reviewer who will follow the provided testing instructions and use the correct region/account Clarification on how to properly communicate geographic restrictions to the review team so this is not flagged as a defect We have put significant effort into complying with every piece of guidance we have received, and we are committed to meeting Apple's standards. We just need a reviewer to spend more than a few seconds with our app using the correct credentials. Any help escalating this or pointing us to the right process would be greatly appreciated. Thank you. App Name: Hustla App ID: 6756264790

Does the App Review process have access to Apple-Hosted Asset Packs during review? My app uses Asset Packs to offer a library of data to the end-user (with a workaround, if unavailable), but I am frequently seeing the workaround screen in App Review with errors I haven't seen elsewhere. The latest error I encountered (via the App Review team's feedback) was: "A server with the specified hostname could not be found." thrown from (to my belief) AssetPackManager.shared.ensureLocalAvailability. This is unexpected to me, as both this code as well as the asset packs have already been released and are working reliably in production. Has anyone else experienced these issues?

Hello everyone, I am trying to understand whether this is a normal delay or if there may be an account-level review issue affecting my submissions. I am an individual developer. I submitted my first app for review on March 14, 2026. It remained without a meaningful response until March 31, 2026. During this time, I sent three expedite review requests, but none of them helped. Because nothing moved, I withdrew the previous submission and uploaded a third build for the same app. However, the app is still stuck in review flow. At the same time, I submitted my second app on March 22, 2026. I also requested an expedite review for that app, but it is still in Waiting for Review as well. So currently: • App 1 was first submitted on March 14, 2026 • Multiple expedite requests were sent • The original submission was withdrawn and a new build was submitted • App 2 was submitted on March 22, 2026 • Both apps have been heavily delayed • One is still in review flow, and the other is still Waiting for Review I would like to ask: 1. Has anyone experienced this kind of delay on an individual account, especially with multiple apps at the same time? 2. Could this indicate an account-level issue, manual queue hold, or some kind of hidden review flag? 3. Is there any effective way to escalate this beyond normal expedite requests? 4. Would contacting App Review again help, or is there another correct channel for this situation? 5. If I withdraw and resubmit again, is there any chance that it makes the delay worse? I am not asking for special treatment. I am only trying to understand what may be causing such an unusual delay and what the most effective next step is. Any insight from developers who faced a similar situation would be very helpful. Thank you.

Hello,I got the following message the second time. I dont know what to do.My app is reviewed and live, but my in app purchases are rejected. I read the message and was wondering about that. This did not happend with my non subscription iaps. I submitted a new "fake" binary with new version and in app purchases again.My app is reviewed and live with new version. My purchases not. I got this message again.We have begun the review of your In-App Purchase(s) but aren't able to continue because your submitted In-App Purchase(s) indicate a change of business model for your app. Therefore, we need to verify the implementation of your submitted In-App Purchase(s) in the app to ensure your app, and its In-App Purchase(s), are in compliance with the App Store Review Guidelines.Specifically, you have submitted auto-renewing subscriptions for review.Please upload a new binary for review and resubmit your In-App Purchase(s) with the binary so that we can continue the review.What to do?

Summary I am unable to link my In-App Purchases and Subscriptions to my app version in App Store Connect. The "In-App Purchases and Subscriptions" section described in Apple's documentation is not visible on my version preparation page, making it impossible to associate IAPs with my build before submission. Steps to Reproduce Open App Store Connect → My Apps → [App Name] Navigate to the app version in "Prepare for Submission" state Scroll through the entire version page The "In-App Purchases and Subscriptions" section is not present anywhere on the page Expected Behavior According to Apple's documentation and the note shown on the Subscriptions page itself: ▎ "Your first subscription must be submitted with a new app version. Create your subscription, then select it in the 'In-App Purchases or Subscriptions' section of the app's version page before submitting the version for review." The section should be visible and allow me to select my configured subscriptions. Actual Behavior The section does not appear on the version page at all. My subscriptions (monthly, yearly, lifetime) are all in "Ready to Submit" state and correctly configured, but there is no way to link them to the build. Account & Contracts Status All prerequisites are in place: All contracts (Paid Apps Agreement) are signed and active — nothing pending under "Business" / "Agreements, Tax, and Banking" Banking and tax information is fully set up No open items or warnings under the Business section in App Store Connect Despite all account requirements being fulfilled, the IAP linking section remains absent from the version page. Impact This is blocking my app from being approved. Apple's reviewer rejected my submission with Guideline 2.1(a) stating the subscription screen showed no available plans. The reviewer cannot see the IAPs because they were never linked to the version — which I cannot do due to this missing UI section. Environment App Store Connect via browser (Safari + Chrome, both tested) App status: "Prepare for Submission" IAP status: All three products "Ready to Submit" First-time submission (new app, never been approved before) Workaround None found. This appears to be a UI bug in the current version of App Store Connect. Has anyone else encountered this? Is there a way to link IAPs to a build via the API or any other workaround?

I have submitted my app and it has been waiting for review. I am the owner of the App and I applied for expedited review, but it didn't work. The version we submitted updated the information of the App. We consulted Apple and asked to continue waiting by using "Contact Us". I also submitted the information and they said to wait further. So we can only seek help from the reviewers here. Application ID: d6479289380

Dear App Review Team, Our app – Apple ID 6755677576 has been stuck in the “In review” status for over 10 days (since March 17, 2026). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Could you please clarify: • Is there a specific reason for this extended hold? • Is any action required from our side? • When can we expect the review to proceed? Thank you very much for your time and assistance.

Hi! Good afternoon how much time is it taking for you to get the app approved? I’m waiting since wednesay for the response of a review update from the apple team, my app was supposed to lunch on Monday

Hello, I would really appreciate if someone from Apple could take a look at this, as I believe there may be an issue with my submission or account. I submitted my app for review for the first time over a month ago, and it has been stuck in “Waiting for Review” ever since, with absolutely no updates. This delay is far beyond the typical review timeframes (which are usually just a few days). I have not received any rejection, feedback, or request for additional information. So far, I have already: Resubmitted the build Sent multiple support requests through App Store Connect Requested an expedited review (which was approved) Despite all of this, there has been no progress at all. I have also sent several support messages and emails, but unfortunately I have not received any response so far. It feels like my case is not being reviewed at all, which makes it very difficult to understand what is going wrong. The app is quite standard and does not contain anything that should require extended review. At this point, I am concerned that there might be: An issue with my developer account A submission stuck in the review queue Or some kind of internal flag that I am not aware of Has anyone experienced a similar situation where an app remained in “Waiting for Review” for over a month? And if anyone from Apple is reading this, could you please check if there is any issue with my submission? Any help or guidance would be greatly appreciated. Thank you.

Hello, I would really appreciate if someone from Apple could take a look at this, as I believe there may be an issue with my submission or account. I submitted my app for review for the first time over a month ago, and it has been stuck in “Waiting for Review” ever since, with absolutely no updates. This delay is far beyond the typical review timeframes (which are usually just a few days). I have not received any rejection, feedback, or request for additional information. So far, I have already: Resubmitted the build Sent multiple support requests through App Store Connect Requested an expedited review (which was approved) Despite all of this, there has been no progress at all. I have also sent several support messages and emails, but unfortunately I have not received any response so far. It feels like my case is not being reviewed at all, which makes it very difficult to understand what is going wrong. The app is quite standard and does not contain anything that should require extended review. At this point, I am concerned that there might be: An issue with my developer account A submission stuck in the review queue Or some kind of internal flag that I am not aware of Has anyone experienced a similar situation where an app remained in “Waiting for Review” for over a month? And if anyone from Apple is reading this, could you please check if there is any issue with my submission? Any help or guidance would be greatly appreciated. Thank you.

Hello, I would really appreciate if someone from Apple could take a look at this, as I believe there may be an issue with my submission or account. I submitted my app for review for the first time over a month ago, and it has been stuck in “Waiting for Review” ever since, with absolutely no updates. This delay is far beyond the typical review timeframes (which are usually just a few days). I have not received any rejection, feedback, or request for additional information. So far, I have already: Resubmitted the build Sent multiple support requests through App Store Connect Requested an expedited review (which was approved) Despite all of this, there has been no progress at all. I have also sent several support messages and emails, but unfortunately I have not received any response so far. It feels like my case is not being reviewed at all, which makes it very difficult to understand what is going wrong. The app is quite standard and does not contain anything that should require extended review. At this point, I am concerned that there might be: An issue with my developer account A submission stuck in the review queue Or some kind of internal flag that I am not aware of Has anyone experienced a similar situation where an app remained in “Waiting for Review” for over a month? And if anyone from Apple is reading this, could you please check if there is any issue with my submission? Any help or guidance would be greatly appreciated. Thank you.

Hi everyone, I am looking for some guidance on a delayed review for a new app launch. Our app, Vibe: Real-Time Social Radar (App ID: 6758596460), has been stuck in the "Waiting for Review" status since March 22nd. Here is the context: It is version 1.0.1. Prior to March 22, we had removed our submission a few times to fix minor metadata issues before the review started. I understand this resets our place in the queue. We have just submitted an Expedited Review request due to an upcoming launch deadline. My question: Does removing a submission multiple times trigger an automated "spam" hold or push the app into a longer Senior Review queue? Is there anything else I can do via App Store Connect to ensure the reviewer has what they need, or do I just need to wait for the Expedited Review team to respond? Any insights from developers who have experienced a similar delay recently would be greatly appreciated!

Thank you for submitting an update to the app, Macy's: Online Shopping & Save, for review. We noticed some issues that require your attention. Please see below for additional information. 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: d429df7a-35c1-4b8f-a85f-c0cce2dcd376 Review date: March 26, 2026 Review Device: iPhone 17 Pro Max Version reviewed: 2603.4.0 Guideline 5.1.2(iii) - Legal - Privacy - Data Use and Sharing Issue Description The app includes fingerprinting functionality that is designed to identify the user or device. Specifically, the app aggregates user and device data to track the user, either directly or indirectly using probabilistic methods. This functionality is found in services or code included in the app, such as AppsFlyer. Apps that fingerprint users or devices are not appropriate. Per section 3.3.9 of the Apple Developer Program License Agreement, neither you nor the app may derive data from a device in order to uniquely identify it. Next Steps Follow these steps to resolve this issue: Identify the fingerprinting functionality in the app. Some or all of this functionality may be provided by third-party SDKs. If you have questions about these SDKs, contact the SDK provider. Remove any functionality from the app that uses algorithmically converted device and usage data to identify the user or device. You should remove any related code or implemented SDKs that support fingerprinting. Since fingerprinting is never appropriate, requesting the user's permission to track them or disclosing fingerprinting activity in a privacy policy will not resolve this issue.

Hello Apple Developer Forums team, I would like to ask for help with my app review (App ID: 6755685130). I first submitted my app on February 14, 2026, and it has been almost 50 days. However, I still have not received clear feedback on what needs to be fixed. If there are issues with my app, I sincerely ask the review team not to provide only general guideline references. I still cannot tell which page, feature, or user flow is causing the problem. If possible, I would really appreciate screenshots, screen recordings, or a written description of the specific issue so I can make the right changes. I also want to clarify that this app is not AI-generated. It is a carefully planned app built with real effort using multiple native Swift frameworks. Thank you very much for your time and help.

Hello, I’m experiencing an issue with auto-renewable subscriptions in App Store Connect and would appreciate any guidance. I have created two subscriptions (monthly and yearly), and all required metadata appears to be fully completed: pricing (price tiers set and saved) availability (countries selected) localization (titles and descriptions added) App Review screenshot uploaded However, both subscriptions remain in the “Missing Metadata” status, and the “Submit for Review” option is not available. Because of this, I am unable to attach the subscriptions to my app version and proceed with App Review (Guideline 2.1(b) - App Completeness). What I have already tried: re-saving all fields multiple times re-uploading the App Review screenshot verifying pricing and availability checking localization reviewing introductory offers The issue persists. Has anyone encountered this before or knows what might be causing this status, even when all fields seem complete? Any help would be greatly appreciated. Thank you!

Hello, I hope you’re doing well. I recently submitted an update for my app, and I would really appreciate it if you could review it when possible. The latest version includes important fixes and improvements. Please let me know if anything else is needed from my side. Thank you for your time and support.

Hi everyone, I recently got rejected under Guideline 1.1.1 - Safety - Objectionable Content and I'm struggling to understand how my app falls under this category. Looking for advice from anyone who's dealt with similar rejections. What the app does: AutoSignal is a vehicle notification app designed for the Bulgarian market. It solves a very common real-world problem - needing to contact a car owner when their vehicle is double-parked, blocking you in, has its lights left on, or has been hit/damaged while parked. The core flow is: A user scans a license plate using their phone camera If the car owner is registered in the app, they receive an anonymous push notification (e.g., "Your car with plate XX 1234 XX is blocking someone" or "Your lights are on") The car owner can then take action Users can also report vehicle damage cases with temporary witness notes that auto-expire after 7 days. Why I believe it doesn't violate 1.1.1: The app does not expose any personal information. Notifications are fully anonymous - the sender never sees the car owner's identity, phone number, or any personal details. License plates are public information - they are visible on every car on every street. The app doesn't scrape or store plate databases. The use cases are entirely constructive: notifing someone their car is being towed, blocked in, damaged or has lights on. There is no messaging or direct contact between users - only predefined notification templates. Damage case witness notes are temporary (7-day expiry) and designed to help with insurance claims, not harassment (everything is opt-in model). What Apple said: "Issue Description The app includes content that could be considered defamatory or mean-spirited. Specifically, your app allows users to collect license plate information and send activity associated with the license plate. Content that is likely to humiliate, intimidate, or harm a targeted individual or group is not appropriate for the App Store." What I've tried/considered: Adding content moderation and reporting features Limiting notification frequency (rate limiting on the backend) Requiring car owners to opt-in by registering their own plates before they can receive any notifications Has anyone successfully appealed a 1.1.1 rejection for a similar use case? Should I request a call with the App Review Board? Any suggestions on what additional safeguards I could highlight or implement to address their concerns? Thanks in advance for any guidance.

Hi everyone, I am experiencing an unusual delay with my app update. I submitted version 1.0.3 of my app, "MarketNow", on March 12, 2026, but it has been stuck in the "Waiting for Review" status for 9 days now. Typically, updates are reviewed within 24–48 hours, so this 9-day wait is quite concerning. I have already sent a formal inquiry through App Store Connect but haven't received a specific update yet. Is anyone else seeing long wait times for updates this week? Could this be related to a backlog before the April SDK deadline, or is there a known issue with the Finance category review queue? Any insights would be helpful. Thanks!

Hello everyone, I’m looking for some clarification and advice regarding an unexpected App Review rejection under Guideline 4.1 – Copycats. My app has been live on the App Store since May 2024, and during that time, it has maintained the same core flow, structure, UI, and feature set. There have been no major redesigns or attempts to imitate any other app. Recently, I submitted a new version (v3.2) with only minor changes related to ad logic implementation (no UI/UX changes, no branding changes, no metadata changes). However, this update was rejected with the following reason: “This app or its metadata appears to be misrepresenting itself as another popular app or game…” This has left me quite confused for a few reasons: The app has been approved and publicly available for nearly 2 years There were no significant design or branding changes in this submission The rejection seems unrelated to the actual changes made in this version My questions: Has anyone experienced a situation where an app was flagged as a copycat after being live for a long time? Is it possible that Apple updated their internal policies or comparisons, causing older apps to be re-evaluated? Could this be triggered by similar metadata (keywords, screenshots, descriptions) rather than the app itself? What would be the best way to respond in App Store Connect Resolution Center in this case? I fully respect Apple’s guidelines and have no intention of copying or misleading users. I’d really appreciate any insights or suggestions on how to resolve this properly. Thank you!

Hello My app got rejected with the message "We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences." In short, my app is a vpn app built entirely by me. In Russia almost all vpn protocols are blocked: wireguard, openvpn etc. And the only protocol they could not block was vless. It was hard to implement it, i spent like 3 weeks on it writing my own package on flutter. The app first was uploaded to android and shared through testflight with some of my friends. And everyone switched to my app, because it works perfect for their needs: accessing instagram, twitter etc. Those apps are blocked here. So on my first attempt publishing i got 2 errors: Vpn should be published on the account that is organization Spam rejection I registered a company and switched from individual account to a company. I also changed the ui of the app (although i agree most vpns share the same concept design). I got rejected again with only "Guideline 4.3(a) - Design - Spam". I appealed with a question why was it it rejected, explaining that the app was built by me, and of course, i use some libraries. I got the same roboting response. After that i added some features: Built in private browser Network connection speed Today submitted the new version hoping it would pass, but yet again got "Guideline 4.3(a) - Design - Spam". I'm really frustrated, because i spent 3 months developing the app. I understand there are dozens of vpns. But vpn is not exactly the simple feature app. Some are bad, some are good, and some doesn't work at all. My app doesn't have any ads and paid subscriptions. I also renamed my app to "Incognito - Browser, VPN". But can't get pass. Would like to get some advices. Please help P.S. Sorry for my bad grammar