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.

After months of hard work developing an app with unique mechanics and a distinct user experience, we recently faced a rejection under Guideline 4.3(b) (Spam/Saturated Category). The feedback we received stated that there are "already enough of these apps on the App Store." While we completely understand Apple's need to filter out low-quality clones, it feels like this guideline sometimes overlooks genuine originality. The most frustrating part for independent developers is that the category you fall into seems to matter more than the actual value your app provides. Whether the app is positioned in lifestyle, entertainment, or productivity, a rigid "category quota" can prevent reviewers from truly seeing the unique features we built. This creates a significant hurdle for new entrants and makes it incredibly difficult for fresh ideas to break into established categories. It feels less about the quality of the application and more about timing—as if early arrivers have a permanent advantage over newcomers, regardless of how much innovation the new app brings to the table. Ultimately, we believe this limits consumer choice. Users deserve the opportunity to discover and decide between new, modern alternatives, rather than having their options restricted by a pre-determined saturation limit. We hope Apple reconsiders how 4.3(b) is applied, ensuring that the App Store remains a place where truly innovative apps, regardless of their category, have a fair chance to be evaluated on their own merits.

Hello, I’m having an issue with my first subscription for my app WealthSlices, where the subscription appears correctly when testing locally from Xcode, but App Store reviewers appear unable to retrieve the product. Symptoms When I run the app from Xcode on my iPhone using the Sandbox environment: The subscription loads successfully. The purchase sheet appears. I can complete a sandbox purchase. However, when App Review tests the app, the paywall fails to load products and the app shows the following message: "No Products found. Purchases are temporarily unavailable on this device." Environment App: WealthSlices Platform: iOS Testing locally via Xcode → Sandbox Apple ID Subscription type: Auto-renewable subscription Product: WealthSlices Basic ($9.99/month) StoreKit: StoreKit 2 Current build: 1.0.7 (Build 32) What works locally When running via Xcode: StoreKit successfully fetches products. The subscription sheet appears with the correct pricing. Sandbox purchase flow completes normally. What appears to happen during App Review It appears that Product.products(for:) returns an empty list when the reviewers test the app. Things I have already verified The subscription is created in App Store Connect. It is attached to the current app version under In-App Purchases and Subscriptions. The subscription has pricing and localization configured. The subscription is in Ready to Submit status. The bundle ID and product ID match the code. Paid Apps Agreement is active. I uploaded a new build after creating the subscription. Question Is there something specific required for first-time subscription submissions that might cause the product not to appear during App Review but still work in local sandbox testing? Is there a known delay or propagation requirement for subscriptions before they can be fetched by Product.products(for:) in TestFlight/App Review environments? Any guidance would be greatly appreciated. also there doesn't seem to be an option to select the subscription over at https://appstoreconnect.apple.com/apps/6754225986/distribution/ios/version/inflight but there is no option to add it Thank you!

Re. APP ID 6758894172 This app was submitted on February 16, and since then it has been showing as waiting for review. I have contacted the support email multiple times as well as requesting the review to be expedited, but no response and no change in app status. Could you please investigate this matter and let me know what the issue is?

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?

Hello, I am posting here to ask whether anyone has recently experienced a similar situation. My app has remained in “Waiting for Review” for an unusually long time. Timeline: The initial submission stayed in “Waiting for Review” for about 10 days I assumed it might be related to a temporary queue or system issue, so I canceled that submission and resubmitted The current submission was resubmitted on March 19, 2026 It is still showing “Waiting for Review” I have contacted Apple through multiple support cases regarding this issue. Some of those cases have not received a response, and despite these inquiries, there has still been no visible review activity. In addition, I submitted an expedited review request on March 17, 2026. Later, on March 31, 2026, I received a response from Apple Developer Support confirming that the expedited review request had been accepted and that the review should begin shortly. However, even after that response, the submission still remains in “Waiting for Review,” and there has been no visible change indicating that the actual review has started. For reference, the related support case IDs are: 102846840976 102853198849 I have also already reviewed and updated the relevant account-side items, including agreements/contracts and related App Store Connect requirements, and I do not see any visible issue on my side. Current status: No rejection No “In Review” status No visible error in App Store Connect At this point, I am trying to understand whether: this is currently a known review queue delay, it is normal for an accepted expedited review to remain in “Waiting for Review” for this long, or there may be some hidden submission or account issue that does not appear in App Store Connect. If anyone has experienced a similar situation recently, I would appreciate hearing whether the review eventually started on its own or whether any additional action was required. Thank you.

Hello, I am posting here to ask whether anyone has recently experienced a similar situation. My app has remained in “Waiting for Review” for an unusually long time. Timeline: The initial submission stayed in “Waiting for Review” for about 10 days I assumed it might be related to a temporary queue or system issue, so I canceled that submission and resubmitted The current submission was resubmitted on March 19, 2026 It is still showing “Waiting for Review” I have contacted Apple through multiple support cases regarding this issue. Some of those cases have not received a response, and despite these inquiries, there has still been no visible review activity. In addition, I submitted an expedited review request on March 17, 2026. Later, on March 31, 2026, I received a response from Apple Developer Support confirming that the expedited review request had been accepted and that the review should begin shortly. However, even after that response, the submission still remains in “Waiting for Review,” and there has been no visible change indicating that the actual review has started. For reference, the related support case IDs are: 102846840976 102853198849 I have also already reviewed and updated the relevant account-side items, including agreements/contracts and related App Store Connect requirements, and I do not see any visible issue on my side. Current status: No rejection No “In Review” status No visible error in App Store Connect At this point, I am trying to understand whether: this is currently a known review queue delay, it is normal for an accepted expedited review to remain in “Waiting for Review” for this long, or there may be some hidden submission or account issue that does not appear in App Store Connect. If anyone has experienced a similar situation recently, I would appreciate hearing whether the review eventually started on its own or whether any additional action was required. Thank you.

Hi everyone, My app has been stuck in "In Review" status for over 20 days with no updates. I submitted the app on March 1, 2026, the status changed to "In Review" on March 4, 2026, and after that no changes. App ID: 6755649144 I also reached out to Apple Developer Support on March 15 but haven't received any response. Support Case ID: 102845096494 Could someone from App Review please take a look? Also any advice on how to move things forward would be appreciated. Thank you!

New member here, please be gentle :) I am getting ready for App Review for my first iOS app, and I am curious if ANY level of obfuscation is allowed? Say I had a drone controller App, I might have something like this: struct Drone{ var name : String var forwardVelocity : Double var lateralVelocity : Double var verticalVelocity : Double var receivedSignalStrength : Int var rssThreshhold : Int var gpsCoordinates : Data func reverseCourse(){ //do a 180 //... } } func onUpdateReceivedSignalStength(drone:Drone){ if drone.receivedSignalStrength < drone.rssThreshhold{ drone.reverseCourse() } } But I don't really want to make it easy for someone to pull the strings from the binaries and try and copy my work. I realize it's pretty much inevitable, but it seems sensible to protect my IP as much as I can. Is something like this acceptable? struct D{ //obfuscated Drone var parameter1 : String //name var parameter2 : Double //forwardVelocity var parameter3 : Double //lateralVelocity var parameter4 : Double //verticalVelocity var parameter5 : Int //receivedSignalStength var parameter6 : Int //rssThreshhold var parameter7 : Data //gpsCoordinates func funcSeven(){ //do a 180 //... } } func funcSix(d:D){ //check if signal strength requires a course reversal if d.parameter5 < d.parameter6{ // signal strength less than threshhold d.funcSeven() //reverse course } } The comments make it clear what the similarly-named parameters are doing, and what the functions do. I fully understand that something like the below is a no-no, just writing it made my eyes bleed: struct DDF{ var SXR : String var KYV : Double var GTC : Double var DKY : Double var ENY : Int var WKN : Int var DJV : Data func BDO(){ //do a 180 //... } } func PUL(KHY:DDF){ if KHY.ENY < KHY.WKN{ KHY.BDO() } } Is there any level of IP protection through obscurity that is acceptable? I realize that the more genericized the variable and function names are, the harder it is to debug, but that might be an acceptable trade-off against IP protection. To be clear, my app isn't anything to do with drones, this was just a vehicle to ask the question with. My code isn't currently at all obfuscated, everything is in clear terms, but I am wondering if I could/should obfuscate the critical parts before App Review and release? The reason for my concern is that a key feature of the app is something very novel, and I have filed a patent application for it. The patent (if granted) won't be granted for 18-24 months, so anything I can do to protect the IP seems like the right thing to do. As a complete newcomer to releasing Apps, I have no experience at all, so I would be grateful for any help/steers from those that do have experience in trying to protect their IP while not making life difficult for the App Review team. Thanks in advance! 6502A

Hello everyone, My app (ID: 6758741935) was submitted on Feb 15, 2026 at 3:51 PM, 2026, and has been stuck in "Waiting for Review" status for over 50 days. I contacted Developer Support and received confirmation that it's proceeding normally, but no update since. On average, Apple reviews 90 percent of apps within 24 hours. However, there might be cases that need more review time, but mine exceeds 50 days.. Any recent experiences with long queues? Thanks!

Now I consider myself a pretty patient person. But I have been waiting over 3 weeks for a very simple app review of a point release of my app. Which is holding up months of work which is live on android. I have tried the accelerate your review process and it led no where. It's quite disappointing that things like this happen and there seems no accountability or tracking for its resolution.

Hello, I would like to request an escalation regarding my app review status. My app (Apple ID: 6758756966) was submitted for review on February 24 and has been in “Waiting for Review” status for an extended period, with no progress so far. I have contacted Apple Developer Support multiple times (Case IDs: 102840237455, 102840079647, 102846664998, 102841727941) starting from March 9, but unfortunately, I have not received any response to any of these requests. I have also submitted three expedited review requests, but none of them have been acknowledged. Could you please: • confirm whether the submission is still active in the queue • check if there are any issues preventing it from moving forward • and assist in escalating the review if possible If any additional information is required from my side, I am ready to provide it immediately. Thank you very much for your time and support.

Guideline 4.2.2 - Design - Minimum Functionality I'm trying to understand why this is happening. My app is a resource for Domestic Violence Survivors. Its not a wrapper of a mobile site -- there isn't a tool that exists like this currently on the market. The app has native features like Quick Exit and a Privacy cover. How can I get past this? What else is needed?

My app has been rejected twice under Guideline 2.1(b) - App Completeness because my In-App Purchase subscriptions have not been submitted for review. Both subscriptions have ALL required metadata complete: Display name and description ✓ Price set for 175 countries ✓ Review screenshot uploaded ✓ Localization (English U.S.) ✓ Paid Apps Agreement active ✓ The problem: both subscriptions show "Missing Metadata" status even though everything is filled in. Because of this, the "In-App Purchases and Subscriptions" section does not appear on the app version page, so I cannot attach them to the submission. I have contacted Apple Support and replied to the rejection message 4 days ago with no response. Has anyone experienced this? How did you resolve it?

Enviei meu app (xek) pra revisão desde terça feira. Recebi a solicitação de ajustes na quarta e depois de ajusta-lo na quarta mesmo, ele ficou travado em “Aguardando revisão” desde então. Um app simples que está no processo de liberação desde terça e desde quarta sem nenhum retorno da Apple, isso eh normal? Tenho outro app que nunca demorou tanto nas aprovações. mandei mensagem por outros canais e nada. Vamos ver se por aqui tenho algum retorno.

I am having issues getting feedback from Apple review to understand whether the game I created is not unique enough or whether it is something else. My game was inspired by Wordle and uses the idea of marking letters as green/yellow to provide hints, but in my view (and the view of all the testers I've had), creates extremely different and unique experience, which is the core goal of guideline 4.1. Core gameplay: The game is real-time multiplayer (or vs an adaptive difficulty computer that mimics human play), where two players each choose a starting hint word, then based on those hint words (yellow/green letters), in 3 minutes, need to find as many unique words that fit those hints. You see what the player guesses and can't guess the same words. Each word gives 1 point, but the last word and 1 bonus word give +5 points. At 120 seconds, a third hint is provided that limits the number of possible options (making it more likely to reach the very final word with +5 bonus or the bonus word if it wasn't guessed yet). There's a rating system, a customisable reward firework system (which you can show off in multiplayer matches). The game is in Lithuanian only, not targeted globally. When playing with another player, there's a voice chat possibility (initial idea was to create a fun way for friends to have quick voice chats daily who like word games). Screenshots used in store listing attached at the end of the post. App review responses I have had close to 10 back-and forth messages with Apple review, trying to ask which parts are the issue (or whether it's the whole concept of the game), but the responses have always been very abstract and vague, no matter how much I ask for specifics, mentioning metadata and in one message, the screenshots. An example response: Regarding guideline 4.1, the app and its metadata contain content that resembles Wordle without obtaining the necessary authorization. To resolve this issue, it would be beneficial to demonstrate your relationship with any third-party brand owners represented in the app. Additionally, the app’s metadata includes third-party content that resembles a popular app or game already available on the App Store. This content may have been sourced from a developer’s website, distribution source, or a third-party platform. Changes I have made so far/things I checked: No mentions of Wordle anywhere in the metadata The colors in the game are not the same ones that Wordle uses Changed the letter elements to be different from Wordle (circles, not squares). Made the screenshots focus on the fully unique items first (the fireworks system, the multiplayer aspect) Sent video recordings to Apple Review to demonstrate how different the gameplay is compared to Wordle Repeated multiple times there is no association with Wordle. Asked if the name "Žodlė" is the piece of metadata that is causing the issue (I would consider renaming if it is) - but got no reaction to this. I have also submitted a formal appeal through the App Review Board more than a week ago but have not yet received a response. For reference, the same app was recently approved and published on Google Play without any copycat concerns. This has been a hobby project of mine for learning about creating and publishing an iOS app, but has turned into something that quite a few people enjoy, so I would like to make sure that I'm not giving up too early trying to publish it. Would love to hear the opinion of someone with more experience on whether there's a chance to get this published or whether any kind of a game that involves guessing words with yellow/green hints would be considered a copycat of Wordle.

Hello everyone, My app (ID: 6756186616) was submitted on Mar 15, 2026, and has been stuck in "Waiting for Review" status for over 17 days. I contacted Developer Support (case #20000111565861) and received confirmation that it's proceeding normally, but no update since. On average, Apple reviews 90 percent of apps within 24 hours. However, there might be cases that need more review time, but mine exceeds two week. Any recent experiences with long queues? Thanks!

Hi everyone, I’m stuck in the App Review process with In-App Purchases (subscriptions) and would really appreciate some guidance. Situation: I have an app with subscriptions (Premium Monthly and Premium Yearly) Both subscriptions are in “Waiting for Review” status I submitted a new app version for review Issue: The app was rejected with: “subscriptions were unavailable at time of review” Before that, I also received a rejection saying the reviewer could not locate the In-App Purchases. What’s confusing: Subscriptions are not yet approved (still “Waiting for Review”) In the current app version page, I do not see the “In-App Purchases” section at all, so I cannot confirm whether they are attached to this build The app correctly loads products via StoreKit, but returns empty when products are not available Questions: Do subscriptions need to be approved before they can be used during app review? Should I reject the current version and resubmit while manually attaching the subscriptions? Is it expected that the “In-App Purchases” section is missing from the version page in this case? Has anyone experienced this “subscriptions unavailable” issue while IAPs are still “Waiting for Review”? I feel like I’m stuck in a loop where: The app needs IAP to pass review But IAP are not available yet during review Any advice on the correct process would be greatly appreciated. Thanks!