Hello, I’m posting here to ask for guidance and to see if anyone has experienced a similar situation. More than 30 days ago, I submitted an appeal to the App Review Board after receiving a Pending Termination Notice for my Apple Developer Program account. However, I have not received any response or update since submitting the appeal. In the notice, Apple mentioned that my account was associated with “dishonest or fraudulent activity” related to app submissions. I want to clarify that I did not intentionally attempt to bypass the App Review process. The only change I made around that time was editing some app metadata (subtitle keywords) while trying to optimize my Apple Search Ads campaign. Looking back, I now understand that some of those keywords may have been interpreted as referencing content that Apple considers inappropriate for the App Store. After realizing this might have caused an issue, I immediately: Canceled the latest app submission that contained those metadata changes Explained the situation clearly in my appeal to the App Review Board Confirmed that I would avoid using similar metadata in the future Despite providing this explanation in my appeal, I have not received any reply or update for over a month, so I’m unsure about the current status of the appeal. If anyone here has gone through a similar process, could you share: How long it took to receive a response from the App Review Board? Whether it’s normal for appeals to take this long? Also, if any Apple staff happens to see this post, I would sincerely appreciate any guidance on whether my appeal is still under review or if there is anything further I should provide. Thank you very much for your time and help.

I accidentally clicked on tvOS instead of iOS for a new build. So now I have a "tvOS Prepare for Submission" item in the left panel of iTunes Connect. I have no plans to make a tvOS version, so is there any way to remove that?

Hello App Review team and iOS developer community, I submitted an updated version of my app on App Store Connect on February 5, 2026, and it entered the review process on February 7, 2026. However, I do not understand why, as of today (March 8, 2026), its status is still "In Review." I have already contacted Developer Support on February 27, 2026 but have only received the following automated reply: “Thanks for submitting your support request. We’ve received your support request and will get back to you as soon as possible.” More than a month has passed, and I still haven’t received any official follow-up or updates from Apple regarding this issue My case ID : 102831527320 Apple ID : 1628986976 I would greatly appreciate your help in reviewing and approving this update as soon as possible, as the delay is affecting many users. Thank you for your support.

We are trying to upload the first Apple-hosted Managed Background Assets pack for our macOS app, but Transporter rejects the asset pack ID during upload. App details: App name: DistillApp Apple ID: 6760288806 Bundle ID: cn.rkbkosp.DistillApp Asset pack ID: distill.pipeline.zh-baseline Platform: macOS Transporter: 1.4 Xcode: 26.2 macOS: 26.3.1 What we see in Transporter: Apple ID: 6760288806 App Name: DistillApp App Bundle ID: cn.rkbkosp.DistillApp No background assets found. And when we try to upload the first asset pack, Transporter fails with: 获取 Apple ID “6760288806”的资源包列表失败。 (-19243) There is an error with a URL parameter (400) Found invalid values: distill.pipeline.zh-baseline What we have already confirmed locally: The app resolves correctly in Transporter, so the Apple ID and bundle ID appear to be correct. The app Info.plist includes: BAHasManagedAssetPacks = YES BAUsesAppleHosting = YES BAAppGroupID = 8U6DAJ62JT.group.cn.rkbkosp.DistillApp.assets The asset pack manifest uses: assetPackID = distill.pipeline.zh-baseline This is intended to be the first Apple-hosted background asset pack for the app. Our understanding is that No background assets found is expected before the first successful upload, so the actual problem seems to be that Transporter/App Store Connect refuses to accept the initial asset pack ID. Questions: Has anyone seen Transporter reject the first Apple-hosted background asset pack for an app with -19243 and 400 invalid values? Does the first Managed Background Assets upload require any additional App Store Connect state beyond having BAHasManagedAssetPacks and BAUsesAppleHosting in the app? Does the app need a newly processed build in App Store Connect after enabling those plist keys before the first asset pack upload will work? Is there any known issue in Transporter 1.4 or App Store Connect for first-time Apple-hosted MBA uploads on macOS apps? If useful, I can also share the exact asset pack manifest and a redacted upload log.

This is my first iOS app release and I’m a bit confused. The initial version was reviewed in under 12 hours (rejected), and the corrected version was approved just as quickly. But my Product Page Optimization with only screenshots has been stuck in “Waiting for Review” for four days. Do these get reviewed only with new versions, or should I just wait it out?

When I update my app name, the App Store URL also changes, and since the app URL contributes to ASO performance, this is a concern for me. I would like to know whether it is possible to change the app name without affecting the URL, or if the previous URL automatically redirects to the new one.

Curious what backend others are choosing these days. I am building a vocabulary app and exploring which backend would be a good fit. Considering options like CloudKit, Firebase, Supabase, AWS Amplify, custom servers, or a combination. What are you using and what made you choose it?

Hi everyone, We are facing a critical blocker with our macOS app processing. Since March 5, 2026, every single build we have uploaded (8 builds total) has been stuck in the "Processing" state for over 4 days. For our project, due to the large binary size, processing usually takes about 4 to 6 hours normally. However, we now have a long queue of builds that haven't transitioned to "Ready to Submit" for up to 80+ hours. Stuck Builds List: 1.0.0 (444): Mar 8, 3:09 PM (Processing) 1.0.0 (443): Mar 8, 5:36 AM (Processing) 1.0.0 (440): Mar 7, 6:37 AM (Processing) 1.0.0 (438): Mar 6, 5:01 PM (Processing) 1.0.0 (434): Mar 6, 12:04 AM (Processing) 1.0.0 (433): Mar 5, 6:26 PM (Processing) 1.0.0 (432): Mar 5, 10:51 AM (Processing) 1.0.0 (431): Mar 5, 6:11 AM (Processing) (Note: The last successful build was 1.0.0 (429) on March 4, which processed within the expected 6-hour window.) There have been no changes to our project settings, Info.plist, or entitlements since the last successful build. This is completely halting our scheduled update release. Is anyone else experiencing a similar backlog with large macOS binaries? Or is there a known issue with the App Store Connect pipeline for the macOS platform recently? Any help or investigation from Apple engineers would be greatly appreciated. (Feedback ID: FB22156358)

Hello everyone, I am reaching out to the community and hopefully Apple representatives because I am currently facing a significant delay that has completely halted my first app launch. Here is the timeline of my submission process: February 1st: Initial submission of my first app. February 3rd: Received a rejection with minor requests for improvement. February 8th: I completed all requested changes and resubmitted the app. Status since then: The app has been stuck in "Waiting for Review" for exactly one month. Actions Taken: I submitted an Expedited Review request. I contacted Apple Developer Support twice via written tickets. I had a phone call with the Apple Developer Support team. During the phone call, I was advised not to withdraw and resubmit the app, as this would move me to the end of the queue. They mentioned they would escalate the issue to the review team. However, despite these efforts and the escalation, there has been absolutely no progress or change in status. This delay has put me a full month behind my launch schedule. I have spoken with several other iOS developers who mentioned their apps are typically reviewed within 1–5 days. This discrepancy is very discouraging. I am not looking for a shortcut; I simply want my app to be reviewed. My app is straightforward and does not contain any complex or controversial features that should justify such a long wait. This situation is unfortunately killing my motivation and excitement for development. Specific Questions: Is there anyone else experiencing a similar "limbo" for this long? Can any Apple representative provide clarity on how long this queue actually is or why a simple update is stuck for 30 days? Is there any other way to get a status update beyond the standard "just wait" response? Case ID: 102829479153 I would deeply appreciate any insights from the community or assistance from the Apple team. Thank you for your time.

I am trying to upload an App Preview to App Store Connect for a iphone app,I created the preview as an "App Preview". When I try to upload the app preview I get the message " your app preview is too big". The preview is 30 sec. It is 6 MB in size. MP4 format. Who know how to change my app preview

Should you rely only on organic installs, or would a mix of strategies work better? Isn’t optimizing keywords and refining creatives essential for higher visibility? Would running Apple Search Ads not further amplify reach? And doesn’t encouraging strong reviews ultimately help in improving both ranking and credibility?

When I update my app name, the App Store URL also changes, and since the app URL contributes to ASO performance, this is a concern for me. I would like to know whether it is possible to change the app name without affecting the URL, or if the previous URL automatically redirects to the new one.

I’m interested in hearing what currently concerns other indie iOS developers, as 2026 feels both exciting and somewhat fragile to me, with the constant worry that an Apple account issue or unexpected rejection could undo years of hard work overnight. AI has made cloning apps easier than ever and even strong niches can quickly attract well funded competitors, so while I’m optimistic about building, these are the realities I often find myself thinking about.

I use AES encryption on my app (it's a game), I encrypt the user data (JSON file) (levels / scores / etc...) This is how I answered the App Store Connect questions, not sure if it's correct:-Does your app use encryption? Select Yes even if your app only uses the standard encryption within Apple’s operating system. YES-Does your app qualify for any of the exemptions provided in Category 5 You can select Yes for this question if the encryption of your app is: (a) Specially designed for medical end-use (b) Limited to intellectual property and copyright protection (c) Limited to authentication, digital signature, or the decryption of data or files (d) Specially designed and limited for banking use or “money transactions”; or (e) Limited to “fixed” data compression or coding techniques NO-Does your app implement any encryption algorithms that are proprietary or not accepted as standards by international standard bodies (IEEE, IETF, ITU, etc.)? NO-Does your app implement any standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple’s operating system? YESIs your app going to be available on the App Store in France? YESNow it's sending me to Encryption page - Add Export Compliance Documentation for ITC.apps.universal.platformName.iosIs your app designed to use cryptography or does it contain or incorporate cryptography? (Select Yes even if your app is only utilizing the encryption available within Apple’s operating system.) YESDoes your app meet any of the following: (a) Qualifies for one or more exemptions provided under Category 5 Part 2 (b) Use of encryption is limited to encryption within Apple’s operating system (c) Only makes calls over HTTPS (d) App is made available only in the U.S. and/or Canada NODoes your app implement any encryption algorithms that are proprietary or not accepted as standards by international standard bodies (IEEE, IETF, ITU, etc.)? NODoes your app implement any standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple’s operating system? YES (it asks me to submit a copy of your French encryption declaration approval form- not sure what it is so I changed it to NO meanwhileClicked OK and then nothing happens. I'm not sure how to continue from here, In order to submit my app to test flight I need to provide export compliance information, which asks my the questions above, and then sends me to Add Export Compliance Documentation, but nothing was added ...

Hi everyone, I’m encountering a persistent issue with a visionOS app distributed through TestFlight for internal testing. The Problem: I have successfully archived and distributed the build as an Internal Test. The testers (including myself) received the invitation, accepted it, and the app is visible in the TestFlight app on Apple Vision Pro. However, the moment we click the "Install" button, an alert pops up saying: "The requested app is not available or doesn't exist." Context: Platform: visionOS (Targeting Vision Pro). App History: This is an ongoing project where the last distribution was about 5 months ago. The app has never been submitted for formal App Review or public release; it has only been used for TestFlight. Account Status: All agreements (including the Paid Applications Agreement) are active and in effect. What I have tried (but did not work): Re-uploading builds: Increased both version and build numbers and re-archived. Resetting Test Groups: Deleted the existing internal testing group, waited, and created a new group to re-invite testers. Tester Association: Removed all testers and re-added them to force a new invitation email. Device-side: Signed out and back into "Media & Purchases" on the Vision Pro. Key Observation: To determine if it was a project-level configuration error, I created a completely new App Identifier (Bundle ID) for the same project code and uploaded it as a new app record. In this case, TestFlight worked perfectly, and I could install the app without any issues. This leads me to believe that the original Bundle ID is stuck in some kind of "detached" or "stale" state on the App Store Connect backend. Has anyone experienced a specific Bundle ID being "corrupted" in the TestFlight system after a period of inactivity? Is there a way to force a full reset of the TestFlight status for an existing app record, or is this a backend bug that only Apple Support can resolve? Any insights or workarounds would be greatly appreciated.

Hi everyone, I’m encountering a persistent issue with a visionOS app distributed through TestFlight for internal testing. The Problem: I have successfully archived and distributed the build as an Internal Test. The testers (including myself) received the invitation, accepted it, and the app is visible in the TestFlight app on Apple Vision Pro. However, the moment we click the "Install" button, an alert pops up saying: "The requested app is not available or doesn't exist." Context: Platform: visionOS (Targeting Vision Pro). App History: This is an ongoing project where the last distribution was about 5 months ago. The app has never been submitted for formal App Review or public release; it has only been used for TestFlight. Account Status: All agreements (including the Paid Applications Agreement) are active and in effect. What I have tried (but did not work): Re-uploading builds: Increased both version and build numbers and re-archived. Resetting Test Groups: Deleted the existing internal testing group, waited, and created a new group to re-invite testers. Tester Association: Removed all testers and re-added them to force a new invitation email. Device-side: Signed out and back into "Media & Purchases" on the Vision Pro. Key Observation: To determine if it was a project-level configuration error, I created a completely new App Identifier (Bundle ID) for the same project code and uploaded it as a new app record. In this case, TestFlight worked perfectly, and I could install the app without any issues. This leads me to believe that the original Bundle ID is stuck in some kind of "detached" or "stale" state on the App Store Connect backend. Has anyone experienced a specific Bundle ID being "corrupted" in the TestFlight system after a period of inactivity? Is there a way to force a full reset of the TestFlight status for an existing app record, or is this a backend bug that only Apple Support can resolve? Any insights or workarounds would be greatly appreciated.

I'm trying to understand why App Preview uploads are stuck in this state even after 24 hours without any errors thrown My current video has the following specs which follows Apple requirements for Video Specifications for App previews. Video codec: H.264 High Profile Level 4.0 — meets requirement Resolution: 886×1920 — correct for 6.9" Frame rate: ~28.9 fps (under 30) — meets requirement Format: MP4 — meets requirement Duration: 28.08s (under 30s) — meets requirement Audio codec: AAC — meets requirement Audio bitrate: 256kbps — meets requirement Audio sample rate: 44.1kHz — meets requirement Audio channels: stereo — meets requirement

I removed TestFlight app from old device (email is no where exists in AppStore connect in Testers) which has different email than my AppStoreConnect email. Now I am trying to get invitation to the device which has same email as my AppStoreConnect, but keep getting -> Couldn't Load App The apple Account you're currently signed in with, , doesn't match the one assiciated to this invitation. You can sign in to TestFlight with original Apple Account, , or request a ne…. Where as all other apps in the AppStore connect shows up fine in the TestFlight using appstore connect email. Followed all the reset & settings mentioned but no luck so far.

Hello everyone, I’m facing an issue with my app submission being stuck in “Waiting for Review.” I initially submitted my app on 21 February and waited until 27 February, but the review process did not start and there were no updates. On 27 February, I contacted Apple Support regarding this issue, but I did not receive any response. Since there was still no progress, on 4 March I removed the app from review and resubmitted it again, but it is still showing “Waiting for Review.” This delay is affecting my operations, so I would really appreciate any guidance or help if someone has experienced a similar situation. App ID: 6741708449 Thank you.

One of my apps has been stuck in “Waiting for Review” for the past 21 days. App ID: 6758734829. I have contacted other support channels over the past few weeks but have not received any response. I also have three additional apps, App IDs 6758755469, 6759047311, and 6759095185, that have been in review for the last 14 days. All of these apps have already been live on the Google Play Store for months. I am trying to launch them on the App Store so I can move forward with my marketing plans. I kindly request Apple to review these submissions and help resolve whatever is causing the delay.