Navigate the App Store landscape. Share strategies for app submission, distribution, marketing, and user acquisition. Discuss best practices for getting your app discovered and downloaded.

All subtopics
Posts under App Store Distribution & Marketing topic

Post

Replies

Boosts

Views

Activity

Locate the In-App Purchases and Subscriptions Section in App Store Connect
App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.
0
0
3.1k
Jun ’26
All my new apps were rejected for SPAM instantly - Guideline 4.3
Hello! I already have 4 active apps and 2 games in the App Store. THE PROBLEM In past months I've submitted a few new apps and games, all of which were instantly rejected under guideline 4.3 regarding spam. They went from “Waiting for Review” to “In Review” and, a second later, to “Rejected.” This happenend to all 4 new apps I was submitting. I answered all the questions, but I don't think they were ever read, since all apps were rejected immediately again. I can't share my apps/games with you via TestFlight either, because they get rejected there as well. I can only give you Play Store links if your are interested, or let you play desktop demos for the games. I believe there is no need to say that I have been working on these apps and games for several months and that, for the most part, they are original and in no way copies of anything else. Some of their features are actually unique, or at least not found in comparable apps. For example, one of these apps is an advanced expiry tracker with integrated AI scanning and management capabilities, with a strong focus on privacy, which can effortlessly handle all types of expiration with minimal user input (automatic renewal, aumatic expense management, and so on). Another game I've been working on for a long time is a complete motorcycle racing suite called the Hyper Racing Series, featuring 3 games in one: superbike racing, supermoto racing, MX racing. Each game has its own physics and control system, unique motorcycle models, unique tracks. The engine sounds were synthesized based on the sounds of real racing motorcycles. One of these app already is doing well on the Play Store, and people who have downloaded it have left positive reviews, and some of them are using the premium features as well. WHAT TO DO NOW? So, what would you guys do if you were in my shoes at this point? They've already threatened to terminate my account, but at this point I'm willing to accept that since I can no longer publish my works. If there's anything else you'd like to know, please feel free to ask.
2
0
108
30m
Repeated App Store Rejections Under Guideline 4.3(a) Despite Following Apple's Instructions – Seeking Advice
ello everyone, I'm looking for advice from developers who have experienced repeated App Store rejections under Guideline 4.3(a), particularly in situations involving a previously published version of the same organization's application under another developer account. I'm developing and publishing an officially authorized application for Arise and Shine Heavenly Embassy. Unfortunately, I've been caught in a prolonged App Review process, and I'm struggling to find a clear path toward resolving the issue. Background There was a previous Arise & Shine application published under a former developer's Apple Developer account. I subsequently developed a new version of the application under my own Apple Developer account, with authorization from the organization. During the review process, Apple repeatedly rejected the new application under Guideline 4.3(a) – Spam. I understand Apple's concerns about duplicate applications and appreciate the need to maintain quality on the App Store. However, I have been trying to resolve this matter in good faith. What I've done so far Communicated with Apple App Review regarding the rejection. Attended a discussion with an Apple representative to understand the concerns. Followed the instructions to investigate and remove the previous application. Accessed the former developer's account and attempted to remove the previous application. Discovered that the removal could not be completed because the former developer's Apple Developer Program membership had expired. Explained this limitation to Apple and provided supporting evidence. Was subsequently encouraged to resubmit the application, which I did in good faith. Unfortunately, the application was rejected again under the same guideline. What makes this particularly difficult is that I still haven't received a sufficiently specific explanation of what exactly is triggering Guideline 4.3(a), or what concrete changes Apple expects me to make. Where I need help I would appreciate insights from developers who have experienced similar situations. Specifically: Can an application be rejected under Guideline 4.3(a) because a previous version of the same organization's app remains on the App Store under another developer account? If the previous developer's membership has expired and the application cannot be removed through that account, what is the appropriate process for resolving this? Is there an established procedure for transferring an application or resolving duplicate-app concerns when the original developer account is no longer active? How can a developer get a case escalated to an App Review specialist who can examine the complete history of previous discussions and submissions? I have also requested another phone call with App Review because I believe a direct discussion would be more productive than continuing through repeated rejections without specific guidance. What I'm hoping to achieve I am not asking Apple to overlook its guidelines or grant special treatment. I simply want to understand the precise issue, follow the appropriate procedure, and get this officially authorized application reviewed on its actual merits. I've invested considerable time and resources into this project, and it is frustrating to remain stuck despite making genuine efforts to cooperate. If anyone from the developer community has navigated a similar situation, I would genuinely appreciate hearing how you resolved it. Thank you.
1
0
31
30m
All 4 of My Original Native Games Rejected Under Guideline 4.3 & 4.2.6 – No Reply to Appeal/Expedite Request
Hello everyone, After waiting over a week in review, all of my recently submitted apps were rejected under Guideline 4.3 (Spam) and Guideline 4.2.6 (App Generation Services). The rejection messages are generic and do not specify which components, assets, or metadata triggered the flags. To clarify, these are original native apps built from scratch in Xcode/Swift—not commercialized templates, web wrappers, or third-party app generation builds—and each has distinct mechanics, custom assets, and functionality. I have already replied in the Resolution Center, submitted an official appeal/support inquiry, and requested an expedited review, but it has been 3 days with no response. Has anyone experienced false-positive 4.3/4.2.6 flags across multiple distinct apps on the same developer account, or can an Apple representative advise on what specific areas I should audit to get these resolved? Thank you in advance for your guidance.
1
0
126
30m
New App Rejected Under Guideline 4.3(a) on Both iOS and tvOS — Seeking Clarification
Hi everyone, I’d like to share my experience with the first release of my app and ask for some guidance. Submission details App ID: 6829444660 Platforms: iOS and tvOS (Apple TV) Initially submitted: November 1, 2026, at 7:17 PM Rejection received: November 13, 2026, at 9:30 PM Rejection reason: Guideline 4.3(a) — Design — Spam Both the iOS and Apple TV submissions received the same rejection at the same time. How the app was built I personally developed the app using UIKit, with some parts built in SwiftUI. I also created the visual assets myself using Canva. AI was not involved in writing or designing the app; its involvement was limited to testing-related assistance. Having personally worked on the implementation and visual design, it was discouraging to see the app classified as spam. I believe there may be a misunderstanding about my submission, and I would appreciate an opportunity to clarify it. What I’m asking for Could an Apple representative help identify the specific elements or duplication concerns that led to this rejection? Clear, actionable feedback would help me understand: Which aspects of the app raised concerns under Guideline 4.3(a). What changes, if any, are needed to address those concerns. What supporting information I can provide to help clarify the situation. This project means a lot to me. I respect the review process and want to meet Apple’s requirements. I would sincerely appreciate a reconsideration of my submission and clear guidance on how to move forward. Has anyone experienced a simultaneous 4.3(a) rejection on iOS and tvOS and successfully resolved it? Thank you for taking the time to read this. Any guidance would mean a great deal to me.
2
0
166
31m
App Stuck in “Waiting for Review” Since November 17
Hi everyone, On Monday, November 17, our company submitted an app to the App Store, and it has been stuck in “Waiting for Review” ever since. From what I’ve read, the usual review time is around 24–48 hours, so we’re a bit worried that the review hasn’t even started yet. Has anyone else seen similar delays recently? Any insight or advice would be greatly appreciated. Thank you!
6
1
458
33m
Account flagged under 4.3: five unrelated apps rejected the same minute, replies unanswered for 9 days, rebuilt app rejected again as "similar"
Hi, I am a solo developer with an individual account since 2024. I would appreciate guidance from App Review, because I do not know what else I can do from my side. On October 13 at 00:06 all five apps I had in review were rejected within the same minute under 4.3 and 4.2.6, each with the same nine questions about the app, its audience, beta testing, shared code and templates. The apps are not related: a voice recorder with on-device transcription, a dice roguelike, a tile based dungeon game, a studio simulation game and a Safari extension for cookie banners. I built them myself in Xcode over several weeks and submitted each one when it was finished, which is why they arrived in the same week. No template, no generation service, no client, no third party SDKs, no other accounts. The same day I answered all nine questions in full for four of the apps and withdrew the fifth, the cookie banner extension, to rebuild it. Nine days later there is no response on any of the four threads. On October 21 I submitted the rebuilt extension as version 2.0. It now has consent receipts decoded from each site's TCF record, a public page listing the 100 sites tested before every release with the result for each, a separate mode for subscribe-or-consent walls, Global Privacy Control, Shortcuts and a Mac app. A review video and a public test page were attached. It was rejected within a day under 4.3(a) as sharing "a similar binary, metadata and/or concept" with apps submitted by me or others, with an Extended Review note. The only earlier app with this name is my own withdrawn 1.0. I have stopped submitting anything. My questions: Is there anything more I can provide for the four open threads so a reviewer can look at the apps themselves? I can send screen recordings, source code or demo builds the same day. For the 4.3(a) rejection: what was the app matched against, and what counts as a sufficient difference in this category, given that several cookie banner blockers for Safari were approved in 2026? App IDs: 6821429432 (Voice Notes: Local Transcribe), 6821423492 (Lampfall), 6821275353 (Bone Caster), 6819040142 (Vibe Coder), 6818993189 (Cookie Hide, version 2.0). Thank you for your time. Armen Ter-Oganezov
3
0
167
34m
TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.
61
8
7.2k
34m
TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)
Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds
157
13
12k
35m
Developer Information Update stuck "In Process" for over a week, blocking app updates
Hi everyone, About 9 days ago, as the Account Holder, I submitted a developer information update for our organization's Apple Developer account. Since then, the account has shown this message: "Developer Information Update In Process. Your developer information update is currently in process. Until it's complete, the updated Program License Agreement may not go into effect." Because of this, we can't accept the updated Program License Agreement, so we can't submit updates for our live app on the App Store. This is affecting our users. What we've done so far: Checked the Account Holder's email (including spam) for any request for documents. Nothing found. Checked Membership details and Agreements, Tax, and Banking in App Store Connect. Nothing is flagged as needing action. Contacted Developer Support several times through the contact form. No reply yet. My questions: Has anyone had a developer information update stuck like this? How long did it take, and what got it moving? Is there a way to escalate a stalled update, or to cancel it so we can accept the agreement and continue releasing? Any guidance from the community or the Apple team would be really appreciated. Thank you.
0
0
3
36m
Waiting for Review since Monday, Nov 16. Our expedited review request was accepted on Nov 16 as well. Need review by Nov 24, 2026 to meet critical release deadline of Nov 30, 2026.
Hi, Our app has been in the Waiting for Review state, with an accepted expedited review request, since last Monday, Nov 16, 2026. Request: If it is at all possible, could our app get reviewed in time for our release deadline of Monday, Nov 30, 2026? If reasonable, a review result by Tuesday, Nov 24, 2026 would leave us time to fix anything you flag and re-submit for review. Reason: Monday, Nov 30, 2026 is our studio’s fiscal year-end. The game has to be live by then to be included in this year’s Ontario Interactive Digital Media Tax Credit claim, which is administered by Ontario Creates, an agency of the Ontario government. Missing the date by even one day pushes that funding back a full year, which is very hard on a studio our size. We can send documentation if that helps. The expedited request we made through Developer Support had no place for an explanation, so I want to make sure the reason and the date reach the review team. I know this is a big ask during a busy period, and I’m grateful for any help you can give. Thank you, William App Apple ID: 6832757024 Version / build: 1.0.0 Submitted: Nov 16, 2026 Original Expedite Request Date: Nov 16, 2026 Requested Latest Review Date: Nov 24, 2026
0
0
4
36m
Account-wide TestFlight build expiration issue — Feedback ID: FB25656884
@DTS Engineer (Albert), I am experiencing the exact same issue across all 3 apps on our team account (TJ9KJ6WV99). Every newly uploaded, validated build (Binary State: Validated, beta-reports-active: true) automatically changes status to Expired within 30–60 minutes of upload and disappears from TestFlight, despite all agreements (Paid Apps, Free Apps), Tax Forms, and DSA Compliance being verified Active (since account reactivation on Oct 29, 2026). Apple Support performed a backend process restart 48 hours ago which temporarily resolved the issue, but all new builds reverted to Expired again today within an hour (matching the BETA_CONTRACT_MISSING / backend state desync reported earlier in this thread). Feedback Assistant Ticket: FB25656884 (includes Team ID TJ9KJ6WV99 and all 3 numeric App IDs). Thanks in advance for routing this to the TestFlight / App Store Connect team!
1
0
96
37m
Review submission stuck in "Canceling" for 12 days: version locked, can't cancel or resubmit
Our iOS review submission has been stuck in CANCELING since 10 Nov 2026. Every action on it is refused, so we haven't been able to ship an update for 12 days. App ID: 6809173786 Stuck submission: 0c25955e-e5d8-4835-8605-79f8115c9992 Developer Support cases: 103018649498, 103018648320 App Review case: 30000012887740 The submission has 4 items, all still "Ready for Review": iOS App 1.0.14 (app version) Lifetime-Flybud (our first non-consumable IAP) retention-3840x2160.png (Asset Library image) Flybud_Orbit_Header_3840x164… (Asset Library video) What the App Store Connect API returns (22 Nov): Cancel the submission: "Resource state is invalid – Resource cannot be canceled at the moment, please try again later." Remove an item: "Resource state is invalid – Item was already submitted." Add 1.0.14 to a new submission: "Asset Library validation error – Asset is locked by a standalone review submission." Submit the IAP on its own: "The first Non-Consumable In-App Purchase for this app must be submitted for review at the same time that you submit an app version." The version is locked by the stuck submission, and the IAP can only ship with a version, so everything is blocked. New builds upload and process normally. Given error 3, I suspect the Asset Library items are what's preventing the cancellation from completing. Since 10 Nov I've written to App Review four times, opened two Developer Support cases, filed a bug report and emailed the App Store team. Phone support has been unavailable, and App Review can't see the submission in their queue. Could someone at Apple escalate this to App Store Connect engineering to clear or complete the cancellation? Thank you.
0
0
3
39m
First app Waiting for Review since 1 Nov, support case has no reply
Our first app, PerCent: Personal Finance (Apple ID 6826506651), has been Waiting for Review since 1 Nov 2026 (submission 52e16f91-b3f5-4bfd-bdb5-babb9706518c). We requested an expedited review on 3 Nov and opened Developer Support case 30000005014098 on 4 Nov. We have received no reply, and there are no messages in App Store Connect. Could someone from Apple please check whether this submission is stuck or whether anything is needed from us? Thank you.
4
0
110
40m
TestFlight dead on new accounts (Oct-Nov 2026): no invite emails, Beta App Review 422 "Please try again later". Collecting all cases here
This thread collects every account with the fault below in one place, so Apple sees one issue across many accounts instead of many lonely threads. If you have it, please reply. What to include is at the end. The fault Builds upload and process fine. Then two things never work: No TestFlight invite email is ever sent. Every tester, internal or external, stays "Invited". Reinvite does nothing: POST /iris/v1/betaTesterInvitations returns 201 Created and no email arrives, not in spam either. A build cannot be submitted for Beta App Review. "There was an error processing your request. Please try again later." POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE with only that sentence and no further reason. So internal testing is blocked by the missing emails and external testing by the refused review. Agreements, tax, banking and DSA are Active, Test Information and export compliance are complete, and nothing a developer can change makes a difference. The accounts reporting it are mostly new, enrolled around October 2026. My case Account enrolled 31 October 2026. Fault since 5 November 2026, every day. Region: Türkiye. No invite email reaches any of my six testers. Beta App Review submit returns the 422 every time. On 13 November I reset everything to rule out my side: removed every tester and both groups, expired the old builds, uploaded a fresh build, added everyone again. Nothing changed. The fresh build is VALID. Its internal state is IN_BETA_TESTING with "automatically notify testers" on, yet its record says the testers were not notified. Its external state is READY_FOR_BETA_SUBMISSION and the submit is refused. Feedback Assistant: FB25540791 (two HAR logs). Developer Support cases 30000005155573 and 30000005989992: only automatic receipts since 4 November, no human reply. Phone support shows as unavailable. Others reporting it https://developer.apple.com/forums/thread/856330 (@Hopeforge): internal invite emails never delivered, testers stay "Invited". Recreating groups, resending and new builds did not help. An App Store Connect Engineer replied there and asked for Feedback Assistant tickets with HAR logs. https://developer.apple.com/forums/thread/857012 (@Kirnuvirsta): tester stuck on "Invited" with no email, Beta App Review submit fails, same on a second app record. FB25399719, case open since 28 October. https://developer.apple.com/forums/thread/856896 (@medlzd, @ganderbite): new internal testers show "Invited" and never get the email, Resend Invite does nothing, on all apps. https://developer.apple.com/forums/thread/856592 (@EmlakBaseDev): Beta App Review submit returns 422 "Please try again later" on three apps since 24 October, build VALID and READY_FOR_BETA_SUBMISSION. https://developer.apple.com/forums/thread/854803 (@SefaAygun, @JanuaryTwelfth): adding a build to external testing fails with "try again later". https://developer.apple.com/forums/thread/854106 (@BWGTrading): new organization account, TestFlight stopped working for all apps on 27 October. If you have this too, please reply with When your account was enrolled, and since when the fault shows Which of the two you have: no invite emails, 422 on Beta App Review, or both Your country or region, to see whether it is tied to one Your Feedback Assistant number (FB...) and Developer Support case ID Anything Apple told you, and above all whether it got fixed, and how If you have not filed a Feedback Assistant ticket yet, please do: steps, a HAR log of the failing request, your App ID. The engineer in thread 856330 asked for exactly that. To Apple Could someone from the App Store Connect or TestFlight team tell us whether this is a known fault in how TestFlight is set up for newly enrolled accounts, and whether each account needs a change on your side? We are paying members who cannot use TestFlight at all, and our support cases stay unanswered for weeks. Thank you.
18
8
830
41m
Three rejections in a week for errors on the reviewer’s iPad, and a reviewer who couldn’t find the subscription the notes describe
I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing. Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView. What has happened: 30 Oct: submitted. 3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day. 5 Nov: rejected on three points: 5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then; 2.1(b): the reviewer couldn’t find the In-App Purchase; 2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27. We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track. 8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests. So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours. The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved. Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things: When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting? Could every issue be raised in one review, rather than a new one appearing after each fix? Could reviewers read the review notes? For us they answered the question the rejection asked. Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it. The quality of the testing effort has been pretty poor. Thank you.
5
0
208
1h
Asked to resubmit after being offered bug fix approval, now 7 days in "Waiting for Review" with no response
Hello, We'd appreciate help from the App Review team with our app update. App: AI Video Generator - Bunsy (Apple ID 6762499422) Version: 1.0.13 (build 350) Submission ID: 644c0463-bcb1-44c5-a0bb-b91ccf1860c2 Timeline: Nov 4: submitted version 1.0.13. Nov 12: App Review identified a Guideline 4 issue (Sign in with Apple logo artwork) under Bug Fix Submissions. The message said the issue could be resolved in our next update, and that if we replied, the submission could be approved without resubmitting. Nov 12: we replied the same day and asked to approve the submission as a bug fix, committing to address the issue in the next update. Nov 13: App Review asked us to resubmit anyway. Nov 14: we resubmitted with build 350, which already includes the fix (native Sign in with Apple button). It has been in "Waiting for Review" since then. Nov 16: we requested an expedited review. Nov 19: we contacted App Review about the status (Case ID 103018616391) and have received only the automated confirmation. We followed every instruction we received, and this version has now been waiting for 17 days in total. It fixes a crash on first launch that affects users of the current version. Could you please check whether anything is holding this submission or whether anything else is needed from us? Thank you.
1
0
153
14h
First app stuck in "Waiting for Review" since Nov 13, after Guideline 2.1 info response
Hello App Review team, My first app, Rental Records, has been in "Waiting for Review" since November 13, 2026, and I'd appreciate it if someone could check whether it needs any action from me. App: Rental Records (iOS 1.0) Apple ID: 6832051224 Platform: iOS, Organization account Timeline: Nov 7: First submission Nov 8: Rejected under Guideline 2.1 (Information Needed) Nov 13: I added everything requested to the App Review Notes (app description, demo logins for both account types, list of external services, regional statement, and a screen recording) and resubmitted. Status has been "Waiting for Review" ever since. What I have already done: Submitted an Expedited App Review request days ago Called Developer Support twice and was told there is no fixed timeline Sent an App Review status inquiry (Case ID: [30000019474998]) The demo accounts work and the notes are complete. I'm happy to provide anything else you need. Thank you for your time.
1
0
143
14h
Concern Regarding App Review Timeline After Months of Organization Enrollment Delays – Fixit Employee Portal
Hello Apple Developer Community, I am reaching out to seek guidance and express our concern regarding our iOS application, Fixit Employee Portal, which is currently showing "Waiting for Review" in App Store Connect. Application Details: • App Name: Fixit Employee Portal • App Apple ID: 6834282511 • Version: 1.0.4 (Build 2) • Submission Date: November 13, 2026 • Current Status: Waiting for Review Before reaching this stage, our company had already spent several months completing the verification and approval process for our Apple Developer Program organization enrollment. We appreciate Apple's commitment to security, compliance, and quality throughout the enrollment and application review processes. However, after experiencing such an extended enrollment process, we are concerned about the possibility of further significant delays before our application becomes available to our employees. Our application is intended to provide essential employee services to our manpower workforce, including access to employment-related information and company resources. Many of our employees are awaiting its availability on iOS, and timely deployment is important to our daily operations. While we understand that our application was only recently submitted for review, we would sincerely appreciate clarification on the following: Is the current waiting period normal for a newly submitted application under a recently approved organization account? After several months of organization enrollment delays, should we anticipate another extended waiting period for the application review process? Is there a way to confirm that our application has no outstanding requirements that could delay its review? Given our employees' operational need for this application, would an expedited review request be appropriate? We are not requesting that Apple bypass its standard review requirements. We simply hope to understand the expected process and avoid further unnecessary delays after the lengthy organization enrollment experience. We sincerely appreciate the efforts of the Apple Developer and App Review teams and would be grateful for any guidance or assistance. Thank you for your understanding and support. Best regards, Fixit Development Team
2
0
131
14h
Two Apps Facing Review Issues – No Response from Apple. Could There Be an Issue with My Developer Account
Hello everyone, I'm an independent developer, and I'm currently experiencing review issues with two different apps under the same Apple Developer account. I'm starting to worry that there may be something wrong with my account or the review process. App 1 – Rejected Due to an Account Restriction Mistaken for a Bug My first app was rejected because the reviewer couldn't complete an in-app purchase. However, this wasn't a technical bug. My app has an intentional rule that prevents one Apple ID subscription from being linked to multiple app accounts. The sandbox Apple ID used during review had already been linked to another test account, which triggered this restriction. To make testing easier, I updated our server to remove this restriction for sandbox subscriptions while keeping it unchanged for real users. I explained everything to Apple on November 17 and requested another review. I also requested a phone call on November 18 and submitted an appeal. Unfortunately, I have received no response to any of these requests. App 2 – Rejected and Resubmitted, Still Waiting for Review My second app was also rejected because the reviewer reported that nothing happened after completing an in-app purchase. I resubmitted the app for review on November 19, but it is still waiting for review, and I haven't received any further feedback. My Main Concern Both apps are under the same developer account, and I'm having difficulty getting responses or moving the review process forward. I understand that reviews can take time, but I've already taken steps to address the issues and tried contacting Apple through multiple channels. I'm now concerned that there might be an issue with my developer account affecting the review process. Has anyone experienced similar problems with multiple apps under the same developer account? Is there any way to ask Apple to check whether my account has any review-related restrictions or unusual status? And when App Review messages, appeals, and phone call requests go unanswered, what is the best way to escalate the situation? I would really appreciate any advice from developers who have experienced something similar. Thank you!
1
0
145
14h
Locate the In-App Purchases and Subscriptions Section in App Store Connect
App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.
Replies
0
Boosts
0
Views
3.1k
Activity
Jun ’26
All my new apps were rejected for SPAM instantly - Guideline 4.3
Hello! I already have 4 active apps and 2 games in the App Store. THE PROBLEM In past months I've submitted a few new apps and games, all of which were instantly rejected under guideline 4.3 regarding spam. They went from “Waiting for Review” to “In Review” and, a second later, to “Rejected.” This happenend to all 4 new apps I was submitting. I answered all the questions, but I don't think they were ever read, since all apps were rejected immediately again. I can't share my apps/games with you via TestFlight either, because they get rejected there as well. I can only give you Play Store links if your are interested, or let you play desktop demos for the games. I believe there is no need to say that I have been working on these apps and games for several months and that, for the most part, they are original and in no way copies of anything else. Some of their features are actually unique, or at least not found in comparable apps. For example, one of these apps is an advanced expiry tracker with integrated AI scanning and management capabilities, with a strong focus on privacy, which can effortlessly handle all types of expiration with minimal user input (automatic renewal, aumatic expense management, and so on). Another game I've been working on for a long time is a complete motorcycle racing suite called the Hyper Racing Series, featuring 3 games in one: superbike racing, supermoto racing, MX racing. Each game has its own physics and control system, unique motorcycle models, unique tracks. The engine sounds were synthesized based on the sounds of real racing motorcycles. One of these app already is doing well on the Play Store, and people who have downloaded it have left positive reviews, and some of them are using the premium features as well. WHAT TO DO NOW? So, what would you guys do if you were in my shoes at this point? They've already threatened to terminate my account, but at this point I'm willing to accept that since I can no longer publish my works. If there's anything else you'd like to know, please feel free to ask.
Replies
2
Boosts
0
Views
108
Activity
30m
Repeated App Store Rejections Under Guideline 4.3(a) Despite Following Apple's Instructions – Seeking Advice
ello everyone, I'm looking for advice from developers who have experienced repeated App Store rejections under Guideline 4.3(a), particularly in situations involving a previously published version of the same organization's application under another developer account. I'm developing and publishing an officially authorized application for Arise and Shine Heavenly Embassy. Unfortunately, I've been caught in a prolonged App Review process, and I'm struggling to find a clear path toward resolving the issue. Background There was a previous Arise & Shine application published under a former developer's Apple Developer account. I subsequently developed a new version of the application under my own Apple Developer account, with authorization from the organization. During the review process, Apple repeatedly rejected the new application under Guideline 4.3(a) – Spam. I understand Apple's concerns about duplicate applications and appreciate the need to maintain quality on the App Store. However, I have been trying to resolve this matter in good faith. What I've done so far Communicated with Apple App Review regarding the rejection. Attended a discussion with an Apple representative to understand the concerns. Followed the instructions to investigate and remove the previous application. Accessed the former developer's account and attempted to remove the previous application. Discovered that the removal could not be completed because the former developer's Apple Developer Program membership had expired. Explained this limitation to Apple and provided supporting evidence. Was subsequently encouraged to resubmit the application, which I did in good faith. Unfortunately, the application was rejected again under the same guideline. What makes this particularly difficult is that I still haven't received a sufficiently specific explanation of what exactly is triggering Guideline 4.3(a), or what concrete changes Apple expects me to make. Where I need help I would appreciate insights from developers who have experienced similar situations. Specifically: Can an application be rejected under Guideline 4.3(a) because a previous version of the same organization's app remains on the App Store under another developer account? If the previous developer's membership has expired and the application cannot be removed through that account, what is the appropriate process for resolving this? Is there an established procedure for transferring an application or resolving duplicate-app concerns when the original developer account is no longer active? How can a developer get a case escalated to an App Review specialist who can examine the complete history of previous discussions and submissions? I have also requested another phone call with App Review because I believe a direct discussion would be more productive than continuing through repeated rejections without specific guidance. What I'm hoping to achieve I am not asking Apple to overlook its guidelines or grant special treatment. I simply want to understand the precise issue, follow the appropriate procedure, and get this officially authorized application reviewed on its actual merits. I've invested considerable time and resources into this project, and it is frustrating to remain stuck despite making genuine efforts to cooperate. If anyone from the developer community has navigated a similar situation, I would genuinely appreciate hearing how you resolved it. Thank you.
Replies
1
Boosts
0
Views
31
Activity
30m
All 4 of My Original Native Games Rejected Under Guideline 4.3 & 4.2.6 – No Reply to Appeal/Expedite Request
Hello everyone, After waiting over a week in review, all of my recently submitted apps were rejected under Guideline 4.3 (Spam) and Guideline 4.2.6 (App Generation Services). The rejection messages are generic and do not specify which components, assets, or metadata triggered the flags. To clarify, these are original native apps built from scratch in Xcode/Swift—not commercialized templates, web wrappers, or third-party app generation builds—and each has distinct mechanics, custom assets, and functionality. I have already replied in the Resolution Center, submitted an official appeal/support inquiry, and requested an expedited review, but it has been 3 days with no response. Has anyone experienced false-positive 4.3/4.2.6 flags across multiple distinct apps on the same developer account, or can an Apple representative advise on what specific areas I should audit to get these resolved? Thank you in advance for your guidance.
Replies
1
Boosts
0
Views
126
Activity
30m
New App Rejected Under Guideline 4.3(a) on Both iOS and tvOS — Seeking Clarification
Hi everyone, I’d like to share my experience with the first release of my app and ask for some guidance. Submission details App ID: 6829444660 Platforms: iOS and tvOS (Apple TV) Initially submitted: November 1, 2026, at 7:17 PM Rejection received: November 13, 2026, at 9:30 PM Rejection reason: Guideline 4.3(a) — Design — Spam Both the iOS and Apple TV submissions received the same rejection at the same time. How the app was built I personally developed the app using UIKit, with some parts built in SwiftUI. I also created the visual assets myself using Canva. AI was not involved in writing or designing the app; its involvement was limited to testing-related assistance. Having personally worked on the implementation and visual design, it was discouraging to see the app classified as spam. I believe there may be a misunderstanding about my submission, and I would appreciate an opportunity to clarify it. What I’m asking for Could an Apple representative help identify the specific elements or duplication concerns that led to this rejection? Clear, actionable feedback would help me understand: Which aspects of the app raised concerns under Guideline 4.3(a). What changes, if any, are needed to address those concerns. What supporting information I can provide to help clarify the situation. This project means a lot to me. I respect the review process and want to meet Apple’s requirements. I would sincerely appreciate a reconsideration of my submission and clear guidance on how to move forward. Has anyone experienced a simultaneous 4.3(a) rejection on iOS and tvOS and successfully resolved it? Thank you for taking the time to read this. Any guidance would mean a great deal to me.
Replies
2
Boosts
0
Views
166
Activity
31m
App Stuck in “Waiting for Review” Since November 17
Hi everyone, On Monday, November 17, our company submitted an app to the App Store, and it has been stuck in “Waiting for Review” ever since. From what I’ve read, the usual review time is around 24–48 hours, so we’re a bit worried that the review hasn’t even started yet. Has anyone else seen similar delays recently? Any insight or advice would be greatly appreciated. Thank you!
Replies
6
Boosts
1
Views
458
Activity
33m
Account flagged under 4.3: five unrelated apps rejected the same minute, replies unanswered for 9 days, rebuilt app rejected again as "similar"
Hi, I am a solo developer with an individual account since 2024. I would appreciate guidance from App Review, because I do not know what else I can do from my side. On October 13 at 00:06 all five apps I had in review were rejected within the same minute under 4.3 and 4.2.6, each with the same nine questions about the app, its audience, beta testing, shared code and templates. The apps are not related: a voice recorder with on-device transcription, a dice roguelike, a tile based dungeon game, a studio simulation game and a Safari extension for cookie banners. I built them myself in Xcode over several weeks and submitted each one when it was finished, which is why they arrived in the same week. No template, no generation service, no client, no third party SDKs, no other accounts. The same day I answered all nine questions in full for four of the apps and withdrew the fifth, the cookie banner extension, to rebuild it. Nine days later there is no response on any of the four threads. On October 21 I submitted the rebuilt extension as version 2.0. It now has consent receipts decoded from each site's TCF record, a public page listing the 100 sites tested before every release with the result for each, a separate mode for subscribe-or-consent walls, Global Privacy Control, Shortcuts and a Mac app. A review video and a public test page were attached. It was rejected within a day under 4.3(a) as sharing "a similar binary, metadata and/or concept" with apps submitted by me or others, with an Extended Review note. The only earlier app with this name is my own withdrawn 1.0. I have stopped submitting anything. My questions: Is there anything more I can provide for the four open threads so a reviewer can look at the apps themselves? I can send screen recordings, source code or demo builds the same day. For the 4.3(a) rejection: what was the app matched against, and what counts as a sufficient difference in this category, given that several cookie banner blockers for Safari were approved in 2026? App IDs: 6821429432 (Voice Notes: Local Transcribe), 6821423492 (Lampfall), 6821275353 (Bone Caster), 6819040142 (Vibe Coder), 6818993189 (Cookie Hide, version 2.0). Thank you for your time. Armen Ter-Oganezov
Replies
3
Boosts
0
Views
167
Activity
34m
TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.
Replies
61
Boosts
8
Views
7.2k
Activity
34m
TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)
Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds
Replies
157
Boosts
13
Views
12k
Activity
35m
Developer Information Update stuck "In Process" for over a week, blocking app updates
Hi everyone, About 9 days ago, as the Account Holder, I submitted a developer information update for our organization's Apple Developer account. Since then, the account has shown this message: "Developer Information Update In Process. Your developer information update is currently in process. Until it's complete, the updated Program License Agreement may not go into effect." Because of this, we can't accept the updated Program License Agreement, so we can't submit updates for our live app on the App Store. This is affecting our users. What we've done so far: Checked the Account Holder's email (including spam) for any request for documents. Nothing found. Checked Membership details and Agreements, Tax, and Banking in App Store Connect. Nothing is flagged as needing action. Contacted Developer Support several times through the contact form. No reply yet. My questions: Has anyone had a developer information update stuck like this? How long did it take, and what got it moving? Is there a way to escalate a stalled update, or to cancel it so we can accept the agreement and continue releasing? Any guidance from the community or the Apple team would be really appreciated. Thank you.
Replies
0
Boosts
0
Views
3
Activity
36m
Waiting for Review since Monday, Nov 16. Our expedited review request was accepted on Nov 16 as well. Need review by Nov 24, 2026 to meet critical release deadline of Nov 30, 2026.
Hi, Our app has been in the Waiting for Review state, with an accepted expedited review request, since last Monday, Nov 16, 2026. Request: If it is at all possible, could our app get reviewed in time for our release deadline of Monday, Nov 30, 2026? If reasonable, a review result by Tuesday, Nov 24, 2026 would leave us time to fix anything you flag and re-submit for review. Reason: Monday, Nov 30, 2026 is our studio’s fiscal year-end. The game has to be live by then to be included in this year’s Ontario Interactive Digital Media Tax Credit claim, which is administered by Ontario Creates, an agency of the Ontario government. Missing the date by even one day pushes that funding back a full year, which is very hard on a studio our size. We can send documentation if that helps. The expedited request we made through Developer Support had no place for an explanation, so I want to make sure the reason and the date reach the review team. I know this is a big ask during a busy period, and I’m grateful for any help you can give. Thank you, William App Apple ID: 6832757024 Version / build: 1.0.0 Submitted: Nov 16, 2026 Original Expedite Request Date: Nov 16, 2026 Requested Latest Review Date: Nov 24, 2026
Replies
0
Boosts
0
Views
4
Activity
36m
Account-wide TestFlight build expiration issue — Feedback ID: FB25656884
@DTS Engineer (Albert), I am experiencing the exact same issue across all 3 apps on our team account (TJ9KJ6WV99). Every newly uploaded, validated build (Binary State: Validated, beta-reports-active: true) automatically changes status to Expired within 30–60 minutes of upload and disappears from TestFlight, despite all agreements (Paid Apps, Free Apps), Tax Forms, and DSA Compliance being verified Active (since account reactivation on Oct 29, 2026). Apple Support performed a backend process restart 48 hours ago which temporarily resolved the issue, but all new builds reverted to Expired again today within an hour (matching the BETA_CONTRACT_MISSING / backend state desync reported earlier in this thread). Feedback Assistant Ticket: FB25656884 (includes Team ID TJ9KJ6WV99 and all 3 numeric App IDs). Thanks in advance for routing this to the TestFlight / App Store Connect team!
Replies
1
Boosts
0
Views
96
Activity
37m
Review submission stuck in "Canceling" for 12 days: version locked, can't cancel or resubmit
Our iOS review submission has been stuck in CANCELING since 10 Nov 2026. Every action on it is refused, so we haven't been able to ship an update for 12 days. App ID: 6809173786 Stuck submission: 0c25955e-e5d8-4835-8605-79f8115c9992 Developer Support cases: 103018649498, 103018648320 App Review case: 30000012887740 The submission has 4 items, all still "Ready for Review": iOS App 1.0.14 (app version) Lifetime-Flybud (our first non-consumable IAP) retention-3840x2160.png (Asset Library image) Flybud_Orbit_Header_3840x164… (Asset Library video) What the App Store Connect API returns (22 Nov): Cancel the submission: "Resource state is invalid – Resource cannot be canceled at the moment, please try again later." Remove an item: "Resource state is invalid – Item was already submitted." Add 1.0.14 to a new submission: "Asset Library validation error – Asset is locked by a standalone review submission." Submit the IAP on its own: "The first Non-Consumable In-App Purchase for this app must be submitted for review at the same time that you submit an app version." The version is locked by the stuck submission, and the IAP can only ship with a version, so everything is blocked. New builds upload and process normally. Given error 3, I suspect the Asset Library items are what's preventing the cancellation from completing. Since 10 Nov I've written to App Review four times, opened two Developer Support cases, filed a bug report and emailed the App Store team. Phone support has been unavailable, and App Review can't see the submission in their queue. Could someone at Apple escalate this to App Store Connect engineering to clear or complete the cancellation? Thank you.
Replies
0
Boosts
0
Views
3
Activity
39m
First app Waiting for Review since 1 Nov, support case has no reply
Our first app, PerCent: Personal Finance (Apple ID 6826506651), has been Waiting for Review since 1 Nov 2026 (submission 52e16f91-b3f5-4bfd-bdb5-babb9706518c). We requested an expedited review on 3 Nov and opened Developer Support case 30000005014098 on 4 Nov. We have received no reply, and there are no messages in App Store Connect. Could someone from Apple please check whether this submission is stuck or whether anything is needed from us? Thank you.
Replies
4
Boosts
0
Views
110
Activity
40m
TestFlight dead on new accounts (Oct-Nov 2026): no invite emails, Beta App Review 422 "Please try again later". Collecting all cases here
This thread collects every account with the fault below in one place, so Apple sees one issue across many accounts instead of many lonely threads. If you have it, please reply. What to include is at the end. The fault Builds upload and process fine. Then two things never work: No TestFlight invite email is ever sent. Every tester, internal or external, stays "Invited". Reinvite does nothing: POST /iris/v1/betaTesterInvitations returns 201 Created and no email arrives, not in spam either. A build cannot be submitted for Beta App Review. "There was an error processing your request. Please try again later." POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE with only that sentence and no further reason. So internal testing is blocked by the missing emails and external testing by the refused review. Agreements, tax, banking and DSA are Active, Test Information and export compliance are complete, and nothing a developer can change makes a difference. The accounts reporting it are mostly new, enrolled around October 2026. My case Account enrolled 31 October 2026. Fault since 5 November 2026, every day. Region: Türkiye. No invite email reaches any of my six testers. Beta App Review submit returns the 422 every time. On 13 November I reset everything to rule out my side: removed every tester and both groups, expired the old builds, uploaded a fresh build, added everyone again. Nothing changed. The fresh build is VALID. Its internal state is IN_BETA_TESTING with "automatically notify testers" on, yet its record says the testers were not notified. Its external state is READY_FOR_BETA_SUBMISSION and the submit is refused. Feedback Assistant: FB25540791 (two HAR logs). Developer Support cases 30000005155573 and 30000005989992: only automatic receipts since 4 November, no human reply. Phone support shows as unavailable. Others reporting it https://developer.apple.com/forums/thread/856330 (@Hopeforge): internal invite emails never delivered, testers stay "Invited". Recreating groups, resending and new builds did not help. An App Store Connect Engineer replied there and asked for Feedback Assistant tickets with HAR logs. https://developer.apple.com/forums/thread/857012 (@Kirnuvirsta): tester stuck on "Invited" with no email, Beta App Review submit fails, same on a second app record. FB25399719, case open since 28 October. https://developer.apple.com/forums/thread/856896 (@medlzd, @ganderbite): new internal testers show "Invited" and never get the email, Resend Invite does nothing, on all apps. https://developer.apple.com/forums/thread/856592 (@EmlakBaseDev): Beta App Review submit returns 422 "Please try again later" on three apps since 24 October, build VALID and READY_FOR_BETA_SUBMISSION. https://developer.apple.com/forums/thread/854803 (@SefaAygun, @JanuaryTwelfth): adding a build to external testing fails with "try again later". https://developer.apple.com/forums/thread/854106 (@BWGTrading): new organization account, TestFlight stopped working for all apps on 27 October. If you have this too, please reply with When your account was enrolled, and since when the fault shows Which of the two you have: no invite emails, 422 on Beta App Review, or both Your country or region, to see whether it is tied to one Your Feedback Assistant number (FB...) and Developer Support case ID Anything Apple told you, and above all whether it got fixed, and how If you have not filed a Feedback Assistant ticket yet, please do: steps, a HAR log of the failing request, your App ID. The engineer in thread 856330 asked for exactly that. To Apple Could someone from the App Store Connect or TestFlight team tell us whether this is a known fault in how TestFlight is set up for newly enrolled accounts, and whether each account needs a change on your side? We are paying members who cannot use TestFlight at all, and our support cases stay unanswered for weeks. Thank you.
Replies
18
Boosts
8
Views
830
Activity
41m
Three rejections in a week for errors on the reviewer’s iPad, and a reviewer who couldn’t find the subscription the notes describe
I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing. Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView. What has happened: 30 Oct: submitted. 3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day. 5 Nov: rejected on three points: 5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then; 2.1(b): the reviewer couldn’t find the In-App Purchase; 2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27. We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track. 8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests. So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours. The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved. Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things: When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting? Could every issue be raised in one review, rather than a new one appearing after each fix? Could reviewers read the review notes? For us they answered the question the rejection asked. Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it. The quality of the testing effort has been pretty poor. Thank you.
Replies
5
Boosts
0
Views
208
Activity
1h
Asked to resubmit after being offered bug fix approval, now 7 days in "Waiting for Review" with no response
Hello, We'd appreciate help from the App Review team with our app update. App: AI Video Generator - Bunsy (Apple ID 6762499422) Version: 1.0.13 (build 350) Submission ID: 644c0463-bcb1-44c5-a0bb-b91ccf1860c2 Timeline: Nov 4: submitted version 1.0.13. Nov 12: App Review identified a Guideline 4 issue (Sign in with Apple logo artwork) under Bug Fix Submissions. The message said the issue could be resolved in our next update, and that if we replied, the submission could be approved without resubmitting. Nov 12: we replied the same day and asked to approve the submission as a bug fix, committing to address the issue in the next update. Nov 13: App Review asked us to resubmit anyway. Nov 14: we resubmitted with build 350, which already includes the fix (native Sign in with Apple button). It has been in "Waiting for Review" since then. Nov 16: we requested an expedited review. Nov 19: we contacted App Review about the status (Case ID 103018616391) and have received only the automated confirmation. We followed every instruction we received, and this version has now been waiting for 17 days in total. It fixes a crash on first launch that affects users of the current version. Could you please check whether anything is holding this submission or whether anything else is needed from us? Thank you.
Replies
1
Boosts
0
Views
153
Activity
14h
First app stuck in "Waiting for Review" since Nov 13, after Guideline 2.1 info response
Hello App Review team, My first app, Rental Records, has been in "Waiting for Review" since November 13, 2026, and I'd appreciate it if someone could check whether it needs any action from me. App: Rental Records (iOS 1.0) Apple ID: 6832051224 Platform: iOS, Organization account Timeline: Nov 7: First submission Nov 8: Rejected under Guideline 2.1 (Information Needed) Nov 13: I added everything requested to the App Review Notes (app description, demo logins for both account types, list of external services, regional statement, and a screen recording) and resubmitted. Status has been "Waiting for Review" ever since. What I have already done: Submitted an Expedited App Review request days ago Called Developer Support twice and was told there is no fixed timeline Sent an App Review status inquiry (Case ID: [30000019474998]) The demo accounts work and the notes are complete. I'm happy to provide anything else you need. Thank you for your time.
Replies
1
Boosts
0
Views
143
Activity
14h
Concern Regarding App Review Timeline After Months of Organization Enrollment Delays – Fixit Employee Portal
Hello Apple Developer Community, I am reaching out to seek guidance and express our concern regarding our iOS application, Fixit Employee Portal, which is currently showing "Waiting for Review" in App Store Connect. Application Details: • App Name: Fixit Employee Portal • App Apple ID: 6834282511 • Version: 1.0.4 (Build 2) • Submission Date: November 13, 2026 • Current Status: Waiting for Review Before reaching this stage, our company had already spent several months completing the verification and approval process for our Apple Developer Program organization enrollment. We appreciate Apple's commitment to security, compliance, and quality throughout the enrollment and application review processes. However, after experiencing such an extended enrollment process, we are concerned about the possibility of further significant delays before our application becomes available to our employees. Our application is intended to provide essential employee services to our manpower workforce, including access to employment-related information and company resources. Many of our employees are awaiting its availability on iOS, and timely deployment is important to our daily operations. While we understand that our application was only recently submitted for review, we would sincerely appreciate clarification on the following: Is the current waiting period normal for a newly submitted application under a recently approved organization account? After several months of organization enrollment delays, should we anticipate another extended waiting period for the application review process? Is there a way to confirm that our application has no outstanding requirements that could delay its review? Given our employees' operational need for this application, would an expedited review request be appropriate? We are not requesting that Apple bypass its standard review requirements. We simply hope to understand the expected process and avoid further unnecessary delays after the lengthy organization enrollment experience. We sincerely appreciate the efforts of the Apple Developer and App Review teams and would be grateful for any guidance or assistance. Thank you for your understanding and support. Best regards, Fixit Development Team
Replies
2
Boosts
0
Views
131
Activity
14h
Two Apps Facing Review Issues – No Response from Apple. Could There Be an Issue with My Developer Account
Hello everyone, I'm an independent developer, and I'm currently experiencing review issues with two different apps under the same Apple Developer account. I'm starting to worry that there may be something wrong with my account or the review process. App 1 – Rejected Due to an Account Restriction Mistaken for a Bug My first app was rejected because the reviewer couldn't complete an in-app purchase. However, this wasn't a technical bug. My app has an intentional rule that prevents one Apple ID subscription from being linked to multiple app accounts. The sandbox Apple ID used during review had already been linked to another test account, which triggered this restriction. To make testing easier, I updated our server to remove this restriction for sandbox subscriptions while keeping it unchanged for real users. I explained everything to Apple on November 17 and requested another review. I also requested a phone call on November 18 and submitted an appeal. Unfortunately, I have received no response to any of these requests. App 2 – Rejected and Resubmitted, Still Waiting for Review My second app was also rejected because the reviewer reported that nothing happened after completing an in-app purchase. I resubmitted the app for review on November 19, but it is still waiting for review, and I haven't received any further feedback. My Main Concern Both apps are under the same developer account, and I'm having difficulty getting responses or moving the review process forward. I understand that reviews can take time, but I've already taken steps to address the issues and tried contacting Apple through multiple channels. I'm now concerned that there might be an issue with my developer account affecting the review process. Has anyone experienced similar problems with multiple apps under the same developer account? Is there any way to ask Apple to check whether my account has any review-related restrictions or unusual status? And when App Review messages, appeals, and phone call requests go unanswered, what is the best way to escalate the situation? I would really appreciate any advice from developers who have experienced something similar. Thank you!
Replies
1
Boosts
0
Views
145
Activity
14h