Hello everyone, I'm seeking some advice and perspective from the community regarding an appeal I've submitted to the App Review Board. My app, (App ID: 6748638280), was recently rejected under Guideline 4.3 - Spam. We believe this was a misunderstanding, as our app is a highly specialized academic tool for the study of Qimen Dunjia (奇門遁甲), a complex form of ancient Chinese metaphysics. It is a professional calculation engine, not a generic fortune-telling app. We submitted a detailed appeal to the App Review Board two weeks ago, explaining the unique, academic nature of our app and providing a link to a demo video that showcases its innovative features (like its real-world compass integration and its unique data visualization system). As of today, we have not yet received a response. I completely understand that the review process takes time, and I want to be respectful of the board's workload. However, I'm starting to wonder if this length of time without a reply is normal for an appeal. I would be very grateful to hear from any other developers who have gone through the appeal process: Is a wait of two weeks (or longer) for a reply from the App Review Board a common experience? Is there any further action you would recommend at this stage, or is the best course of action simply to continue to wait patiently? Thank you in advance for sharing your experience and any advice you might have. It is greatly appreciated.

My app has been approved and all of my subscriptions have been approved, but my subscription localization is still showinig Waiting for Review. Going on almost 2 days now since the subscriptions and app have been approved. I see no communication or anything on this. Is this seprate of those? How long does this take?

I need apple recommended approaches & validate our approach if apple has any concern for the below design. I am very new to the Apple deployment team. I have gone through online docs & articles. Currently our app is live on the app store We want to release a new version by the end of this year. This release is a major upgrade to the existing app. It contains a complete revamp of the UI. Lot of new features are added. Older version will be supported for a couple of years. Process I want to recommend to the company is. Older version of the app works for a couple of years until all the users are upgraded to the new release. New release for testflight(Internal/External), will go with "New bundle Id" & "New Name". Test the new release thoroughly in the beta phase. Revert the temporary bundleid & name to the original bundle id & name. Release to testflight. Release to app store.

Recently I got an email stating I need to update age rating questionnaire. I have tried to update age rating for my app in App Store using the account owner already. I have followed this tutorial (https://developer.apple.com/help/app-store-connect/manage-app-information/set-an-app-age-rating/), but the age rating cannot be updated. Anyone know how to update this, please let me know

Hello, My app Native Talk! has been "waiting for review" for +24 hours. I want to know if this hold up is because of something I need to do on my end or if this is normal. Thank you! Matt

Hello, I’m encountering a consistent HTTP 400 – Bad Request error when attempting to retrieve daily sales reports via the App Store Connect API. The request format follows the official documentation: https://developer.apple.com/documentation/appstoreconnectapi/get-v1-salesreports. Here is an example of the request I’m making: curl --location --globoff \ ' https://api.appstoreconnect.apple.com/v1/salesReports?filter[frequency]=DAILY&filter[vendorNumber]=<REDACTED VENDOR NUMBER>&filter[reportDate]=2025-08-11&filter[reportType]=SALES&filter[reportSubType]=SUMMARY' \ --header 'Authorization: Bearer <REDACTED_JWT>' This request worked without issues until August 6, 2025 (Obviously using the previous day date), but from August 7 onward it returns a 400 error. Could you please confirm: Whether there have been any changes to the required query parameters (e.g., filter[version]). If there are any known issues with the SALES / SUMMARY / DAILY endpoint. Aside from the images attached, our buffer error also shows: new Uint8Array([60, 33, 100, 111, 99, 116, 121, 112, 101, 32, 104, 116, 109, 108, 62, 60, 104, 116, 109, 108, 32, 108, 97, 110, 103, 61, 34, 101, 110, 34, 62, 60, 104, 101, 97, 100, 62, 60, 116, 105, 116, 108, 101, 62, 72, 84, 84, 80, 32, 83, 116, 97, 116, 117, 115, 32, 52, 48, 48, 32, 226, 128, 147, 32, 66, 97, 100, 32, 82, 101, 113, 117, 101, 115, 116, 60, 47, 116, 105, 116, 108, 101, 62, 60, 115, 116, 121, 108, 101, 32, 116, 121, 112, 101, 61, 34, 116, 101, 120, 116, 47, 99, 115, 115, 34, 62, 98, 111, 100, 121, 32, 123, 102, 111, 110, 116, 45, 102, 97, 109, 105, 108, 121, 58, 84, 97, 104, 111, 109, 97, 44, 65, 114, 105, 97, 108, 44, 115, 97, 110, 115, 45, 115, 101, 114, 105, 102, 59, 125, 32, 104, 49, 44, 32, 104, 50, 44, 32, 104, 51, 44, 32, 98, 32, 123, 99, 111, 108, 111, 114, 58, 119, 104, 105, 116, 101, 59, 98, 97, 99, 107, 103, 114, 111, 117, 110, 100, 45, 99, 111, 108, 111, 114, 58, 35, 53, 50, 53, 68, 55, 54, 59, 125, 32, 104, 49, 32, 123, 102, 111, 110, 116, 45, 115, 105, 122, 101, 58, 50, 50, 112, 120, 59, 125, 32, 104, 50, 32, 123, 102, 111, 110, 116, 45, 115, 105, 122, 101, 58, 49, 54, 112, 120, 59, 125, 32, 104, 51, 32, 123, 102, 111, 110, 116, 45, 115, 105, 122, 101, 58, 49, 52, 112, 120, 59, 125, 32, 112, 32, 123, 102, 111, 110, 116, 45, 115, 105, 122, 101, 58, 49, 50, 112, 120, 59, 125, 32, 97, 32, 123, 99, 111, 108, 111, 114, 58, 98, 108, 97, 99, 107, 59, 125, 32, 46, 108, 105, 110, 101, 32, 123, 104, 101, 105, 103, 104, 116, 58, 49, 112, 120, 59, 98, 97, 99, 107, 103, 114, 111, 117, 110, 100, 45, 99, 111, 108, 111, 114, 58, 35, 53, 50, 53, 68, 55, 54, 59, 98, 111, 114, 100, 101, 114, 58, 110, 111, 110, 101, 59, 125, 60, 47, 115, 116, 121, 108, 101, 62, 60, 47, 104, 101, 97, 100, 62, 60, 98, 111, 100, 121, 62, 60, 104, 49, 62, 72, 84, 84, 80, 32, 83, 116, 97, 116, 117, 115, 32, 52, 48, 48, 32, 226, 128, 147, 32, 66, 97, 100, 32, 82, 101, 113, 117, 101, 115, 116, 60, 47, 104, 49, 62, 60, 47, 98, 111, 100, 121, 62, 60, 47, 104, 116, 109, 108, 62]) Thank you for your assistance.

Hi, I want to consult about this: This is regarding [Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage] My client is asking if we can remove the new account registration through the iOS App, so we won't need to ask for mobile and birthdate. For iOS App users, new users will register through the website (or through a non-Apple related app). After registering through the website, they can access the iOS App using the credentials created through another method. Will that be a problem with Apple policies? My client said they need the Mobile number and birthdate for verification. Thanks in advance for the help and guidance. Best regards, Sophia

Hi, we are trying to move an existing application to a Web based SPA architecture with majority of the screens written in JS opening in a webview and using native bridges for the Hardware components. Before proceeding ahead, we just wanted to be sure that these kinds of applications are generally approved by Apple or not. If not, what are the guidelines to be followed if one wants to create an SPA application for iOS. PS: The content that will be served in web view would be controlled and hosted within the organisation domain and whitelisted for the mobile app only.

IPad 15.6 searched for the ‘北辰遴选’ app on the App Store, but there was no response when clicking to download it. Today, 5 users have reported that they cannot download it after restarting the device or changing the network. May I ask how to solve this?

Hello Apple Review Team, We truly appreciate your hard work, but our app has been stuck in “Waiting for Review” status for almost a month with no updates. During this time, we have: Sent emails explaining our situation Submitted expedited review requests Uploaded new builds to refresh the status However, we still haven’t received any response. Could you please let us know if there is any specific issue with our app, or help escalate our review manually? Our App id: 6744839843 Thank you for your attention and support.

https://testflight.apple.com/join/3WFJJ4YQ

Hi I'm not a overly technical person, and our app developer is currently on leave so trying to figure this out. Our app was grandfathered a few years ago, but it's time to finally stop all uses having access to the app due to back end changes. Is the only way to do this to Remove the app from App Connect? What will the end user see? Do they just get a note saying the app is no longer functional?

Our app generally gets reviews within 24 hours. I understand there could be delay of a day or two. But this time it has been around 4 days. What could be the reasons?

Hi all - I used to run a development studio, but shut down around ~8 years ago. Since then, I've kept a personal $99/year Individual developer account to access documentation, apps, etc, as I still work in the mobile iOS development space, just for corporate projects. I have a friend who has an app that was built years back, but was removed from the store ~2-3 years ago due to just letting account lapse. He's asked me to help him get it back on the App Store, with some updates, etc. His account is an Individuals or sole proprietors/single-person businesses account as well. He granted me Admin access on his account, but I can't see or select his team in Xcode when handling automatic code signing in order to upload to App Store Connect. He's not a developer, and he lives several states/hours away. We worked remotely and I was able to get a development certificate and provisioning profile that I walked through setting up with him, that he exported and sent over to me. However, when I compile a build this way, Xcode won't allow upload because I am not logged in to his developer account. Outside of him giving me his personal account password, which isn't advisable and I would be reluctant to ask him for, is there a way I can submit this app for him up to App Store Connect?

Hey guys, A quick question. I use my personal phone as a two factor auth which I use to login to my personal account. Is it possible to have this same phone to receive the two factor auth code when I log in using my company email?

<SKPaymentQueue: 0x283da58d0>: Payment completed with error: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={client-environment-type=Sandbox, storefront-country-code=IND, NSUnderlyingError=0x28310f6c0 {Error Domain=AMSErrorDomain Code=305 "Purchase Failed" UserInfo={NSLocalizedDescription=Purchase Failed, AMSURL=https://sandbox.itunes.apple.com/WebObjects/MZBuy.woa/wa/inAppBuy?guid=f7d7d15046ee6db6d61ef721b924773fa7d9347d, AMSStatusCode=200, AMSServerPayload={ "cancel-purchase-batch" = 1; customerMessage = "Unable to process your request."; dialog = { defaultButton = ok; explanation = "Please try again later."; initialCheckboxValue = 1; isFree = 1; "m-allowed" = 0; message = "Unable to process your request."; okButtonString = OK; }; failureType = ""; "m-allowed" = 0; metrics = { actionUrl = "sandbox.itunes.apple.com/WebObjects/MZBuy.woa/wa/inAppBuy"; asnState = 0; dialogId = "MZCommerce.SystemError"; I am getting this error code who all are added via beta test link and internal tester who all are added after the beta link has been created but IAP working one who all are before in internal testers as beofre the link has been created

Hello. I was working on a Unity game for iPhone, but Apple said that it is impossible to prohibit downloading to iPad. They tested it on iPad Air 5, and for some reason the game did not work correctly - nothing happened when launched, although everything was fine in the simulator and in the real iPhone. Please tell me what to do?

Greetings, I am facing the following issue. I always get that the app was rejected for no obvious reason. I also notice the message Invalid Binary at the app version. I am on MacOs 14.7.6, Xcode 16.0. I have validated the app using the xcode archive and I got that everything is valid, and the app gets uploaded to app store connect with no issue, but once I submit the app for review I get those errors and the release gets rejected. Any help ? error message Your app version was rejected and no other items submitted can be accepted or approved. You can make edits to your app version below.

We run an analytics query every day; this worked fine for the past 6 years or so. Two days ago this query has stopped working. It always returns a non-descript 400 Bad Request. Here's the exact query: curl \ -H 'Accept: application/a-gzip' \ -H 'Authorization: Bearer <TOKEN>' \ 'https://api.appstoreconnect.apple.com/v1/salesReports?filter[frequency]=DAILY&filter[reportType]=SALES&filter[reportSubType]=SUMMARY&filter[version]=1_0&filter[vendorNumber]=<VENDOR>' And the response: <!doctype html><html lang="en"><head><title>HTTP Status 400 – Bad Request</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 – Bad Request</h1></body></html> I have confirmed that the <TOKEN> is correct (with an incorrect token I get a specific error message). Same with missing or incorrect filter parameters: the API returns an exact error message. I have also confirmed that our vendor number is correct (from AppstoreConnect › Payments and Financial Reports, top left corner), though specifying an invalid vendor number yields the same non-descript 400 Bad Request. With seemingly valid filter parameters, (no matter the report type or frequency or specifying a date) I always get the generic 400 Bad Request. Has something changed in the API?

App Store Connect's privacy label system creates impossible review situations by checking live app versions instead of submitted builds. Problem: Developer has a live app with tracking on the App Store Developer create a new app version with all tracking removed Privacy labels from AppStore Connect cannot be updated because system references live version with tracking App gets rejected for privacy label mismatch with submitted build Cannot fix labels until approved, cannot get approved with wrong labels Expected behavior: Privacy label system should allow updates for pending app versions or check submitted build instead of live version. Steps to reproduce: Submit app update with tracking removed Try to update privacy labels to "no tracking" from AppStore Connect System shows error: "Your app contains NSUserTrackingUsageDescription, indicating that you will request permission to track users. You must indicate which data types are tracking users. If this is incorrect, update your app binary and upload a new build to App Store Connect." App gets rejected despite submitted build having no tracking This affects any developer trying to remove tracking functionality from AppStore Connect in such a scenario. I have opened a bug in Feedback Assistant: FB19459680