I am trying to upload my app to the app store, but app review says that nothing is happening when they click my "purchase" button for my subscription paywall. I have tested my subscription button process on my local device numerous times, with a sandbox account and never a problem. For context, I am using revenuecat to process my payments here. Any advice on testing IAP's, edge cases that could cause this problem, or anything that could help me solve this? Thank you!

How long do appeals normally take? I submitted my appeal on 2024-11-28 and its been a month now with no response from Apple whatsoever. I've sent messages to the review as well asking on this but its just the generic - submit one and wait. You can't check on the progress of the appeal either as there is no specific place from what I saw where you can check this like a support ticket. In the mean time I can't release my app on the App Store while the Google Play version is going on just fine. Is there anyway I can bump this its silly stuff that they denied the app on and I'd like to get it sorted ASAP otherwise I spent R2k on a dev license for nothing - its quite infuriating 😑

In December 2022 we published an app. Since then, we published countless updates, never had any problem with the app. We have hundreds of new users daily, got far more than 100k downloads in total, have paying/subscribed users. The beginning of December 2024 in app update that shoudl fix a crucial bug, we suddenly received this rejection: _"Guideline 4.3(a) - Design - Spam: We continue to notice that your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps."_ What makes it even worse is: In our latest update that we published is a very crucial bug. Literally just days after we noticed this bug we fixed it and sent another version for review. Since then the rejections happened. I do not understand why Apple, out of nowhere, suddenly, prevents us to update/fix our application. It caused us to work more than 10+ hours per day during the christmas holidays. We made so many changes to our app, rebranded our entire app, improved UI/UX, added unique features, languages, and so on to our app. But whatever we send for review simply gets rejected again, and again with the same reason. What is happening? Why would they even prevent an app that has a 100k+ downloads, paying/subscribed users, was released two years ago, etc. from updating? We have responsibilities towards our users (especially paying users!) It is incredibly frustrating and demotivating to have an incognito person (who knows who the app reviewer is?!) above you and your product and to literally decide over YOUR faith. We already sent it to appeal but no reply at all. As we write this, we already have lost thousands of dollars in the past few weeks. Not only have we lost so much money, but we have worked 80+ hours to fix this problem, simply to get the same old rejection without real explanation. Did I already mention that we published the app in December 2022? We have no control over that someone copies our product our our features. Why would they punish us? Why was it totally fine to publish the app and to have 20+ (or even far more) updates published without any problem, but when we try to fix a crucial bug, suddenly we get rejected like this? After spending such a long time to add unique features, updating the app, and so on, to simply get rejected again, after we tried so hard to solve this problem, we get rejected just with the same reason. I asked them: What do you exactly want us to change? No answer. Just the same copy and paste reply. It is incredibly frustrating. I am even thinking to take legal actions. They are literally preventing us to update our product. We are the ones who get emails every single day from customers. We have a huge monetary loss as well. I feel so disappointed and angry at the same time.

My app is live on the App Store with basic functionality and no login feature. I've now added sign-in options, including Sign in with Google,Apple. While the app works fine on both simulators(iphone, ipad) and my physical iPhone without any crashes, it was rejected during App Review due to a crash. The crash reports provided are specifically from iPads. On iPads, my app opens in a layout designed for phones. Here are the crash log ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Incident Identifier: 20E15987-98DF-4F19-884A-6C64117FFBBE CrashReporter Key: 7deeb72ac4e45243b75a1d89c4f0078f34cc1a43 Hardware Model: iPad13,16 Process: Path: /private/var/containers/Bundle/Application/C237DF18-C3BC-41EB-B504-5C0A73262D3D/App_name/App_name Identifier: Bundle_identifier Version: 1.9 (5) AppStoreTools: 16C5031b Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: Bundle_identifier [884] Date/Time: 2024-12-31 04:30:19.9584 +0400 Launch Time: 2024-12-31 04:30:19.8246 +0400 OS Version: iPhone OS 18.2 (22C152) Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: . [722] Triggered by Thread: 10 Application Specific Information: abort() called Thread 9: 0 libsystem_pthread.dylib 0x211ad946c start_wqthread + 0 Thread 10 name: Dispatch queue: com.facebook.react.SwiftFunctionsBackgroundthreadQueue Thread 10 Crashed: 0 libsystem_kernel.dylib 0x1d85ed2d4 __pthread_kill + 8 1 libsystem_pthread.dylib 0x211ae059c pthread_kill + 268 2 libsystem_c.dylib 0x18ee21b08 abort + 128 3 libc++abi.dylib 0x211a065b8 abort_message + 132 4 libc++abi.dylib 0x2119f4bac demangling_terminate_handler() + 348 5 libobjc.A.dylib 0x1845632c4 _objc_terminate() + 156 6 libc++abi.dylib 0x211a0587c std::__terminate(void (*)()) + 16 7 libc++abi.dylib 0x211a05820 std::terminate() + 108 8 libdispatch.dylib 0x18ed67fbc _dispatch_client_callout + 40 9 libdispatch.dylib 0x18ed6f5cc _dispatch_lane_serial_drain + 768 10 libdispatch.dylib 0x18ed70124 _dispatch_lane_invoke + 380 11 libdispatch.dylib 0x18ed7b38c _dispatch_root_queue_drain_deferred_wlh + 288 12 libdispatch.dylib 0x18ed7abd8 _dispatch_workloop_worker_thread + 540 13 libsystem_pthread.dylib 0x211adb680 _pthread_wqthread + 288 14 libsystem_pthread.dylib 0x211ad9474 start_wqthread + 8 Thread 13 name: hades Thread 13: 0 libsystem_kernel.dylib 0x1d85e8090 __psynch_cvwait + 8 1 libsystem_pthread.dylib 0x211adbf98 _pthread_cond_wait + 1204 2 libc++.1.dylib 0x197843584 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28 3 hermes 0x104460f24 hermes::vm::HadesGC::Executor::worker() + 116 4 hermes 0x104460e8c void* std::__1::__thread_proxy[abi:v160006]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, hermes::vm::HadesGC::Executor::Executor()::'lambda'()>>(void*) + 44 5 libsystem_pthread.dylib 0x211ad97d0 _pthread_start + 136 6 libsystem_pthread.dylib 0x211ad9480 thread_start + 8 Thread 14: 0 libsystem_pthread.dylib 0x211ad946c start_wqthread + 0 Thread 10 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000211a0af3b x5: 0x000000016d49a800 x6: 0x000000000000006e x7: 0x0000000000000000 x8: 0x4782a95f5f805284 x9: 0x4782a95e32c9e284 x10: 0x0000000000000051 x11: 0x000000000000000b x12: 0x000000000000000b x13: 0x00000001874659ac x14: 0x00000000001ff800 x15: 0x00000000000007fb x16: 0x0000000000000148 x17: 0x000000016d49b000 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000006303 x21: 0x000000016d49b0e0 x22: 0x0000000000000000 x23: 0x0000000000000114 x24: 0x0000000301c3dc68 x25: 0x0000000000000000 x26: 0x000000016d49b0e0 x27: 0x00000003027721c0 x28: 0x0000000302771440 fp: 0x000000016d49a770 lr: 0x0000000211ae059c sp: 0x000000016d49a750 pc: 0x00000001d85ed2d4 cpsr: 0x40001000 far: 0x0000000000000000 esr: 0x56000080 Address size fault

Recently, we received a rejection for our app on the App Store under Guideline 4.1 - Design - Copycats. We strongly disagree with this decision, as we are confident in the uniqueness of our project. We have submitted an appeal regarding this rejection, but so far, we have not received any confirmation that it has been reviewed or accepted for reconsideration. The explanation provided for the rejection was vague, offering only general statements and references without specific details. This makes it challenging for us to understand which aspects of our app are causing concerns. Here’s what we’ve done so far to address the feedback: Changed the Original Name: We renamed our app to emphasize its uniqueness and avoid any potential associations with other franchises. Removed the Character from Screenshots: We deleted the image from our screenshots to prevent any misunderstandings and to highlight the originality of our visual content. Replaced the Icon: We completely redesigned the app icon, creating a new and unique design that reflects the original concept of our game. Updated Description and Other Metadata: We revised the app description and other metadata to better showcase the unique features of our game and eliminate any possible confusion. Despite these changes, our app was still rejected. Questions for the Community: How can we verify the status of our appeal? Has anyone had success in receiving confirmation that their appeal is being reviewed by Apple? What steps can we take if we don’t receive a response to our appeal? Should we try contacting Apple through alternative support channels, or is there another recommended approach? Any recommendations to improve our chances of approval? Perhaps we missed some details or there are ways to better highlight the uniqueness of our app to meet Apple’s guidelines.

Hello everyone, We submitted our app for review on December 30th, and it's still waiting for review. This delay is critical for our business as we have an important marketing campaign scheduled for tomorrow, and the app update is essential for its success. I read that App Store reviews might take longer during the holiday period (December 22–27), but we’re now well past that timeframe. Has anyone else experienced similar delays recently? We also submitted a request for an expedited review over 24 hours ago but haven’t received any updates yet. Any advice or shared experiences would be greatly appreciated! Thanks in advance for your help!

Hi there, I submitted my app for review a month ago, but I haven’t received any updates yet. Is this a typical timeline for Apple reviews? Are there any alternative communication channels with Apple, such as chat or phone calls, besides the review and support email, as these methods seem ineffective? Thanks for your assistance.

i already mention why i used location functionality but again show reject app... i dont understand what i do? i already attach screen short app rejection messages and show where i explain why i used location... and i dont use contact information permission in my app

Our problem is that our app was rejected for "Guideline 3.1.1 - Business - Payments - In-App Purchase". Specifically, "the app uses a promo code to unlock or enable paid features in store". Our app does use promo codes. But these codes do not directly unlock paid functionality. What our app actually does with promo codes is as follows... We have products with ids "Product1" and "Product1_Discount1". These are both valid product definitions in Apple IAP. They enable the same features within the app but have different price definitions. We allow the user to enter an optional promo code. We consult our backend to see if the promo code allows the user the opportunity to purchase "Product1_Discount1", and if it does we display the info defined by "Product1_Discount1", otherwise, we display the info defined by "Product1". We are trying to understand a) is it always going to be a guideline violation to offer our own promo codes for in-app purchases (these are not Apple generated codes, we generate them)?, or b) is there a scenario where it is acceptable to manage our own promo codes for in-app purchases? We didn't see anything in the guidelines that prohibited us to define multiple IAP products that have different prices but enable the same functionality. Is this allowed? Our business goal is to share revenue of purchases that our partners promote which we track using their designated promo codes. Is our approach a definite guideline violation? If so then what is the recommendation to achieve our business goal? Thanks

Hey All, I would appreciate suggestions on how to resolve this problem as this is my first time publishing app on iOS store. So, I made a party game which simulates a user urinating into ****** and you have shoot some targets in ****** by controlling motion sensor. During testing on test flight no problem was shown but during official rollout, App store review says it's to remove the content which is basically the whole gameplay. I submitted a reply clarifying everything but it seems they have an automated response which was same as previous one. On the other hand, there's a similar game on app store with somewhat same idea. Can someone please guide me how to approach this problem. My game is published on Android without any problem but here.

Hi all, My app was rejected because of Guideline 4.3(a). Below is the response: 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. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third-party Submitting several similar apps across multiple accounts Is due to another Beta Build of the same app that is also under App Review currently? Because the app idea, UI, code, everything is ideated by me without any inspiration

I had tens of updates with no problems and my review times have always been less than 48 hours and 95% of the times even less than a couple of hours. Unfortunately I have a critical update now that seems to got stuck for days now. The update is critical, because it contains a Wrapped 2024 functionality for our users, and the longer it takes the less relevant it becomes. Anybody else experiencing this? Can it have to do with the fact that i removed my update from review and submitted another one? I removed it from review on 31 Dec and submitted a new one on 31 dec. I guess the review time start counting again when you resubmit, but I'm afraid this resubmission (that we normally dont do) might be the reason of the app getting stuck.

I got this below rejection. I was asking why and which aspects of mine was a spam/similarity to which app, but they told me that they can't give a review for my app. I don't know how to resolve this, because I think I did this app done by myself and copying nothing from outside. Can anyone help me? Thank you so much. Hello, The issues we previously identified still need your attention. Review Environment Submission ID: cb12182d-504f-4c1f-851b-1595820da7ec Review date: January 03, 2025 Version reviewed: 1.0.2 Guideline 4.3(a) - Design - Spam We continued to notice your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality.

Hi everyone, I'm desperate, they keep rejecting my app application, I don't know what to do anymore. My app was accepted to be among the "unlisted" ones, but the verification team keeps rejecting the app telling me to apply as an "unlisted" app. I even replied to them so many times writing that the request was approved as unlisted, I pasted the text of the approval email and attached it, but nothing they keep rejecting it.

Since we incorporated Apple Pay they have been rejecting the version, in the last review they mentioned to me that there were missing Terms of Use and Privacy Policy links which we already added in a previous review but they continue to mention it to us, they also mentioned the functionality to delete an account, which also already exists even from the first version, I explained this in App Review including images of the screens where this was already there, which they mention is missing, unfortunately I have not had a response since January 3

Hello All, My company has a Flutter application that has a signup process where we collect information like the user's name, address, etc. This data is not sold to advertisers or shared with any third parties, just used for functionality available in the application. (It's an FSM where contractors can operate there business). The app has been rejected twice now for not having the prompt and app tracking transparency framework in it. We adjusted the policy to indicate we don't collect private information and share it, but still got rejected for it. Does anyone have any clarity on if we need it in this scenario?

Hello everyone, I am seeking advice regarding a recurring issue with our app, "YouMi UM," which was rejected due to alleged spam under App Review Guideline 4.3(a). The review team stated that our app shares a similar binary, metadata, and/or concept with apps previously submitted by a terminated Apple Developer Program account. Our app, "YouMi UM," has been successfully launched on the Android platform, and we have invested significant effort into its UI design and features. However, when submitting to Apple, the review team pointed out similarities between our app and others submitted by different developers, particularly in terms of binary files, metadata, and concept, which led them to believe it might violate Guideline 4.3. Our app is independently developed, with all code and design being original. We have also added several unique features, such as real-time news widgets, branded dynamic toast notifications, and exclusive scene transition animations, which are not commonly found in similar apps. We believe these innovations significantly enhance the user experience and give our app uniqueness in the market. Despite these adjustments, the review team still indicated that our app shares similarities with certain apps previously submitted, which they believe could affect the user discovery experience and lead to redundant content. We believe this is a misunderstanding, as our app is neither repackaged nor similar to any previously submitted apps. Our app has already been released on the Android platform, and given this situation, we cannot make major adjustments to the UI or features. We would greatly appreciate any valuable advice from fellow developers in the community to help us navigate this challenge and successfully pass the review.

Hi everyone,  We’ve been trying to submit our app to the App Store for quite some time now, but we’ve encountered multiple rejections despite addressing all the feedback we’ve received. Initially, we resolved a few issues, but there is one recurring problem that continues to block us.  Every time, the review team reports an issue with the “Sign in with Apple” feature, specifically stating: “App did not produce further action when we tapped on Sign in with Apple.”  However, we’ve tested the feature on multiple devices, including iPads and iPhones, targeting all iOS versions from 17 and above. The login process works flawlessly in all our tests. We’ve ensured that we are following Apple’s best practices and have meticulously reviewed our implementation numerous times and also reviewed with another team which implemented it the same way and did got approved.  It’s becoming frustrating as the issue appears to be on the review side. We’ve even uploaded videos demonstrating various scenarios, yet we still receive no detailed feedback. Each review cycle takes about 24 hours, which is significantly delaying our iOS launch.  Has anyone experienced a similar situation, where a working feature consistently fails during App Store review? If so, how did you resolve it? We’re quite behind schedule and would appreciate any advice.   The app is made with Xcode 16.  Thank You!  ------- This is the reviewer notes -------  Guideline 2.1 - Performance - App Completeness Issue Description   The app still exhibited one or more bugs that would negatively impact App Store users.   Bug description: App did not produce further action when we tapped on Sign in with Apple.   Review device details:   Device type: iPad Air (5th generation)  OS version: iPadOS 18.2  Next Steps   Test the app on supported devices to identify and resolve bugs and stability issues before submitting for review.   If the bug cannot be reproduced, try the following:   For new apps, uninstall all previous versions of the app from a device, then install and follow the steps to reproduce.  For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.

Hi I uploaded an app in apple account but app getting rejected with The status of your app has changed to Invalid Binary. I am using Xcode 15.3. I am not getting specific problem. I am getting same message as invalid binary.

Received the following rejection message following submission: We noticed an issue in your app that contributes to a lower-quality user experience than App Store users expect: Your app included hard to read type or typography. Screenshots were supplied showing everything faded on screens apart from icons, tabs, and the navigation bar. Seeing clear everything on local simulators and a real device. Does anyone know what the problem is? The app was developed with React Native.