Hello, I am a sole proprietor based in South Korea. My Apple Developer account was originally enrolled as an individual and was later changed to an organization account. When I try to provide new tax information in App Store Connect, the available form appears to treat my business as a corporation and asks me to complete documentation intended for a corporate entity. I do not want to submit a form that may be inappropriate for my actual tax status. I contacted Apple Media Services Finance Support about this issue through the website on September 4, 2026, and received an acknowledgment for Case-ID: 22018889. Because I had not received a substantive response, I submitted another inquiry about the same issue on September 8, 2026, and received Case-ID: 22076834. The second case was a follow-up to the first, not a separate tax issue. As of September 16, I have received only the automated acknowledgments, with no further update or request for information. I have not been able to arrange phone support from South Korea. The acknowledgment emails say I can update each request by replying with the same subject line. Is that the best way to reach the tax team or escalate this tax-form classification issue? If an Apple staff member sees this post, could you please check the status of both cases (22018889 and 22076834) and let me know whether further information is needed or what the next step should be? I would also appreciate hearing from anyone who has dealt with a similar individual-to-organization change as a Korean sole proprietor. I can provide business documents privately to Apple Support if needed. I will not post tax identifiers or account details publicly. Thank you.

Does anyone know why I'm having this issue. I am uploading screenshots that worked fine a week ago in my last approved submission, yet they just disappear when I go to upload them in my new version. I've tried everything I can think of and google hasn't been helpful either. The image is not being rejected and it worked fine last week. The upload just spins and then the screenshot goes away, It is just disappearing and won't upload. No error message. A few people on reddit told me they are having the same issue.

I’m unable to add several older In-App Purchases and auto-renewable subscriptions to an App Review submission in App Store Connect. The UI only shows: Unable to Add for Review Something went wrong. Try again. However, checking the failed reviewSubmissionItems requests in the browser dev tools shows HTTP 409 responses indicating that the existing IAP/subscription versions use an older format that is no longer supported for review submission. The affected errors include: STATE_ERROR.SUBSCRIPTION_VERSION_NOT_SUPPORTED Subscription version '[REDACTED]' is using an older format that is not supported for review submission. Please update before submitting. STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_NOT_SUPPORTED Subscription group version '[REDACTED]' is using an older format that is not supported for review submission. Please update before submitting. STATE_ERROR.IAP_VERSION_DATA_SCHEMA_NOT_SUPPORTED In-app purchase version '[REDACTED]' is using an older format that is not supported for review submission. Please update before submitting. In my case, this affects: 3 older subscription versions 1 subscription group version 1 older IAP version All required metadata in App Store Connect is complete. The interesting part is that I can create a new IAP today and add it to the same review submission successfully. Only the older IAP/subscription records fail. I can’t find any option in App Store Connect to “update” or migrate these legacy versions to the newer format referenced by the error message. Has anyone found a self-service way to migrate/regenerate these older IAP/subscription versions, or does this require Apple to update the records server-side? I’ve already opened a support case with Apple (ID: 102963040418), but wanted to check whether others are seeing the same issue.

Our build was rejected under Guideline 2.3.2 (Accurate Metadata) over subscription promotional images that were flagged as duplicates of, and too similar to, our app icon. The rejection was against the build, not the subscriptions directly. At the time, all five subscriptions plus the subscription group were in "Submitted for Review" status, which meant they couldn't be edited directly. Troubleshooting steps taken so far: Developer-cancelled each of the five subscriptions to get them out of "Submitted for Review" and into an editable state. Edited each subscription to remove the promotional image that triggered the 2.3.2 flag. Made changes to the Localization and Review Information fields on each subscription to force a new Save action. The Save completed successfully with no errors on any of the five subscriptions. After this, all five subscriptions and the subscription group are showing "Removed" from the Review Status column of our iOS submission. However, "Developer Rejected" status still shows in the Subscriptions section of Monitization (ASC->Distribution). That status hasn't cleared despite the successful edit and save, and I'm not able to reattach the subscriptions to a build for a new review submission from this state. Has anyone run into this — a subscription that was developer-cancelled, corrected, and successfully saved, but remains stuck on "Developer Rejected" instead of returning to a submittable state? Is there a separate action needed beyond edit-and-save (e.g., a distinct resubmit step, or removing and recreating the subscription) to move it forward from here? Any guidance on the correct path would be appreciated — happy to provide additional screenshots or details if useful.

My iOS app has passed App Review and is marked “Ready for Distribution,” but App Store Connect does not allow me to release it because the App Store Version Release controls are disabled. App Review is closed and the Resolution Center is unavailable. I have submitted multiple Apple Developer Support cases and called phone support, but the issue remains unresolved. This appears to be an App Store Connect backend state issue affecting a first-time app with subscriptions. Can Apple engineering assist in unlocking release permissions for iOS version 1.0?

Hi all, Looking for insight on whether others are seeing similar delays right now. Timeline for this app (first submission, new developer account): Aug 31: Initial submission, status "Waiting for Review" The submission sat in "Waiting for Review" for ~12 days with no movement Requested an expedited review — it was picked up and moved to "In Review" Rejected for a server-side issue (not a metadata issue). I responded in Resolution Center explaining the fix, then resubmitted on Sep 12 Since Sep 12, the app has been back in "Waiting for Review" and has not moved to "In Review" again It's now been several days since resubmission with no update. Given the app was already expedited once and rejected for a fixable server-side issue (already explained and resolved), I'd expect it to move faster on resubmission, but it's sitting exactly like a fresh submission. Has anyone experienced a resubmission after an expedited-review rejection get stuck like this? Trying to figure out if this is a broader queue issue (I've seen similar posts referencing September slowdowns) or something specific to my submission that I should look into. Any recent experiences appreciated.

I am new and submitted an app which got reviewed twice over the last 2 weeks. I tried adding IAP in the 2nd submission but it didn't get attached. I created 3rd submission and the status says Ready for Review. The IAP says (Unable to Submit for Review To submit your items for review, add an app version for the selected platform.). There is no option to cancel the submission and restart. Previous review cycles showed "Waiting for Review" and "In Review" before I got response on reasons for rejecting the app submission. But now it appears to be stuck. I requested email support. Is there any solution that I am missing? Thanks for your help! Raja

I'm hoping someone from Apple engineering can help, as support tickets and callbacks have not resolved this issue. The problem: My app "Brutal Time - Typographic Clock" does not appear in App Store search results at all — not even when searching for its exact name "Brutal Time." This has been ongoing for over six weeks. Additionally, the app does not appear in Apple Search Ads when I try to set up a campaign — suggesting this is a backend indexing issue, not a ranking issue. Timeline: Dec 17, 2025: App launched, initially searchable Dec 31, 2025: Transitioned to freemium model, became invisible in search. Jan 5, 2026: Fixed the issue, submitted update (v2.02), approved same day Jan 14, 2026: Submitted metadata update (v2.03) to improve discoverability, approved same day Feb 8, 2026: Tried removing from sale and re-adding to force re-index — no effect Feb 10, 2026: Still not appearing in any search results What I've tried: Submitted multiple support tickets (most recent: Case #102797235758) Each ticket generates an automated reply stating Apple will respond within 2 business days — they never have Requested and received callbacks multiple times, was told it would be escalated to US engineering team. But no follow-up, no resolution, no explanation Removed from sale and re-added to attempt to force re-indexing — didn't work App shows "Ready for Distribution" in App Store Connect Direct link works fine: https://apps.apple.com/us/app/brutal-time-typographic-clock/id6756289461 Response from Apple Support: "The behavior you observed is expected. App Store charts and search results change regularly and we don't guarantee app placement." This response misses the point entirely. I'm not asking about rankings — I'm asking why the app is completely invisible in search, including for its own branded name. This is not an isolated issue. Other developers have reported the same problem with the same non-response from Apple: https://developer.apple.com/forums/thread/803937 https://developer.apple.com/forums/thread/73981 https://developer.apple.com/forums/thread/74110 Has anyone found a resolution? Is there any way to trigger a proper re-index, or escalate to someone who can actually investigate?

A newly released iOS app has been available for approximately three weeks, but I still cannot find it by searching its exact name in the U.S. App Store. Several U.S.-based people whom I asked to independently test the same search were also unable to find it using their own devices and accounts. The same issue occurs on Apple’s public U.S. App Store website. The app’s direct link works normally, and searching for the developer name returns the app, but searching for the exact app name only returns unrelated apps. I submitted Developer Support case 20000142933730 approximately one week after the app became available, so the issue was already well beyond the normal 24-hour post-approval period. Apple Support reproduced and documented the issue before the case was escalated. After multiple phone calls and emails, the case has been assigned to three different Advisors. The current Senior Advisor says the app appears in her search environment and asked me to provide a screen recording. I sent the requested screen recording and screenshot, but was subsequently asked to provide the same evidence again. My questions have not been answered. Her response also referenced an unrelated case number. I do not intend to criticize any individual Advisor. However, I am increasingly concerned that the complete case history and submitted evidence have not been reviewed, and that the case may be stuck in a Support loop rather than reaching the team that can investigate App Store search behavior. This issue is significantly delaying the app’s launch and preventing users from discovering it through normal App Store search. Could an Apple staff member please help confirm whether case 20000142933730—including Apple’s previous reproduction and the screen recording and screenshot I submitted—has been forwarded to the Engineering team responsible for App Store search? If any other developers have experienced inconsistent exact-name search results across different App Store user environments, I would also appreciate hearing how the issue was resolved.

Hello, I submitted my EU Digital Services Act trader verification on 23 August 2026, including all requested documentation. Since then the status in App Store Connect has read "In Review", and the section is not editable, so I cannot correct or resubmit anything. I opened this case on 31 August 2026 and have followed up twice. I have not received a reply. As of today, 14 September 2026, 16 business days have passed since submission. App Store Connect Help states that if a compliance case is still pending after 14 business days, I should contact Support — which is why I am writing again. The practical impact: my app Nefelejcs (Apple ID 6799616127) is currently not downloadable in any EU storefront. The app is Hungarian-language and built specifically for users in Hungary, so it is effectively unavailable to all of its intended customers. Could you please: tell me the current status of the verification; tell me whether any submitted document is insufficient, and which one, so that I can correct it — I can also provide English translations of any Hungarian document; arrange a phone callback if that would be faster. Thank you, Attila Nagy App: Nefelejcs — Apple ID 6799616127

All auto-renewable subscriptions for Domiai (bundle app.domiai, App ID 6799989904, group 22305757) stay MISSING_METADATA via ASC API for weeks. Metadata complete for each product: fi+en-US localizations, group localizations, pricing, multi-territory availability, review screenshot COMPLETE (1290×2796). Business (Paid Apps, Banking, Tax, DAC7) all Active. Even a newly created control product domiai_meta_unstick_monthly (6801762338) with full config is also MISSING_METADATA. TestFlight StoreKit / RevenueCat: “products could not be fetched”. Feedback: FB24775023 Support case: 20000138025601 (closed without investigating ASC state) Has anyone seen MISSING_METADATA persist after Paid Apps became Active with screenshots+localizations complete? Any known account-level unblock? Product IDs: domiai_plus_monthly/yearly, domiai_ai_monthly/yearly.

Has anyone observed the intermittent issues with the AppStore Connect site? Missing app records and error banners where information should appear “Your account cannot be found” error “Please accept these terms and conditions” Could this explain why some apps remain in review or seem to wait indefinitely—perhaps due to suppressed technical bugs or errors in the site’s processing of changes, where end-to-end flows fail to complete what would otherwise yield a finished review?

My iOS app “Artı Eksi” (version 1.0, build 13) was submitted for review on September 10, 2026, at 1:56 PM but its status has remained “Waiting for Review” without any update. The Submission ID is 1bfb533b-f2c8-4473-905c-9ee8a87ed3e6. Could you please check the submission and let me know whether there is an issue or anything I need to do?

The Screenshot specifications page lists iPhone Duo as an iPhone screenshot size: Outer display: 1398 × 2034 and 2034 × 1398 Inner display: 2007 × 2853 and 2853 × 2007 https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications I cannot find a way to upload them. In App Store Connect, the App Previews and Screenshots device selector on my app's version page does not list iPhone Duo. The only iPhone options are the existing display sizes. In the App Store Connect API, ScreenshotDisplayType has no Duo case. The largest iPhone case is still APP_IPHONE_67. I checked the current reference: https://developer.apple.com/documentation/appstoreconnectapi/screenshotdisplaytype My questions: Where in App Store Connect do I upload iPhone Duo screenshots? If the option is not open yet, is there a ScreenshotDisplayType case for Duo that I should use through the API instead? Thanks.

Hi Apple Developer Community, My app was rejected under Guideline 2.3.2 because I accidentally uploaded the wrong promotional image. I want to remove the image as instructed by App Review, but the IAP is currently Ready for Review, and the image is locked. There is no option to remove or replace it, and the Save/Add for Review buttons are disabled. I have already contacted Apple Developer Support (Case ID: 102955732091) and am waiting for a response. Has anyone faced this issue? Is there a way to unlock the IAP metadata, or does Apple need to remove the image from their side? Thanks!

Its my First App. It has been ready for Distribution since August 18, in the Business tap,everything is "Active" but my status in Compliance -Digital Services Act is stack "in review"!! No email replies, no nothing. Can anyone help me please?

Good day, I'm trying to resolve the EU "Digital Services Act" compliance for my employer's Apple Developer account, but I'm stuck on verifying the phone number. The email verification code came through without any issue. We are located in South Africa, with a "+27" area code and the number I need to use here is a landline that comes through to the receptionist at our head office. This number does not have the ability to receive text messages, so I selected the "Didn't get a verification code?" link and chose the receive a phone call instead, however the call never comes through. Calling the number from my cellphone goes straight through to the receptionist, there are no digital switchboard prompts for the caller to select from. I tried this numerous times this Friday just past, and again twice now today, still no luck. I've requested an official document from my manager to see if I can go that route to verify the details, but so far nobody seems to be able to find an appropriate document for me to use... :( Is there anything else that I can do here?

My app has one App Store Connect listing with released iOS, tvOS, and native visionOS versions. I have temporarily discontinued native visionOS development due to very limited adoption and no access to a physical Vision Pro for ongoing testing. I would like Vision Pro users to receive my iPad app through “Designed for iPad” compatibility instead. Xcode is configured with “Apple Vision (Designed for iPad)” and correctly produces an iOS build. I am not trying to generate another native visionOS build. The obstacle is the existing published visionOS version. Apple’s documentation says that iPad compatibility is unavailable when the app already supports native visionOS, and that a platform cannot be deleted once a build has been uploaded. Has anyone successfully made this transition while keeping the same App Store Connect record? Specifically: Is there a supported way to retire the native visionOS version and offer the compatible iPad app? Can Apple Developer Support enable this if App Store Connect cannot? What happens to existing native visionOS installations? I would appreciate any firsthand experience or clarification from Apple on whether this transition is supported.

I am having an error when trying to Add for Review? Unable to Add for Review The items below are required to start the review process: An unexpected error was encountered when submitting for review. If the issue persists please contact us. Does anyone else have this issue or know perhaps a workaround.

I’m wondering if anyone else is experiencing the same issue. My app has been sitting in “Waiting for Review” for quite some time now, with no status changes or updates. I completely understand that review times can vary, and I truly appreciate the work the App Review team does. However, when there is no visibility into what’s happening, it can be difficult for developers to know whether everything is progressing normally or if there is an unexpected delay. It would be very helpful if Apple could provide more transparency during longer waiting periods, or publish a brief announcement when review queues are unusually busy. Even a simple status update would help developers better manage expectations and plan their releases. For many independent developers and small teams, every day of waiting can have a significant impact on launch plans, marketing schedules, and business operations. The uncertainty is often more stressful than the wait itself. I hope Apple can consider providing a little more communication around extended review queues. It would greatly improve the developer experience and reduce unnecessary anxiety. Has anyone else’s app been waiting for review longer than usual recently?