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.

Hi everyone, I submitted an appeal to the App Review Board on May 27, related to a rejection under Guideline 4.3(a). (We noticed your app shares a similar binary, metadata, and/or concept as other apps you already submitted to the App Store, with only minor differences.) (The app is named LucidYou and was submitted through my personal developer account.). So far, I haven't received any update or response in App Store Connect or via email. I fully understand that WWDC may have delayed reviews, and I appreciate how busy this time of year is. Still, I just want to make sure my appeal was received and is still being considered. Has anyone else experienced longer-than-usual response times for appeals recently? Should I follow up via App Store Connect again or wait a bit longer? Thanks in advance — any advice or shared experience would be appreciated!

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

Hi everyone, We’re going through our first App Store review, and honestly, it’s been incredibly discouraging. We’ve put a huge amount of effort into building a financial app that helps real users, and our U.S.-based company has done everything possible to meet Apple’s guidelines and review requirements. Still, we keep getting rejected - and it's starting to feel like we’re caught in a loop with no clear way forward. First, the app was rejected because the test login supposedly didn’t work. We double-checked everything and found it was functioning correctly. The reviewer likely didn’t notice that the country code is pre-filled and tried entering it manually, which led to confusion. Then we were asked to provide detailed instructions to access all sections of the app - fair enough. We fully understand that financial apps require deeper scrutiny, and we provided all requested information, including step-by-step access instructions and realistic test data. Next, we submitted our legal agreements with our partners. These are official partnerships, and our legal team ensures we meet all U.S. regulatory requirements. Despite this, the reviewer rejected the app again, saying the documents were low quality - even though everything was clearly legible. Still, we re-scanned over 70 pages and uploaded everything again in higher resolution to be extra careful. Now, we’re being asked for a demo video - even though we’ve already provided full test access, documentation, and data. We’re starting to feel like no matter what we provide, it won’t be enough. And honestly, it’s taking a real toll on our team. We’re not trying to bypass any rules - quite the opposite. We want to do everything the right way. But right now, it feels like we’re being penalized for things that aren't clearly explained or fairly evaluated. We deeply respect Apple’s review process, but we also hope our case can be looked at with fresh eyes and understanding. Has anyone here experienced something similar? Any advice on how to move forward would mean a lot. Thank you for reading - we really appreciate this community.

I can't pass rule 4.3b. I'm practicing horoscope. How do you think I should proceed? Is it possible to publish this application?

My app / subscription gets rejected with the following: Guideline 2.1 - Performance - App Completeness We have returned your in-app purchase products to you as the required binary was not submitted. When you are ready to submit the binary, please resubmit the in-app purchase products with the binary. and Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review. Once your binary has been uploaded and your first subscription has been submitted for review, additional subscriptions can be submitted from the Subscriptions section. Learn More ...ive tried all kinds. I archive a new build, upload it, update the app information top show new build so it ties in...and still nothing works. it is incredible frustrating. Can anyone help please. Ive wasted days on this

Hi All, So I have been trouble publishing my app on App Store as it keeps rejected by App Review. Specifically guideline 2.3.10 and 3.1.1. Although I don't have any metadata for third-party services in my app or "tip" button anywhere within my apps binary. I do however have external links to my projects help and Github which have that information, which I am getting rejected for. However, I want those external links because I need to have google play on the projects github page so users can know that are visiting to github that they can also download it officially from those sources as well. It is also useful to tell users that those are the only official platforms that I support, and downloading from anywhere else is not advised. Is there an acceptable solution where the google play and donation link can be kept on the github page? It is not really built into the binary itself anyways so I thought it would be allowed. Here is an link to my projects repo in case that helps clarify: https://github.com/SrS2225a/custom_uploader Really hoping to resolve this. I’d love to get the app on the App Store as soon as possible.

Hello Apple Developer Team, We’re preparing a future version of our enterprise app, Lenovo XClarity Mobile, and would like to request guidance regarding a potential ATS exception scenario. Context: The app is used exclusively in enterprise environments. It connects via USB to a local Lenovo Think Server (embedded device). The connection is entirely offline (no internet use). The app uses SSDP to discover the device over the USB-attached local network. Communication occurs via HTTPS over 192.168.x.x, tunneled through the USB interface. The server uses a factory-generated self-signed certificate. Planned Behavior: In a future release, we plan to prompt the user with a certificate trust confirmation if a self-signed cert is detected locally. Only if the user explicitly agrees, the connection proceeds. Here’s a simplified code example: if challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodServerTrust, let serverTrust = challenge.protectionSpace.serverTrust { let accepted = UserDefaults.standard.bool(forKey: "AcceptInvalidCertificate") if accepted { let credential = URLCredential(trust: serverTrust) completionHandler(.useCredential, credential) return } // Show user confirmation alert before accepting } **Key Notes:** This logic is not in the current App Store version. ATS is fully enforced in production today. The exception would only apply to USB-based local sessions, not to internet endpoints. Question: Would such an implementation be acceptable under App Store and platform guidelines, given the restricted use case (offline, USB-only, user-confirmed self-signed certs)? We're looking for pre-approval or confirmation before investing further in development. Thank you in advance!

Build is currently rejected but the submission status is marked as "complete" (even though it isn't). I think this is what's preventing me from replying to the reviewer who is now waiting on info from me. How am I supposed to reply to them if the option is no longer available? I already submitted another build - will they eventually just review that or not? If I expire the build that is rejected, will that get them to stop reviewing it?

Hello. Appstore is rejecting my app according to article 4.3. But the app is not a copy, what should I do in this case? It is useful to specify the details; I had previously registered with my personal account and the Appstore stated that unfortunately VPN applications are not accepted with a personal account. Then they told me to register with a company account and make this application from the company account. (When I sent the application for review on my personal account, there were only a few incorrect items and the most important reason why it was not accepted was that it was a personal account). Now we send the application for review with our company account, but as soon as it is put into in review mode, it is quickly rejected due to 4.3 spam. The app is not a copy but completely custom created. I don't know how to find a solution. Can you please help with the issue?

Dear Apple Review, I submitted my app for review on June 11th, and it has remained in “Waiting for Review” status for the past 8 days without any updates or communication. As this is my first app submission, I was expecting the review process to follow the usual 24–48 hour timeframe, as publicly stated. I’ve noticed that other apps are being reviewed and even updated multiple times in the meantime, which makes this prolonged delay particularly concerning. I would greatly appreciate it if you could look into the status of my submission and provide any updates or guidance regarding the next steps. Thank you for your time and support. Best regards,

Hoping this is the right place to post. My app submission was rejected as my support url doesn't include a way to contact the developer. My previous app didn't have this problem, but the rules have changed now. Does anyone have any tips/templates that could be used to create a site that allows comms. I already own my own domain. Thanks , G

I've submitted my app on May 17, 2025, and has been stuck 'in review' since (9+ days). I've contacted support numerous times with little success. One support rep said that my app was "expedited" 5 days ago, but not changes to the status of my app since. I'm afraid of deleting the submission and resubmitting as it might repeat this long process. Getting my app reviewed and hopefully listed on the app store as soon as possible is absolutely crucial to the success of my company. And every day spent 'in review' is a huge hurt on the conversions/sales on the people already waiting to try the app. Any help or visibility would be appreciated

Hello, I submitted an appeal after my app was rejected under Guideline 4.3(a). It has now been over 5 days and I have not received any reply from the App Review Team. Has anyone experienced similar delays recently? Does Apple respond eventually or is there something else I should do? Thank you in advance.

Hello, I am looking for a better understanding of Guideline 1.4.2, which states that "Drug dosage calculators" must be developed by drug manufacturers, hospitals, universities, or other approved entities. My main question is: What is Apple’s exact definition of a "Drug Dosage Calculator"? - Does the term exclusively refer to apps that calculate dosage (dose, interval, and treatment duration)? - Are apps that do not make clinical decisions, but only display bibliographic references based on user-entered data, also considered Drug Dosage Calculators? - If an app only performs basic mathematical operations on a dose value entered by the user, without suggesting medications or treatments, does it still fall under this restriction? I would like to better understand how Apple differentiates a medical support app (which only presents data) from a dosage calculator (which makes clinical decisions). I appreciate any insights from the community!

Section 1: Our game was developed using Cocos Creator 3.8.5, written in TypeScript. The team spent nearly two years completing it. Initially, our submission wasn't classified under Guideline 4.3(a). The first four reviews provided normal feedback, which we addressed. However, after a subsequent rejection citing 4.3(a), we considered whether similarities in gameplay concepts, narrative, or art assets might exist. In response, our team introduced unique features not found in other App Store applications. We completely redesigned our original art assets to ensure originality and extensively modified aspects potentially resembling other developers’ work. This included removing all third-party SDK modules except Apple Pay and Sign in with Apple. Despite these significant efforts, we still received a 4.3(a) rejection. We have now iterated over 20 versions but continue to face this issue.  Section 2: Our game’s business logic code (excluding the Cocos engine code) is entirely original and should not duplicate others' work. Could the rejection stem from similarities in compiled JSC files or binaries generated from JavaScript? Would it be possible for the review team to examine our source code for verification? We are deeply committed to launching on the App Store and can provide comprehensive proof of originality, including but not limited to: Full GIT commit history and source code from inception to present  Documentation proving original art creation  Evidence demonstrating unique gameplay mechanics distinct from other developers  Cocos Creator Engine: https://www.cocos.com/creator-download Games developed with Cocos have successfully launched on platforms like WeChat Mini Games and Android app stores in China, where they are well-received by users. Honorable Review Team, could you please conduct a manual inspection of our source code and evaluate the gameplay? We believe Apple—the world’s most innovative technology company—employs highly professional and insightful experts dedicated to delivering unique, high-quality experiences for players. However, the persistent 4.3(a) rejections are concerning, especially since numerous Cocos-based games are approved globally. We’ve revised the game over six months across 20+ versions, yet each rejection cites identical reasoning:  Apple's Rejection Message Translation: Hello, The issues we previously identified still require your attention. If you have any questions, we’re here to help. Please reply to this message in App Store Connect. Review Details Submission ID: 68 bd1e 18-6 EAA-4a 19-976 e-c 7 B2 E1 ff 0 e 44 Date Reviewed: June 28, 2025 Version Reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We continue to find that your app shares a similar binary, metadata, and/or concept as other apps submitted to the App Store with only minor differences. Submitting similar or repackaged apps constitutes spam, creates clutter, and diminishes user discovery of genuinely new applications. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a truly original application with distinct content and functionality. Support Reply in your preferred language if you need assistance. For further support, use the Contact Us module.  Seek advice from fellow developers and Apple engineers on the Apple Developer Forums.  Request an App Review consultation via Meet with Apple (availability varies based on local hours, Tuesdays and Thursdays).  Provide feedback on this process and your review experience by completing a brief survey.

I want to clarify why both email and phone number are mandatory at registration, while still allowing users to log in with either method if one fails. Email Address (Collected at Registration) Account Creation & Verification: We use email to establish a unique, verifiable account for each user. This prevents duplicate or fraudulent profiles. Primary Communications: All booking confirmations, trip updates, support requests, and in-app chat messages between care seekers and carers are sent via email. This ensures users have a reliable record of every transaction and message. Phone Number (Collected at Registration) OTP-Based Security: We send a one-time password (OTP) via SMS during registration and login. This SMS-OTP step is critical to confirm that the user owns the provided phone number and to safeguard against unauthorized account access. Critical Trip Notifications: During a booked trip, carers and care seekers must receive time-sensitive alerts (e.g., gate changes, flight delays, check-in reminders) even if they’re not actively using the app. SMS ensures immediate delivery—even if a user’s internet connection is unavailable. Support & Emergency Contact: If there’s an urgent issue mid-trip (e.g., a missed flight, sudden cancellation, or a medical concern), our support team can reach users directly via phone to resolve issues in real time. Flexible Login Options Fallback Mechanism: If a user cannot access their email (e.g., server delay or no internet), they can request an OTP via SMS to log in. Conversely, if SMS delivery fails (e.g., network outage), they can choose to receive a OTP by email. This redundancy guarantees that users aren’t locked out due to a single point of failure. We believe both email and phone number are directly tied to our app’s security model, communication requirements, and overall user experience. All collection and usage details are transparently disclosed in our Privacy Policy (https://b4t.com/legal/privacy-policy) and User Terms and Conditions (https://b4t.com/legal/user-terms-and-conditions).

Dear Apple reviewer: We are a social media app that has been submitted for review for the first time. I have been waiting for 2 weeks in the 'awaiting review' status. We have applied for expedited review, but have not made any progress; Our users have been anxiously asking when we will launch, and they are very eager to use these features. Apple ID：6746186652. Looking forward to your reply, thank you!

I have created an app with one subscription for one year. The subscriptions was rejected for more as 3 time. But I don't know, what I must do. No description or no email from apple. Only I can see "developer action is needed". I have changed the name of the subscription group, I have changed the localization. but also it was rejected. I have resubmitted an app version with text, that the subscription to checked. but the app was distributed only the subscription. the text was ignored. now the state for the group localization is in waiting for review. but, the subscription under the subscription group is approved. what can I do?

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