Overview

Post

Replies

Boosts

Views

Activity

App Stuck in “Waiting for Review” – Request for Guidance
Hi Everyone, My app has been stuck in the “Waiting for Review” status on App Store Connect, and there has been no update on the review process. I would like to know if anyone else is experiencing a similar issue or has faced this situation before. Could someone please advise how long the review process usually takes and whether there are any steps I can take to resolve this or get an update from Apple? App Details: App Name: Sammaan Capital: Home Loans Submission Date: Oct 21, 2026 Current Status: Waiting for Review Any suggestions or guidance would be greatly appreciated. Thank you!
0
0
20
23h
Individual enrollment rejected with no reason after 9 attempts (error 202003) — Case 102995833261, asking for Enrollment Operations review
Hi, I have been trying to enroll in the Apple Developer Program as an Individual since August 2026 and would appreciate help from Apple staff on case 102995833261. What happens: Web enrollment (developer.apple.com/enroll): identity, entity type and license agreement all complete, but the final step always returns "Your enrollment in the Apple Developer Program could not be completed at this time." The underlying call submitIndividualEnrollment returns HTTP 406 / resultCode 202003. Nine attempts between 5 Aug and 20 Oct 2026, identical result. Apple Developer app (Mac, version 11.1): Enroll Now is greyed out with "Enrollment through the Apple Developer app is not available for this Apple Account." getEnrollmentEligibility keeps returning eligible (resultCode 0), which contradicts the submission failure. What I have already done: Legal name on the account matches my passport; two-factor authentication on; Australian address (no P.O. box); Australian trusted phone number; the old +86 trusted number removed on 19 Oct; waited several days between attempts. Opened the support case on 14 Oct and followed up on 20 Oct. On 23 Oct I received only the template reply "For one or more reasons, your enrollment … could not be completed. We are unable to continue with your enrollment at this time." with no reason and no verification request. What I am asking: Can someone from Enrollment Operations look at the case and tell me which check is failing? I am ready to verify my identity right now — passport, Australian (ACT) driver's licence, device SEID, or a phone call. The Developer app route is not available for this account, so a secure upload link would be needed. If the account is permanently ineligible, please say so, so I stop retrying. I am an individual developer living in Canberra, Australia, with no previous or pending membership. Thank you.
0
0
11
23h
4.3(a) Spam for my own Color Lines game - what made a difference for you?
Hi! My Color Lines puzzle game was rejected under 4.3(a), and the App Review Board upheld the rejection on appeal. App Review says it cannot give feedback on concepts, so I am asking developers who went through the same thing. About the app: All code, art and sound are my own. No templates, one developer account, and this is the only Lines game on it. I first released this game for Windows in 2003. The iOS version is my own rewrite of it. It has gameplay other Lines games on the App Store do not have: bombs, rainbow balls, three visual themes, and a weekly leaderboard where any player's game can be watched move by move. If you had a 4.3(a) rejection for a game in a classic genre (Lines, solitaire, Tetris-like, match-3), what changed the outcome: a new name and metadata, new gameplay, combining several games in one app, or something else? Thank you.
1
0
25
23h
Unable to Access Contact Us Page to Submit Developer Account Reinstatement Petition
Hello Apple Developer Support and Community, My Apple Developer Program membership has been formally terminated, and I was instructed by Apple to submit a petition through the “Re-instate a Terminated Developer Program Membership” form. Unfortunately, I have been unable to access the Contact Us page required to submit this petition. Whenever I click “Contact Support,” the browser redirects me to: https://developer.apple.com/register/agree/?path=%2Fcontact%2F The page remains completely blank and continues loading indefinitely. The Contact Us form never appears, so I cannot submit my reinstatement request or open a support case through the website. I have already tried multiple browsers, private/incognito browsing, and different networks, but the problem persists. I have attached a screenshot showing the page stuck loading. My previous appeal reference is APL546734. Apple has informed me that I may petition for reinstatement after formal termination, and I have prepared a reinstatement request explaining the corrective changes I have made to my applications. I am not trying to bypass Apple's review process. I simply want to access the correct form and submit my petition through the official process. Could Apple Developer Support please help me with one of the following? Restore access to the Contact Us page or the reinstatement form. Provide an alternative official method to submit my reinstatement petition. Advise me how to open a Developer Support case when the Contact Us page itself does not load. I would sincerely appreciate any assistance, as I want to ensure I can submit my request for consideration. Thank you for your time and help.
1
1
43
23h
Enabling Apple Pay on the Web for merchants in additional countries
We are an acquirer and PSP and we are building our Apple Pay on the Web integration, starting in India. Please tell us what is needed to enable merchants in other countries like Singapore, Hongkong, New Zealand, etc. Does one Platform Integrator ID and one set of certificates cover merchants in all countries? Which country code should the payment request carry for a merchant whose acquirer processes in a different country? Are there per-country requirements for networks, currencies or issuer participation that affect acceptance? Is there a published list of countries where the Registration API model is supported? Is any separate onboarding with Apple required per country?
1
0
29
23h
Repeated App Review Delays – No Response Despite Multiple Support Requests
Hello everyone, I am an independent developer of Bolzplatz – Soccer GM (App ID: 6747684577), and I am hoping someone from Apple's App Review team might be able to help me. Unfortunately, I have been experiencing recurring and unusually long App Review delays over the past several weeks. During a previous submission, I had to wait more than three weeks for a review, despite receiving confirmation that my expedited review request had been approved. Multiple attempts to contact Developer Support did not resolve the situation. Now I am facing similar difficulties again. Since October 16, 2026, I have been trying to get another update reviewed. Concerned about another prolonged delay, I submitted two replacement builds, hoping to avoid a possible issue with the review process. I understand that replacing a build may reset the review queue. However, my previous experience has left me genuinely concerned that something might not be working correctly. What makes the situation especially frustrating is the lack of communication. I have contacted Apple Developer Support several times, including messages on October 19 and 20, and submitted another support request on October 22. Unfortunately, I have not received a substantive response. I also submitted formal complaints on September 29 and October 21 regarding these recurring issues. As an independent developer, I continuously invest considerable time and resources into improving my game, fixing bugs, and providing new features for my players. I fully respect Apple's review process and understand the importance of thorough app reviews. However, repeated delays without meaningful communication make it extremely difficult to plan updates and support my players. My main concern is whether there might be an underlying technical or administrative issue affecting my application's review process. Could someone from the Apple App Review team please help investigate this situation or advise me on how to get it properly escalated? I would sincerely appreciate any assistance or guidance. Thank you very much for your time! Kind regards,Felix DämmrichDeveloper – Bolzplatz – Soccer GM
4
1
114
1d
How can I disable sharing age range with an app
I am still in development phase of an app, I integrated AgeRangeAPI and shared age range with my app. When I go to system settings > profile > personal information > Age Range for Apps , I see the app and it says "Shared", but I can't unshare anymore. I can unshare globally but now per app. I know the AgeRangeAPI can be tested from the Developer > Account > Manage, but that kind of testing skips the native UI I want to test again full scenario to see what real users will experience, I want to see the real UI of sharing again.
4
0
75
1d
Regression: AxisValueLabel anchor parameter ignores .topLeading on iOS 27
Hello Apple SwiftUI / Swift Charts Engineering Team, I am writing to report a layout regression regarding Swift Charts in iOS 27. The anchor property on AxisValueLabel has stopped honoring the .topLeading layout coordinate, whereas it functions perfectly in iOS 26. Bug Description: To prevent the first label on a bottom X-axis from clipping past the left screen edge, a .topLeading anchor is applied. In iOS 27, this specific anchor alignment is completely ignored. The chart falls back to a standard top-center alignment, causing the initial boundary label to clip off-screen. Core Code Snippet to Reproduce: struct XAxisAnchorBugView: View { let dates = [ Calendar.current.date(from: DateComponents(year: 2026, month: 10, day: 1))!, Calendar.current.date(from: DateComponents(year: 2026, month: 10, day: 2))! ] var body: some View { Chart(dates, id: .self) { date in LineMark(x: .value("Date", date), y: .value("Value", 100)) } .frame(height: 300) .padding() .chartXAxis { AxisMarks(preset: .aligned, position: .bottom, values: .stride(by: .day, count: 1)) { value in AxisTick() let currentAnchor: UnitPoint = { guard let currentDate = value.as(Date.self) else { return .top } // BUG: .topLeading layout anchor parameter is completely ignored on iOS 27 return (currentDate == dates.first) ? .topLeading : .top }() AxisValueLabel(format: .dateTime.month(.abbreviated).day(), anchor: currentAnchor) } } } } Steps to Reproduce: Render an X-axis with a .bottom position. Assign anchor: .topLeading strictly to the first axis element's label. Run on an iOS 26 simulator (the first label anchors its top-left corner correctly, preventing edge clipping). Run on an iOS 27 simulator (the .topLeading anchor is ignored, reverting to standard top-center alignment). Expected Behavior: AxisValueLabel should position its layout bounding box using the .topLeading anchor point when specified. Actual Behavior: The layout engine ignores the .topLeading parameter on iOS 27, causing the boundary text to shift left and clip. Attachments: I have attached Xcode Simulator screenshots demonstrating this regression: Best regards, Soumyajit Das
2
0
58
1d
Regression: AxisValueLabel multiLabelAlignment parameter ignored in iOS 27
Hello Apple SwiftUI / Swift Charts Engineering Team, I am writing to report a layout regression regarding Swift Charts in iOS 27. The multiLabelAlignment property on AxisValueLabel has stopped working as expected, whereas it functions perfectly in iOS 26. Bug Description: When configuring custom string values within AxisMarks using AxisValueLabel with multiLabelAlignment: .trailing, the alignment configuration is completely ignored on iOS 27. Labels fail to align text properly to the trailing edge, causing rendering layout issues for multi-line or custom text labels on the Y-axis. This exact same implementation compiles and aligns correctly on iOS 26. Code Snippet to Reproduce: swift struct YAxisAlignmentBugView: View { // data points to render the chart frame let data = [(date: Date(), revenue: 3000.0), (date: Date().addingTimeInterval(10000), revenue: 4000.0)] var body: some View { Chart(data, id: .date) { item in LineMark(x: .value("Date", item.date), y: .value("Revenue", item.revenue)) } .frame(height: 300) .padding() .chartYAxis { AxisMarks(preset: .aligned, position: .trailing, values: [12.0, 600.0, 3000.0, 6000.0]) { value in if let revenue = value.as(Double.self) { // BUG: multiLabelAlignment: .trailing is completely ignored on iOS 27 AxisValueLabel("y-(Int(revenue))", anchor: .leading, multiLabelAlignment: .trailing) } } } } } Steps to Reproduce: Render a Swift Chart containing a .chartYAxis configuration with position: .trailing. Pass a string directly using AxisValueLabel(customText, anchor: .leading, multiLabelAlignment: .trailing). Run the application on an iOS 26 simulator (text aligns properly to the trailing edge). Run the identical application code on an iOS 27 simulator. Expected Behavior: The text inside the AxisValueLabel should honor the multiLabelAlignment: .trailing parameter and align the text strings flush right. Actual Behavior: The multiLabelAlignment layout modifier is ignored on iOS 27, resulting in unexpected default left-alignment of the text strings. Attachments: I have attached screenshots from the Xcode Simulator demonstrating the regression: Please let me know if you need any further diagnostic details. Best regards, Soumyajit Das
2
0
42
1d
iOS 27.0.1 child device does not enforce third-party ManagedSettings shields when the parent device runs iOS 18.7.1 (system Screen Time works)
Setup Parent device: FamilyActivityPicker with a selection created as FamilyActivitySelection(includeEntireCategory: true). The parent selects apps for an always-on block list. The selection is encoded with PropertyListEncoder and sent to our server. Child device: authorized with AuthorizationCenter.shared.requestAuthorization(for: .child). It receives the selection, decodes it, and immediately applies its application tokens. The shield stays on all day, with no schedule: let selection = try PropertyListDecoder().decode(FamilyActivitySelection.self, from: data) ManagedSettingsStore(named: .appBlock).shield.applications = selection.applicationTokensObserved Cases A and B use the same two physical devices with the parent and child roles swapped. In all cases, the Family Sharing group uses legacy Screen Time, because not every device is on iOS 27 and the redesigned Screen Time is not available. CaseParentChildOur app's shieldSystem Screen Time (set by parent)AiOS 27.0.1iOS 18.7.1BlocksBlocksBiOS 18.7.1iOS 27.0.1Does not blockBlocksCiOS 18.7.1iOS 18.7.1BlocksBlocksQuestions Is this a known issue in iOS 27.0.x? Could it be related to issue number 175437403 ("Screen Time restrictions might not apply to child accounts despite being configured"), which the iOS 27 release notes list as fixed? Should tokens selected on an iOS 18 parent device be enforced on an iOS 27 child device? Is there a workaround, or a way to detect that a shield was applied but is not being enforced?
1
0
38
1d
Apple Pay on the Web: merchant-hosted payment page, Register Merchant API, eligibility checks, and who decrypts the token
We are an acquirer and PSP with our own payment gateway. Merchants can either: Use an Apple Pay payment page hosted by us, or Host their own payment page and submit payment data to us via server-to-server APIs. We are currently implementing Apple Pay on the Web using the Platform Integrator model. The acquirer-hosted payment page flow is clear to us, but we have a few questions regarding merchant-hosted payment pages. Our current understanding (please correct us if any of this is incorrect) We register each merchant using the Web Merchant Registration API as a Platform Integrator, with a unique partnerInternalMerchantIdentifier. Merchants do not have their own Apple Developer accounts. For merchant-hosted payment pages, the merchant's checkout domain is provided in domainNames. The domain verification file is downloaded from our Apple Developer account (Platform Integrator account), and the merchant hosts that file under the /.well-known/ path on their domain. The merchant registration created through the Web Merchant Registration API is then used for Apple Pay eligibility checks and merchant validation. Questions: Domain registration For a merchant-hosted payment page, is it correct to register the merchant's domain against that merchant's partnerInternalMerchantIdentifier registration? Verification file When onboarding multiple merchants: Is the same domain association file used across all merchant domains? Or is a unique verification file generated per merchant registration? Eligibility checks and Apple Pay button The "Supporting Apple Pay on Third-Party Browsers" documentation (Scenario 3) suggests that a payment service provider may provide a JavaScript library that loads apple-pay-sdk.js for merchants. For merchant-hosted pages, is it supported and recommended for the PSP/platform integrator to provide a thin wrapper library around: canMakePayments() applePayCapabilities() Apple Pay button rendering Session creation Or is Apple’s preferred approach that the merchant's checkout page interacts directly with Apple Pay JS APIs? PSP/acquirer decrypts the payment token If the PSP/acquirer is responsible for token decryption, we understand that encryptTo should be set to the Platform Integrator identifier. For merchant-hosted payment pages, are there any additional requirements beyond domain registration and merchant validation? Merchant decrypts the payment token We would also like to support a model where the merchant decrypts Apple Pay tokens directly. In that case, our understanding is that encryptTo must reference the merchant's identifier rather than the Platform Integrator identifier. Is that understanding correct, and are there any additional onboarding or registration requirements for that model? Merchant validation For merchant-hosted checkout pages, what is the expected implementation pattern for onvalidatemerchant? Specifically: Should the merchant's frontend send the validationURL to the PSP/platform integrator backend, which then performs merchant validation with Apple and returns the merchant session? Or is a different flow expected when using the Platform Integrator model? Any clarification or guidance would be greatly appreciated. Thank you.
1
0
31
1d
Are Kosovo banks supported for App Store payouts? Alternatives for developers in Kosovo?
Hi everyone, I'm an individual developer based in Kosovo and I'm setting up the Paid Apps Agreement in App Store Connect. Kosovo appears in the Bank Country list (currency EUR, IBAN starting with XK), but Apple's bank lookup can't find my bank (TEB Sh.A., SWIFT TEBKXKPR) by SWIFT code or by the bank code from the IBAN. My questions: Are Kosovo banks actually supported for App Store payouts? Has anyone in Kosovo received payments from Apple successfully? If so, which bank (Raiffeisen Bank Kosovo, ProCredit Bank, NLB Banka, BKT...) and which Bank/Branch Number did Apple accept? If Kosovo banks don't work, what are the alternatives? Does a bank account in a neighbouring country (Albania, North Macedonia) work with Apple? Do online accounts such as Wise or Revolut with a European IBAN work for Apple payouts? I've already opened a case with Apple Finance and I'm waiting for their reply, but any first-hand experience would help a lot. Thank you!
2
1
51
1d
8 Days in “Waiting for Review” After Resubmission — No Response from Apple Developer Support
Hello Apple App Review Team and fellow developers, I am an independent developer working on my first public iOS release, Marque: Car Collection, and I am becoming increasingly concerned about the lack of progress and communication regarding my submission. Submission details: App: Marque: Car Collection Bundle ID: app.marque.collect Version: 1.1.0 (Build 24) Resubmitted: October 14, 2026 Current status: Waiting for Review Time waiting: 8 days Submission ID: b37a9421-6980-4708-a396-dd33df072f14 Our previous submission was rejected under Guideline 5.1.2(i), related to App Tracking Transparency. We addressed the reported issue, implemented the ATT authorization flow, updated our App Privacy disclosures, uploaded a corrected build, and provided detailed Review Notes explaining how to verify the changes. The current submission also includes our Marque+ monthly and annual subscription products. Eight days have now passed, and the submission has not moved to “In Review”. During this period: I contacted Apple Developer Support to ask whether additional information was required. I raised the issue on the Apple Developer Forums. I checked App Store Connect regularly for messages or outstanding actions. Unfortunately, I have not received a meaningful response or explanation, and no additional information has been requested. I understand that some submissions require additional verification, particularly first-time releases. I respect the review process and am fully prepared to cooperate with any requirements. However, the lack of communication makes it extremely difficult to plan a release or understand whether the submission is progressing normally. Could someone from the Apple App Review team please clarify: Is this submission correctly queued for review? Is there any outstanding issue or verification requirement that has not been communicated? Can the current submission or existing support request be escalated for a status check? Is any further action required from my side? I am not requesting an exception to the App Review Guidelines. I am simply asking for visibility into the status of a submission that has remained untouched for more than a week. I would sincerely appreciate a response from an Apple representative. Thank you, Marque Development Team
1
0
30
1d
How long should I wait for an App Review Board appeal response before following up? And where?
Hi everyone, I submitted an appeal to the App Review Board on October 6, 2026, regarding a rejection. It's now been 16 days, and I haven't received a response yet. I understand that the appeal process can take some time, and I'm not necessarily looking to speed things up. I'm just wondering what the typical waiting time is based on other developers' experiences. For those who have gone through the App Review Board appeal process: How long did it take for you to receive a response? After how many days without a response would you recommend following up? If a follow-up is necessary, what's the most appropriate contact channel? Apple Developer Support, App Review Contact, or somewhere else? I'd appreciate any advice or experiences you could share. Thanks in advance!
1
0
37
1d
App Review Delayed Again After Addressing All Rejection Issues — Waiting for Review for 7+ Days
Hi everyone, I'm looking for advice from developers who have experienced prolonged App Review delays, and hopefully some help from someone at Apple who can look into this situation. My app, Parozo: Restaurant POS & KOT (iOS version 1.0.0), was initially reviewed by Apple, and I received feedback regarding several guidelines: Guidelines 2.3.10 and 2.3.3: App Store screenshots and accurate representation of the app. Guideline 3.1.1: In-app purchases and business subscription functionality. Guideline 4.5.4: Push notification permissions. I carefully reviewed Apple's feedback and made the requested changes. I replaced the screenshots with actual iOS app screenshots, made push notifications optional, and removed plan, pricing, registration, and renewal screens and purchase links from the iOS app to address the subscription-related concerns. I then submitted the updated build 1.0.0 (7) for review on October 16, 2026. However, the submission is still showing “Waiting for Review,” and more than seven days have now passed without the new review process starting or any further communication. I've also contacted Apple Developer Support multiple times regarding these delays. Unfortunately, I haven't received a meaningful response to my previous requests. I submitted another support request yesterday, but the issue remains unresolved. My latest App Review support case is 103003613618. I completely understand that app reviews take time and that Apple must carefully evaluate every submission. I'm not asking for the review guidelines to be bypassed or for special treatment. I have addressed the issues identified in the previous review and simply want to understand why the corrected submission is still waiting and whether any further action is needed from my side. As an independent developer, these repeated delays and the lack of communication make it difficult to plan a product launch, particularly after spending time addressing the feedback provided by App Review. Has anyone experienced a similar situation after fixing all the issues identified by Apple? Did your resubmission eventually move into review, and is there an effective way to get a status update when repeated support requests receive no response? I'd especially appreciate guidance from anyone who has successfully escalated a similar case, or from an Apple representative who can direct me to the appropriate team. Thank you for your time and help.
1
0
32
1d
Resubmission stuck in "Waiting for Review" for 13 days after resolving a Guideline 2.1 note — how to get it looked at?
Our app was reviewed on 8 October and returned under Guideline 2.1 (Information Needed) because the reviewer could not sign in with the demo account. The cause was on our side and was fixed the same evening: the review account now uses a fixed verification code, the App Review notes were updated with step-by-step instructions, we replied in the Resolution Center, and we resubmitted on 9 October. Since then the submission has shown Waiting for Review with no further contact — 13 days as of today. The first cycle of the same submission also waited eight days before review. We requested an expedited review on 14 October and have had no reply to that either. Submission ID: 9f09ed47-0ac0-45d1-8b6c-af9c05c8e3bd. We have verified the demo sign-in end to end against production and are available at any time if a reviewer needs anything. Two questions: Is there anything about a resubmission after a 2.1 note that places it in a different or slower queue than a new submission? Would cancelling and resubmitting the identical build as a new submission be the right move at this point, or does that risk losing a place in an escalated queue we can't see? Thanks for any guidance.
1
0
47
1d
Pending Termination Notice (Section 3.2(f)) received on 24 September, with no response to our appeal or follow-ups for 28 days
Hello everyone, On 24 September, our developer account received a Pending Termination Notice citing Section 3.2(f). We appealed immediately and have followed up repeatedly since. It has now been 28 days, and we have not received a single response, not even an acknowledgement. I’m posting here because we have run out of other options, and because I want to ask a plain question: who at Apple is responsible for this? What the notice told us, and what it didn’t The notice quotes a clause from the agreement. It does not say which of our apps is involved, what exactly was found, or what we are expected to fix. We can only guess at what Apple’s review found. Our best guess is this. We built a white-labelled version of our product for a client and hosted it on our developer account, because the client’s own developer account was still waiting on DUNS approval. We always planned to move it to the client’s account as soon as theirs was ready. If that is the issue, we are willing to transfer the app right away and make any other changes needed. But we can’t tell whether that is the issue, or whether there is something else we haven’t even thought of. Without an explanation, we can’t fix anything. What 28 days of silence has cost us Our entire team is at a standstill, because we can’t plan releases, updates or new work while the account’s future is uncertain. Our client is waiting, and so are our users. For a small company, every week of this puts salaries, contracts and relationships at risk. What we are asking Apple for A response to our appeal, from a person, with a clear owner for this case. A specific explanation of the finding, meaning which app and which part of the clause, not only the clause text. A fair, reasonable window to fix the issue, including moving the client’s app to their own account, before any termination is considered. A timeline, so we can tell our team and clients what to expect. Apple sets the rules for its platform, and we accept that. But the people who build on that platform put years of work and a lot of passion into their products. A process that threatens to end a business and then goes silent, with no explanation and nobody taking responsibility, is hard to defend as fair. If an action carries consequences this serious, someone should own the decision and be able to explain it. If any Apple representative reads this, or if anyone in the community has been through the same situation and found a way forward, we would be grateful to hear from you. Thank you.
2
0
64
1d
First release stuck in Waiting for Review since October 17
Our first iOS release, KanChinese: Learn Chinese HSK (Apple ID 6819210106), version 1.13.34, was first submitted on October 7, 2026. It was reviewed on October 17 and we fixed every point raised (camera and photo permission text, account deletion, with a screen recording in the review notes). We resubmitted the same day, and it has been in Waiting for Review since October 17. We opened support case 102997347616 but have not received an update. Is there anything we need to provide? Thank you.
1
0
23
1d
First app stuck in "Waiting for Review" since October 14 – expedite granted, review never started
Hello, Our first app, Hegemonia: War Strategy Game (Apple ID 6822418708), has been waiting for its first review since October 14 and has never reached "In Review". We made a mistake: we withdrew and resubmitted twice (October 18 to change the build, October 22 to include the first in-app purchases with the version). The current submission is from October 22 and has 9 items: version 1.0 (build 37), 6 consumable in-app purchases and 2 non-renewing subscriptions. We will not withdraw it again. An expedited review was granted on October 22, and we opened a support case (103004844776). Agreements, tax, banking and the DSA trader status are all active, and our TestFlight external builds were approved. Is there anything on our side that could be holding the submission, or anything else we should do? Thank you.
1
0
29
1d
App Stuck in “Waiting for Review” – Request for Guidance
Hi Everyone, My app has been stuck in the “Waiting for Review” status on App Store Connect, and there has been no update on the review process. I would like to know if anyone else is experiencing a similar issue or has faced this situation before. Could someone please advise how long the review process usually takes and whether there are any steps I can take to resolve this or get an update from Apple? App Details: App Name: Sammaan Capital: Home Loans Submission Date: Oct 21, 2026 Current Status: Waiting for Review Any suggestions or guidance would be greatly appreciated. Thank you!
Replies
0
Boosts
0
Views
20
Activity
23h
Individual enrollment rejected with no reason after 9 attempts (error 202003) — Case 102995833261, asking for Enrollment Operations review
Hi, I have been trying to enroll in the Apple Developer Program as an Individual since August 2026 and would appreciate help from Apple staff on case 102995833261. What happens: Web enrollment (developer.apple.com/enroll): identity, entity type and license agreement all complete, but the final step always returns "Your enrollment in the Apple Developer Program could not be completed at this time." The underlying call submitIndividualEnrollment returns HTTP 406 / resultCode 202003. Nine attempts between 5 Aug and 20 Oct 2026, identical result. Apple Developer app (Mac, version 11.1): Enroll Now is greyed out with "Enrollment through the Apple Developer app is not available for this Apple Account." getEnrollmentEligibility keeps returning eligible (resultCode 0), which contradicts the submission failure. What I have already done: Legal name on the account matches my passport; two-factor authentication on; Australian address (no P.O. box); Australian trusted phone number; the old +86 trusted number removed on 19 Oct; waited several days between attempts. Opened the support case on 14 Oct and followed up on 20 Oct. On 23 Oct I received only the template reply "For one or more reasons, your enrollment … could not be completed. We are unable to continue with your enrollment at this time." with no reason and no verification request. What I am asking: Can someone from Enrollment Operations look at the case and tell me which check is failing? I am ready to verify my identity right now — passport, Australian (ACT) driver's licence, device SEID, or a phone call. The Developer app route is not available for this account, so a secure upload link would be needed. If the account is permanently ineligible, please say so, so I stop retrying. I am an individual developer living in Canberra, Australia, with no previous or pending membership. Thank you.
Replies
0
Boosts
0
Views
11
Activity
23h
4.3(a) Spam for my own Color Lines game - what made a difference for you?
Hi! My Color Lines puzzle game was rejected under 4.3(a), and the App Review Board upheld the rejection on appeal. App Review says it cannot give feedback on concepts, so I am asking developers who went through the same thing. About the app: All code, art and sound are my own. No templates, one developer account, and this is the only Lines game on it. I first released this game for Windows in 2003. The iOS version is my own rewrite of it. It has gameplay other Lines games on the App Store do not have: bombs, rainbow balls, three visual themes, and a weekly leaderboard where any player's game can be watched move by move. If you had a 4.3(a) rejection for a game in a classic genre (Lines, solitaire, Tetris-like, match-3), what changed the outcome: a new name and metadata, new gameplay, combining several games in one app, or something else? Thank you.
Replies
1
Boosts
0
Views
25
Activity
23h
Unable to Access Contact Us Page to Submit Developer Account Reinstatement Petition
Hello Apple Developer Support and Community, My Apple Developer Program membership has been formally terminated, and I was instructed by Apple to submit a petition through the “Re-instate a Terminated Developer Program Membership” form. Unfortunately, I have been unable to access the Contact Us page required to submit this petition. Whenever I click “Contact Support,” the browser redirects me to: https://developer.apple.com/register/agree/?path=%2Fcontact%2F The page remains completely blank and continues loading indefinitely. The Contact Us form never appears, so I cannot submit my reinstatement request or open a support case through the website. I have already tried multiple browsers, private/incognito browsing, and different networks, but the problem persists. I have attached a screenshot showing the page stuck loading. My previous appeal reference is APL546734. Apple has informed me that I may petition for reinstatement after formal termination, and I have prepared a reinstatement request explaining the corrective changes I have made to my applications. I am not trying to bypass Apple's review process. I simply want to access the correct form and submit my petition through the official process. Could Apple Developer Support please help me with one of the following? Restore access to the Contact Us page or the reinstatement form. Provide an alternative official method to submit my reinstatement petition. Advise me how to open a Developer Support case when the Contact Us page itself does not load. I would sincerely appreciate any assistance, as I want to ensure I can submit my request for consideration. Thank you for your time and help.
Replies
1
Boosts
1
Views
43
Activity
23h
Enabling Apple Pay on the Web for merchants in additional countries
We are an acquirer and PSP and we are building our Apple Pay on the Web integration, starting in India. Please tell us what is needed to enable merchants in other countries like Singapore, Hongkong, New Zealand, etc. Does one Platform Integrator ID and one set of certificates cover merchants in all countries? Which country code should the payment request carry for a merchant whose acquirer processes in a different country? Are there per-country requirements for networks, currencies or issuer participation that affect acceptance? Is there a published list of countries where the Registration API model is supported? Is any separate onboarding with Apple required per country?
Replies
1
Boosts
0
Views
29
Activity
23h
Repeated App Review Delays – No Response Despite Multiple Support Requests
Hello everyone, I am an independent developer of Bolzplatz – Soccer GM (App ID: 6747684577), and I am hoping someone from Apple's App Review team might be able to help me. Unfortunately, I have been experiencing recurring and unusually long App Review delays over the past several weeks. During a previous submission, I had to wait more than three weeks for a review, despite receiving confirmation that my expedited review request had been approved. Multiple attempts to contact Developer Support did not resolve the situation. Now I am facing similar difficulties again. Since October 16, 2026, I have been trying to get another update reviewed. Concerned about another prolonged delay, I submitted two replacement builds, hoping to avoid a possible issue with the review process. I understand that replacing a build may reset the review queue. However, my previous experience has left me genuinely concerned that something might not be working correctly. What makes the situation especially frustrating is the lack of communication. I have contacted Apple Developer Support several times, including messages on October 19 and 20, and submitted another support request on October 22. Unfortunately, I have not received a substantive response. I also submitted formal complaints on September 29 and October 21 regarding these recurring issues. As an independent developer, I continuously invest considerable time and resources into improving my game, fixing bugs, and providing new features for my players. I fully respect Apple's review process and understand the importance of thorough app reviews. However, repeated delays without meaningful communication make it extremely difficult to plan updates and support my players. My main concern is whether there might be an underlying technical or administrative issue affecting my application's review process. Could someone from the Apple App Review team please help investigate this situation or advise me on how to get it properly escalated? I would sincerely appreciate any assistance or guidance. Thank you very much for your time! Kind regards,Felix DämmrichDeveloper – Bolzplatz – Soccer GM
Replies
4
Boosts
1
Views
114
Activity
1d
How can I disable sharing age range with an app
I am still in development phase of an app, I integrated AgeRangeAPI and shared age range with my app. When I go to system settings > profile > personal information > Age Range for Apps , I see the app and it says "Shared", but I can't unshare anymore. I can unshare globally but now per app. I know the AgeRangeAPI can be tested from the Developer > Account > Manage, but that kind of testing skips the native UI I want to test again full scenario to see what real users will experience, I want to see the real UI of sharing again.
Replies
4
Boosts
0
Views
75
Activity
1d
Regression: AxisValueLabel anchor parameter ignores .topLeading on iOS 27
Hello Apple SwiftUI / Swift Charts Engineering Team, I am writing to report a layout regression regarding Swift Charts in iOS 27. The anchor property on AxisValueLabel has stopped honoring the .topLeading layout coordinate, whereas it functions perfectly in iOS 26. Bug Description: To prevent the first label on a bottom X-axis from clipping past the left screen edge, a .topLeading anchor is applied. In iOS 27, this specific anchor alignment is completely ignored. The chart falls back to a standard top-center alignment, causing the initial boundary label to clip off-screen. Core Code Snippet to Reproduce: struct XAxisAnchorBugView: View { let dates = [ Calendar.current.date(from: DateComponents(year: 2026, month: 10, day: 1))!, Calendar.current.date(from: DateComponents(year: 2026, month: 10, day: 2))! ] var body: some View { Chart(dates, id: .self) { date in LineMark(x: .value("Date", date), y: .value("Value", 100)) } .frame(height: 300) .padding() .chartXAxis { AxisMarks(preset: .aligned, position: .bottom, values: .stride(by: .day, count: 1)) { value in AxisTick() let currentAnchor: UnitPoint = { guard let currentDate = value.as(Date.self) else { return .top } // BUG: .topLeading layout anchor parameter is completely ignored on iOS 27 return (currentDate == dates.first) ? .topLeading : .top }() AxisValueLabel(format: .dateTime.month(.abbreviated).day(), anchor: currentAnchor) } } } } Steps to Reproduce: Render an X-axis with a .bottom position. Assign anchor: .topLeading strictly to the first axis element's label. Run on an iOS 26 simulator (the first label anchors its top-left corner correctly, preventing edge clipping). Run on an iOS 27 simulator (the .topLeading anchor is ignored, reverting to standard top-center alignment). Expected Behavior: AxisValueLabel should position its layout bounding box using the .topLeading anchor point when specified. Actual Behavior: The layout engine ignores the .topLeading parameter on iOS 27, causing the boundary text to shift left and clip. Attachments: I have attached Xcode Simulator screenshots demonstrating this regression: Best regards, Soumyajit Das
Replies
2
Boosts
0
Views
58
Activity
1d
Regression: AxisValueLabel multiLabelAlignment parameter ignored in iOS 27
Hello Apple SwiftUI / Swift Charts Engineering Team, I am writing to report a layout regression regarding Swift Charts in iOS 27. The multiLabelAlignment property on AxisValueLabel has stopped working as expected, whereas it functions perfectly in iOS 26. Bug Description: When configuring custom string values within AxisMarks using AxisValueLabel with multiLabelAlignment: .trailing, the alignment configuration is completely ignored on iOS 27. Labels fail to align text properly to the trailing edge, causing rendering layout issues for multi-line or custom text labels on the Y-axis. This exact same implementation compiles and aligns correctly on iOS 26. Code Snippet to Reproduce: swift struct YAxisAlignmentBugView: View { // data points to render the chart frame let data = [(date: Date(), revenue: 3000.0), (date: Date().addingTimeInterval(10000), revenue: 4000.0)] var body: some View { Chart(data, id: .date) { item in LineMark(x: .value("Date", item.date), y: .value("Revenue", item.revenue)) } .frame(height: 300) .padding() .chartYAxis { AxisMarks(preset: .aligned, position: .trailing, values: [12.0, 600.0, 3000.0, 6000.0]) { value in if let revenue = value.as(Double.self) { // BUG: multiLabelAlignment: .trailing is completely ignored on iOS 27 AxisValueLabel("y-(Int(revenue))", anchor: .leading, multiLabelAlignment: .trailing) } } } } } Steps to Reproduce: Render a Swift Chart containing a .chartYAxis configuration with position: .trailing. Pass a string directly using AxisValueLabel(customText, anchor: .leading, multiLabelAlignment: .trailing). Run the application on an iOS 26 simulator (text aligns properly to the trailing edge). Run the identical application code on an iOS 27 simulator. Expected Behavior: The text inside the AxisValueLabel should honor the multiLabelAlignment: .trailing parameter and align the text strings flush right. Actual Behavior: The multiLabelAlignment layout modifier is ignored on iOS 27, resulting in unexpected default left-alignment of the text strings. Attachments: I have attached screenshots from the Xcode Simulator demonstrating the regression: Please let me know if you need any further diagnostic details. Best regards, Soumyajit Das
Replies
2
Boosts
0
Views
42
Activity
1d
iOS 27.0.1 child device does not enforce third-party ManagedSettings shields when the parent device runs iOS 18.7.1 (system Screen Time works)
Setup Parent device: FamilyActivityPicker with a selection created as FamilyActivitySelection(includeEntireCategory: true). The parent selects apps for an always-on block list. The selection is encoded with PropertyListEncoder and sent to our server. Child device: authorized with AuthorizationCenter.shared.requestAuthorization(for: .child). It receives the selection, decodes it, and immediately applies its application tokens. The shield stays on all day, with no schedule: let selection = try PropertyListDecoder().decode(FamilyActivitySelection.self, from: data) ManagedSettingsStore(named: .appBlock).shield.applications = selection.applicationTokensObserved Cases A and B use the same two physical devices with the parent and child roles swapped. In all cases, the Family Sharing group uses legacy Screen Time, because not every device is on iOS 27 and the redesigned Screen Time is not available. CaseParentChildOur app's shieldSystem Screen Time (set by parent)AiOS 27.0.1iOS 18.7.1BlocksBlocksBiOS 18.7.1iOS 27.0.1Does not blockBlocksCiOS 18.7.1iOS 18.7.1BlocksBlocksQuestions Is this a known issue in iOS 27.0.x? Could it be related to issue number 175437403 ("Screen Time restrictions might not apply to child accounts despite being configured"), which the iOS 27 release notes list as fixed? Should tokens selected on an iOS 18 parent device be enforced on an iOS 27 child device? Is there a workaround, or a way to detect that a shield was applied but is not being enforced?
Replies
1
Boosts
0
Views
38
Activity
1d
Apple Pay on the Web: merchant-hosted payment page, Register Merchant API, eligibility checks, and who decrypts the token
We are an acquirer and PSP with our own payment gateway. Merchants can either: Use an Apple Pay payment page hosted by us, or Host their own payment page and submit payment data to us via server-to-server APIs. We are currently implementing Apple Pay on the Web using the Platform Integrator model. The acquirer-hosted payment page flow is clear to us, but we have a few questions regarding merchant-hosted payment pages. Our current understanding (please correct us if any of this is incorrect) We register each merchant using the Web Merchant Registration API as a Platform Integrator, with a unique partnerInternalMerchantIdentifier. Merchants do not have their own Apple Developer accounts. For merchant-hosted payment pages, the merchant's checkout domain is provided in domainNames. The domain verification file is downloaded from our Apple Developer account (Platform Integrator account), and the merchant hosts that file under the /.well-known/ path on their domain. The merchant registration created through the Web Merchant Registration API is then used for Apple Pay eligibility checks and merchant validation. Questions: Domain registration For a merchant-hosted payment page, is it correct to register the merchant's domain against that merchant's partnerInternalMerchantIdentifier registration? Verification file When onboarding multiple merchants: Is the same domain association file used across all merchant domains? Or is a unique verification file generated per merchant registration? Eligibility checks and Apple Pay button The "Supporting Apple Pay on Third-Party Browsers" documentation (Scenario 3) suggests that a payment service provider may provide a JavaScript library that loads apple-pay-sdk.js for merchants. For merchant-hosted pages, is it supported and recommended for the PSP/platform integrator to provide a thin wrapper library around: canMakePayments() applePayCapabilities() Apple Pay button rendering Session creation Or is Apple’s preferred approach that the merchant's checkout page interacts directly with Apple Pay JS APIs? PSP/acquirer decrypts the payment token If the PSP/acquirer is responsible for token decryption, we understand that encryptTo should be set to the Platform Integrator identifier. For merchant-hosted payment pages, are there any additional requirements beyond domain registration and merchant validation? Merchant decrypts the payment token We would also like to support a model where the merchant decrypts Apple Pay tokens directly. In that case, our understanding is that encryptTo must reference the merchant's identifier rather than the Platform Integrator identifier. Is that understanding correct, and are there any additional onboarding or registration requirements for that model? Merchant validation For merchant-hosted checkout pages, what is the expected implementation pattern for onvalidatemerchant? Specifically: Should the merchant's frontend send the validationURL to the PSP/platform integrator backend, which then performs merchant validation with Apple and returns the merchant session? Or is a different flow expected when using the Platform Integrator model? Any clarification or guidance would be greatly appreciated. Thank you.
Replies
1
Boosts
0
Views
31
Activity
1d
Are Kosovo banks supported for App Store payouts? Alternatives for developers in Kosovo?
Hi everyone, I'm an individual developer based in Kosovo and I'm setting up the Paid Apps Agreement in App Store Connect. Kosovo appears in the Bank Country list (currency EUR, IBAN starting with XK), but Apple's bank lookup can't find my bank (TEB Sh.A., SWIFT TEBKXKPR) by SWIFT code or by the bank code from the IBAN. My questions: Are Kosovo banks actually supported for App Store payouts? Has anyone in Kosovo received payments from Apple successfully? If so, which bank (Raiffeisen Bank Kosovo, ProCredit Bank, NLB Banka, BKT...) and which Bank/Branch Number did Apple accept? If Kosovo banks don't work, what are the alternatives? Does a bank account in a neighbouring country (Albania, North Macedonia) work with Apple? Do online accounts such as Wise or Revolut with a European IBAN work for Apple payouts? I've already opened a case with Apple Finance and I'm waiting for their reply, but any first-hand experience would help a lot. Thank you!
Replies
2
Boosts
1
Views
51
Activity
1d
8 Days in “Waiting for Review” After Resubmission — No Response from Apple Developer Support
Hello Apple App Review Team and fellow developers, I am an independent developer working on my first public iOS release, Marque: Car Collection, and I am becoming increasingly concerned about the lack of progress and communication regarding my submission. Submission details: App: Marque: Car Collection Bundle ID: app.marque.collect Version: 1.1.0 (Build 24) Resubmitted: October 14, 2026 Current status: Waiting for Review Time waiting: 8 days Submission ID: b37a9421-6980-4708-a396-dd33df072f14 Our previous submission was rejected under Guideline 5.1.2(i), related to App Tracking Transparency. We addressed the reported issue, implemented the ATT authorization flow, updated our App Privacy disclosures, uploaded a corrected build, and provided detailed Review Notes explaining how to verify the changes. The current submission also includes our Marque+ monthly and annual subscription products. Eight days have now passed, and the submission has not moved to “In Review”. During this period: I contacted Apple Developer Support to ask whether additional information was required. I raised the issue on the Apple Developer Forums. I checked App Store Connect regularly for messages or outstanding actions. Unfortunately, I have not received a meaningful response or explanation, and no additional information has been requested. I understand that some submissions require additional verification, particularly first-time releases. I respect the review process and am fully prepared to cooperate with any requirements. However, the lack of communication makes it extremely difficult to plan a release or understand whether the submission is progressing normally. Could someone from the Apple App Review team please clarify: Is this submission correctly queued for review? Is there any outstanding issue or verification requirement that has not been communicated? Can the current submission or existing support request be escalated for a status check? Is any further action required from my side? I am not requesting an exception to the App Review Guidelines. I am simply asking for visibility into the status of a submission that has remained untouched for more than a week. I would sincerely appreciate a response from an Apple representative. Thank you, Marque Development Team
Replies
1
Boosts
0
Views
30
Activity
1d
How long should I wait for an App Review Board appeal response before following up? And where?
Hi everyone, I submitted an appeal to the App Review Board on October 6, 2026, regarding a rejection. It's now been 16 days, and I haven't received a response yet. I understand that the appeal process can take some time, and I'm not necessarily looking to speed things up. I'm just wondering what the typical waiting time is based on other developers' experiences. For those who have gone through the App Review Board appeal process: How long did it take for you to receive a response? After how many days without a response would you recommend following up? If a follow-up is necessary, what's the most appropriate contact channel? Apple Developer Support, App Review Contact, or somewhere else? I'd appreciate any advice or experiences you could share. Thanks in advance!
Replies
1
Boosts
0
Views
37
Activity
1d
App Review Delayed Again After Addressing All Rejection Issues — Waiting for Review for 7+ Days
Hi everyone, I'm looking for advice from developers who have experienced prolonged App Review delays, and hopefully some help from someone at Apple who can look into this situation. My app, Parozo: Restaurant POS & KOT (iOS version 1.0.0), was initially reviewed by Apple, and I received feedback regarding several guidelines: Guidelines 2.3.10 and 2.3.3: App Store screenshots and accurate representation of the app. Guideline 3.1.1: In-app purchases and business subscription functionality. Guideline 4.5.4: Push notification permissions. I carefully reviewed Apple's feedback and made the requested changes. I replaced the screenshots with actual iOS app screenshots, made push notifications optional, and removed plan, pricing, registration, and renewal screens and purchase links from the iOS app to address the subscription-related concerns. I then submitted the updated build 1.0.0 (7) for review on October 16, 2026. However, the submission is still showing “Waiting for Review,” and more than seven days have now passed without the new review process starting or any further communication. I've also contacted Apple Developer Support multiple times regarding these delays. Unfortunately, I haven't received a meaningful response to my previous requests. I submitted another support request yesterday, but the issue remains unresolved. My latest App Review support case is 103003613618. I completely understand that app reviews take time and that Apple must carefully evaluate every submission. I'm not asking for the review guidelines to be bypassed or for special treatment. I have addressed the issues identified in the previous review and simply want to understand why the corrected submission is still waiting and whether any further action is needed from my side. As an independent developer, these repeated delays and the lack of communication make it difficult to plan a product launch, particularly after spending time addressing the feedback provided by App Review. Has anyone experienced a similar situation after fixing all the issues identified by Apple? Did your resubmission eventually move into review, and is there an effective way to get a status update when repeated support requests receive no response? I'd especially appreciate guidance from anyone who has successfully escalated a similar case, or from an Apple representative who can direct me to the appropriate team. Thank you for your time and help.
Replies
1
Boosts
0
Views
32
Activity
1d
Resubmission stuck in "Waiting for Review" for 13 days after resolving a Guideline 2.1 note — how to get it looked at?
Our app was reviewed on 8 October and returned under Guideline 2.1 (Information Needed) because the reviewer could not sign in with the demo account. The cause was on our side and was fixed the same evening: the review account now uses a fixed verification code, the App Review notes were updated with step-by-step instructions, we replied in the Resolution Center, and we resubmitted on 9 October. Since then the submission has shown Waiting for Review with no further contact — 13 days as of today. The first cycle of the same submission also waited eight days before review. We requested an expedited review on 14 October and have had no reply to that either. Submission ID: 9f09ed47-0ac0-45d1-8b6c-af9c05c8e3bd. We have verified the demo sign-in end to end against production and are available at any time if a reviewer needs anything. Two questions: Is there anything about a resubmission after a 2.1 note that places it in a different or slower queue than a new submission? Would cancelling and resubmitting the identical build as a new submission be the right move at this point, or does that risk losing a place in an escalated queue we can't see? Thanks for any guidance.
Replies
1
Boosts
0
Views
47
Activity
1d
Pending Termination Notice (Section 3.2(f)) received on 24 September, with no response to our appeal or follow-ups for 28 days
Hello everyone, On 24 September, our developer account received a Pending Termination Notice citing Section 3.2(f). We appealed immediately and have followed up repeatedly since. It has now been 28 days, and we have not received a single response, not even an acknowledgement. I’m posting here because we have run out of other options, and because I want to ask a plain question: who at Apple is responsible for this? What the notice told us, and what it didn’t The notice quotes a clause from the agreement. It does not say which of our apps is involved, what exactly was found, or what we are expected to fix. We can only guess at what Apple’s review found. Our best guess is this. We built a white-labelled version of our product for a client and hosted it on our developer account, because the client’s own developer account was still waiting on DUNS approval. We always planned to move it to the client’s account as soon as theirs was ready. If that is the issue, we are willing to transfer the app right away and make any other changes needed. But we can’t tell whether that is the issue, or whether there is something else we haven’t even thought of. Without an explanation, we can’t fix anything. What 28 days of silence has cost us Our entire team is at a standstill, because we can’t plan releases, updates or new work while the account’s future is uncertain. Our client is waiting, and so are our users. For a small company, every week of this puts salaries, contracts and relationships at risk. What we are asking Apple for A response to our appeal, from a person, with a clear owner for this case. A specific explanation of the finding, meaning which app and which part of the clause, not only the clause text. A fair, reasonable window to fix the issue, including moving the client’s app to their own account, before any termination is considered. A timeline, so we can tell our team and clients what to expect. Apple sets the rules for its platform, and we accept that. But the people who build on that platform put years of work and a lot of passion into their products. A process that threatens to end a business and then goes silent, with no explanation and nobody taking responsibility, is hard to defend as fair. If an action carries consequences this serious, someone should own the decision and be able to explain it. If any Apple representative reads this, or if anyone in the community has been through the same situation and found a way forward, we would be grateful to hear from you. Thank you.
Replies
2
Boosts
0
Views
64
Activity
1d
First release stuck in Waiting for Review since October 17
Our first iOS release, KanChinese: Learn Chinese HSK (Apple ID 6819210106), version 1.13.34, was first submitted on October 7, 2026. It was reviewed on October 17 and we fixed every point raised (camera and photo permission text, account deletion, with a screen recording in the review notes). We resubmitted the same day, and it has been in Waiting for Review since October 17. We opened support case 102997347616 but have not received an update. Is there anything we need to provide? Thank you.
Replies
1
Boosts
0
Views
23
Activity
1d
First app stuck in "Waiting for Review" since October 14 – expedite granted, review never started
Hello, Our first app, Hegemonia: War Strategy Game (Apple ID 6822418708), has been waiting for its first review since October 14 and has never reached "In Review". We made a mistake: we withdrew and resubmitted twice (October 18 to change the build, October 22 to include the first in-app purchases with the version). The current submission is from October 22 and has 9 items: version 1.0 (build 37), 6 consumable in-app purchases and 2 non-renewing subscriptions. We will not withdraw it again. An expedited review was granted on October 22, and we opened a support case (103004844776). Agreements, tax, banking and the DSA trader status are all active, and our TestFlight external builds were approved. Is there anything on our side that could be holding the submission, or anything else we should do? Thank you.
Replies
1
Boosts
0
Views
29
Activity
1d