I’m trying to submit my app for review, but I’m currently blocked due to a recurring issue with in-app subscriptions. Both of my auto-renewable subscriptions (premium_monthly and premium_yearly) are marked as “Waiting for Review”. However, I am still seeing the blue box stating that “your first subscription must be submitted with a new app version.” Despite creating a new version (1.0.1) and uploading/selecting a new build , I am not seeing the “In-App Purchases and Subscriptions” section on the version page, and I therefore cannot link the subscriptions before submitting. This issue is blocking my ability to submit the app for review. Any help to resolve this would be greatly appreciated.

My app has been stuck 'in review' for 72+ hours. The last thing i got from the App Review team was an email saying "One or more In-App Purchases has been returned." This was the second time i've gotten this email. I feel like the people reviewing my app stops after testing my paywall and doesn't proceed with reviewing the rest of the app. Previously, i had an issue (which has been since solved) with the app review team even reviewing my app at all (waited over 9+ days). I submitted the app for review on a Friday and it's Monday now. I'm not sure if they stop reviewing apps over the weekend. But any help to solve the issue would help

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 all, One of my app submission got rejected saying deletion feature wasnt available. We allow de-activate our user accounts after our customer support representative speaks with customer to confirm and then delete the account. But while submitting our app for release we got this message?? The app only offers to deactivate the account. Temporarily deactivating accounts is not sufficient to meet the account deletion requirement. Any help how to overcome this issue pls? Thanks K

Hello we just submitted our app one week ago. First submission was rejected and we have resubmitted it after resolving issues with it. but it has been more than 5 days. And we still haven't got any feedback from apple team. We need to publish the app ASAP. Thanks in advance for your help. Looking forward to hearing back from you.

Hello, Can anyone help me with the below? I've been sent the below bolded, italicized message three time in a row now with no further explanation. _**Please note that links are required to be included in both of the metadata and the binary. We noticed that your app binary is still missing: A functional link to your privacy policy A functional link to your Terms of Use This information is required for apps which include auto-renewable subscriptions.**_ My reviewer initially instructed me to include my terms of use link in my app description (as my privacy policy was already displayed). I followed that instruction and that subsequently started the persistence of the bolded, italicized message. For full context, the links are in my app description and on my paywall inside of the app itself. I need help and clarity on what I'm missing so I can get the app approved. Also, if anyone knows any alternative ways of allowing users to purchase a subscription within the app that Apple allows - I would appreciate that information, as it seems this process is too complicated for me.

My app uses Apple IAP. With the recent US external payment changes (May 2025), I plan to use Stripe via Superwall. Superwall allows me to remotely toggle my paywall for US users between Apple IAP and Stripe checkout without a new app build. Is it permissible to activate Stripe for new US users on an already live app version (approved with only Apple IAP) without first submitting a new build for Apple to review the Stripe integration? Or does this dynamic switch create a risk of takedown/compliance problems? Concerned about new users hitting an unreviewed Stripe flow during any potential review period for a new build. Seeking clarity on Apple's stance or community experiences. Thanks!

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).

My application has been in "In Review" status since May 30, 2025, and it is still in that status today. Please check the status of my app, LS Tools. Our customers are waiting for the latest version

I am planning to gradually phase out the app and make it unavailable for new users. However, we would like to ensure that users who have already installed the app can continue to receive updates and support during this transition period. Please advise if this is possible? If so, what are the necessary steps or settings we need to configure in the App Store Console to achieve this? In addition, I would appreciate your guidance on the following questions: What is the process for uploading or releasing an update for an app that is currently "Removed from Sale"? If an app is "Removed from Sale", can it be republished later? What are the steps to do that? Are there any limitations when changing the app’s distribution region (e.g., is there a maximum number of times the region can be changed)? Thank you.

Hello, our submission rejected by the apple team and now we can't remove cancel the current submission. This is api response when we attempt remove: { "errors" : [ { "id" : "e069078e-4c57-4aa6-ab3b-913ddf9e6314", "status" : "409", "code" : "STATE_ERROR.ENTITY_STATE_INVALID", "title" : "Resource state is invalid.", "detail" : "Resource cannot be canceled at the moment, please try again later" } ] } We need to publish app asap and can't do anything because of this bug.

My app was accepted onto the app store yesterday, but i just found out that my subscriptions were rejected for some reason. The localization of each subscription said there was something wrong with it so i changed them and resubmitted them. The issue/question that i have is that now that my app has been accepted with my 1.0.0 version, do i have to submit an update for them to review my subscriptions? or do they review the subscriptions separately because you have to submit the subscriptions for review, the same way you have to submit builds. I just don't want to be waiting around because i can't market my app without those subscriptions accepted

Looking for a solution: our app name is read more clearly when it is lower-case. We have submitted it to the store in that format, and it shows up on the App Store that way, but when it is sent to the devices, it changes to upper case. I am not seeing results on why this is happening or how to change it. The app name is 1on1 Piano, and when it is downloaded on the device, it changes to 1ON1 Piano, which people often mistake for "ioni piano" and "10 and 1 piano," so we would like it to be consistent with our branding where "on" is lowercase.

Hello, my app was rejected with this reason - Guideline 2.1 - Performance - App Completeness. Bug description: Sign in with Apple requests the Apple ID password rather than entering a code. The issue is that I'm using Clerk inside Expo and they don't support native Apple signIn, only web based. But when users open signIn for the first time - they need to login for appleId via web. I already submitted rejection appeal with explanation. Did someone encounter similar problems? The flow works correctly. In fact even apple testers went through and created accounts.

I am stuck. Apple asked me to modify the Name/Description of one of my Subscriptions. But the subscription is "In Review" and everything (including the save button) is disabled. It's lierally impossible for me to update the Name/Description like they are asking for. I have tried rejecting my submission but they are still locked. I have asked Apple Review for help - like changing the status so that I can edit them but they won't. I can't get out of review until I modify the Name/Description of a Subscription but I can't update the Name/Description of a Subscription until I'm out of review. HELP!! 😭

Hello, I submitted my mobile game to the App Store with in-app purchase items. I initially sent my in-app purchases for review for the first time. I had fixed a bug before and thought I could submit a new build with the fix. (Before too much time has passed)I withdrew the previous build and re-submitted the new one. Now, I cannot select in-app purchase items in the new build, and the in-app purchases are still in “Waiting for Review.” Did they get stuck? It has been one day. Even if the in-app purchases get approved, I am unable to choose them in the new build.

Hi, I have submitted my app for review since 05/06/2025. Today is 09/06 it still in Waiting for Review status. Please help me look into this issue. We need to release it ASAP AppName: 小马AI学 AppleID: 6745546153 Thank you

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?

in review for long time Apple ID: 6742814997

We submitted our app for Review on June 3. The submission was put in "In Review" status on the same day. Today is June 10 and we did not receive any status update. Our customers are waiting for the release of our app. This is delaying our promised release date. Can someone review our app?