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

Hi Apple Developer Support, We're currently implementing auto-renewable subscriptions in a React Native app using the react-native-iap library. The subscription purchases are working as expected in Sandbox. We receive the transaction and purchaseUpdatedListener gives us a valid-looking transactionReceipt However, when we attempt to validate this receipt with Apple's servers, the response consistently returns status code 21002, indicating that the receipt data is either malformed or missing. We’ve confirmed the receipt is well-formed, properly passed as received, and well above the minimum size expected. The shared secret is correctly configured and matches the subscription group. We're using the correct sandbox endpoint and ensuring no modification is done to the receipt before validation. Despite this, validation fails every time. We are looking for guidance or clarification on what might cause this status, especially when the receipt is coming directly from the system after a successful test purchase. const purchaseUpdateSub = purchaseUpdatedListener(async (purchase) => { console.log("🛒 Purchase Updated:", purchase); const receipt = purchase.transactionReceipt; if (!receipt) { Alert.alert("Error", "No receipt found."); setLoading(false); return; } }); the response is: { "status": 21002 } Any guidance on why this might be happening would be appreciated. Thanks!

Hello everyone The in-app subscription / purchase aren't loading in the version of my app that I'm submitting onto App Store Connect. Locally, I use StoreKit config to test/develop my app. I already have my subscription groups and legal stuff set up properly. However, when I goto my subscription group, a blue notice says 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 But when I goto Appstore Connect -> Apps -> the app I'm working on -> iOS -> Version 1.0 Prepare for Submission, I can't find any section regarding "In-App Purchases and Subscriptions". I also can't find it after going into the build by clicking on the build number(there's only Test Information and Build Metadata)

I am currently developing a feature to support global privacy compliance, which relies on accurately obtaining the user’s App Store country/region. Based on this country/region information, out App dynamically display privacy policies that comply with local regulations. To retrieve this information, I use the relevant StoreKit APIs. API usage examples: Objective-C: NSString *countryCode = [SKPaymentQueue defaultQueue].storefront.countryCode; Swift let storefront = await Storefront.current let code = storefront?.countryCode However, during sandbox account testing on iOS 18.0 and above, I noticed that the returned country code does not match the actual country/region configured in the sandbox Apple ID. This issue does not occur on systems below iOS 18.0, where the country code returned by the API matches the account setting. Since this discrepancy can directly affect the accuracy of our compliance logic, I would appreciate your clarification on the following points: Is this a known change in behavior for iOS 18? In production environments, does the country code returned by the above APIs accurately reflect the App Store region of the user’s signed-in Apple ID? Is there a recommended approach to reliably obtain the user’s App Store account country/region?

My app keeps getting rejected by Apple Review team. This is their reason: The app still exhibited one or more bugs that would negatively impact users. Bug description: your app was unresponsive to scan provided code or barcode on website before we purchased the subscription. Review device details: - Device type: iPhone 13 mini and iPad Air (5th generation) - OS version: iOS 18.5 and iPadOS 18.5 We have tried our own devices but it works fine for us. We aren't able to reproduce the issue. What should we do?

Hello community, I'm facing a very frustrating issue for several days with successive rejections for the same guideline 3.1.2 regarding Terms of Use, despite my efforts to comply with the requirements. The problem: Apple keeps rejecting my app saying: "The app's metadata is missing the following required information: A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App Description." What I have already implemented: In the application: "Terms of Use Apple" links present on ALL purchase pages (signup, premium, boosters, settings) Functional link: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/ Complete subscription information (duration, price, features) In App Store description: Dedicated line: "Terms of Use: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/" In App Store Connect: "Privacy Policy" field filled Description updated with links My frustration: I feel like it's a bot responding to me because I receive exactly the same message every time, without taking into account my detailed explanations and evidence that I have everything in place. I'm even trying to add elements that aren't necessary out of desperation, but nothing seems to work. Questions: Has anyone else encountered this problem recently? Is there something specific I'm missing? Does the exact format of the link in the description matter? I'm really desperate after several rejections for the same reason. Any help or advice would be greatly appreciated! Thanks in advance for your help.

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.

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.

4.2.2 Other than catalogs, apps shouldn’t primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links. I cannot understand why app is rejected. The app collects 1000 grocery store offers a week from 250 papers using AI. Users vote on best offers and keep updated with notifications for their own personal products. Images of my app and original pages it is reading from. the most frustrating thing is that the only other app trying to solve the same problem just displays theres papers statically like a website with absolutely no functionality. Their app is a copy of the website: https://mattilbud.no Features of app: Favorite offers, contributing to a global and local vote system. Saved searches with notifications when new matching offers appear. Search by product name or category, with filtering by store. Adjustable grid layout for homepage offers. Home Screen Quick Actions for saved searches. Option to view the original grocery page. Native Share Sheet integration for sharing offers. Haptic feedback on key interactions. Dark/Lightmode based on ios appearance settings.

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.

It’s now day 7 with no communication since we addressed the login issue your team flagged—an issue that prevented the reviewer from accessing the app. That fix was submitted promptly and the app has been in review since, but we've had no updates. This follows a two-week wait just to receive that initial feedback. Our launch was planned for the first week of June, and the continued delays with no communication are putting our timeline and business plans at risk. We’ve already requested an expedited review and made sure all required information is in place. This is really sad even after submitting every necessities and information requested

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

I don't have any other games on the app store, so no duplicate bundle IDs. All the code was written by myself. I developed a game where you play as as 1 of 4 Healing classes healing a party of 4 adventurers, with a big talent tree system where you can learn additional healing skills. Various boss fights that test your builds in various ways. I don't feel this design area is saturated, there aren't many games where you play a healer rather than a damage dealer. I've been working on and off on this game for 4 years, it's not a clone app or anything like that. I'm not sure how to proceed, because they didn't elaborate on exactly what rule I am violating.

Title: App Rejected (4.3.0 Design Spam) Hi everyone, I need help understanding why my app was rejected with the reason 4.3.0 Design Spam. The explanation from Apple was very generic, and it doesn't really help me figure out how to resolve the issue. It’s a puzzle game we’ve been working on for about 3 years, with completely hand-drawn graphics and 250 manually designed levels created using a custom editor built specifically for Mac. We haven’t used any automatically generated assets or recycled content from other apps. This is an Alpha version but fully playable—we’re using it to test retention and gameplay, not monetization. We’ve already tried contacting Apple’s support team, but we haven’t received any response so far. The same thing happened about a month ago with a penalty kick game we developed using SpriteKit specifically for Apple Watch. That game was also rejected with the same reason, and again, we weren’t able to understand why or get in touch with support for clarification. In that case, I wondered if the problem was either the simplicity of the game (even though it was fully coded from scratch and had hand-drawn graphics by our designer), or because that game was initially uploaded by an external freelancer to his account for testing purposes on TestFlight (but he never actually published the app). Has anyone experienced something similar or has any advice on how to clarify this situation with Apple? Is it possible to request a more detailed review or get in touch with someone at Apple to understand where the real issue might be? Thanks so much to anyone who can help me out!

Our team is migrating from Apple Server Notifications V1 to V2. We have two primary questions regarding notification delivery during this transition: Is it possible to configure Apple to send V1 notifications to an existing V1 endpoint URL and V2 notifications to a separate V2 endpoint URL concurrently? If concurrent delivery to distinct URLs is not supported, what is the expected behavior for outstanding/pending V1 notifications when the notification endpoint URL is updated to the V2 URL? Are V1 notifications re-sent to the new V2 URL, or are they dropped?

When adding a phone number in the contact information for submitting an app for external use, it doesn’t let me proceed. It says the number is invalid and that I should ensure it contains only numbers, but it still won’t let me continue. I need help with the external use configuration.

Tying to enroll since last 2 weeks, we tried making payment but it doesnt go through.