Overview

Post

Replies

Boosts

Views

Activity

PHASE occluder silences direct sound instead of muffling it
I’m using PHASE for an outdoor soundscape with only .directPathTransmission enabled. A point source and listener are 2 metres apart. Between them is a PHASEOccluder built from a 2 × 2 × 0.02 metre MDLMesh box, with a .cardboard material assigned to every shape element. Without the occluder, the sound is loud. With it, the sound is completely inaudible. Switching to .glass and setting the sampler’s cullOption to .doNotCull makes no audible difference. This happens on both iOS Simulator and a physical iPhone. Adding .lateReverb produces faint audible sound, but room reverb is inappropriate for this outdoor scene and doesn’t establish whether direct transmission works. Is this expected attenuation, or is additional configuration required to hear muffled sound through an occluder? Is there a working sample demonstrating material-dependent transmission with reverb disabled?
3
1
1.6k
21h
AirSystem HQ – Waiting for Review since Oct 17, expedite requested Oct 18
Hello App Review team, Our app AirSystem HQ (Apple ID: 6821436401, bundle ID: com.airsystemhq.app) has been in Waiting for Review since October 17, 2026. We submitted an expedited review request on October 18 and have had no movement since. An earlier submission received a reviewer question about pricing. We corrected the pricing and resubmitted, and nothing is pending on our side. AirSystem HQ is a service and sales platform for compressed-air service companies, and customers are waiting to onboard. Could someone check whether anything is holding this submission and help move it forward? Case number: 102996856121 Thank you, Michael Moore Moore Managed IT Inc
0
0
32
21h
Our app DeltaYa (Apple ID: [número]) has been stuck in App Review for nearly two weeks, and we have run out of ways to get it moving.
Oct 13: submitted for review. Oct 13 – 21: "Waiting for Review" for 8 days. We contacted Developer Support and submitted an expedited review request. No reply to either. Oct 21: finally reviewed. The review itself took less than 30 minutes. Rejected under 5.1.1(v) for two privacy items: an optional field shown as required, and account deletion that was hard to find. Same day: both issues fixed, the screen recording Apple requested attached, new build resubmitted. Today: back in "Waiting for Review", again with no movement. DeltaYa is a delivery service for the islands of the Tigre Delta in Argentina, communities that can only be reached by boat. Our Android app is already live. Stores, boat drivers and customers are ready. We have postponed our launch day after day because we planned around Apple's own statement that most reviews are completed within 24–48 hours. What we can't understand: Why a review that takes 30 minutes needs 8 days just to start. Why a resubmission that only fixes the exact points flagged by the reviewer goes back to the end of the queue. Why the expedited review request, the process that exists for exactly this situation, gets no response at all. We are a small company. Every day of delay costs us money and credibility with the community that is waiting for this service. Is anyone else seeing these delays right now? And if anyone from the App Review team reads this: we would really appreciate it if someone could look at our resubmission. It only fixes the points already raised.
0
0
34
21h
Location Services stopped working across the system on macOS
MacBook Air (M4) Current build: macOS 27 Developer Beta (26A5368g) I have a system-wide Location Services failure affecting Apple Maps, Safari geolocation APIs, and any application requesting the current location. Symptoms: Apple Maps cannot determine current location. Safari and browser geolocation APIs fail. Websites report that location cannot be found. Location Services are enabled and permissions are granted. The issue has persisted across: macOS 26.5 beta macOS 26.6 beta macOS 26.6 beta 2 macOS 27 Developer Beta Troubleshooting already performed: Multiple Wi-Fi networks tested. iPhone hotspot tested. VPN enabled and disabled. Location Services reset. Permissions reset and reauthorized. New clean local user account created (no Apple ID, no third-party software). Issue reproduces identically in the clean account. Technical observations: locationd logs repeatedly show: knownCount = 0 AlsWifi = unknown while Wi-Fi scanning itself appears successful: queryMacAddresses.size = 57 The system sees dozens of nearby access points, but none appear to be recognized for Wi-Fi positioning. Additional findings: Wi-Fi hardware functions normally. Internet connectivity is normal. Bluetooth and Find My device presence work. GeoServices resources are present on disk. No successful location fix is ever produced. Has anyone seen similar CoreLocation / GeoServices behavior where Wi-Fi scans succeed but knownCount always remains 0 and no location fix is generated?
9
2
1.9k
21h
W-9 shown for single-member US LLC owned by a non-US individual — should be W-8BEN (disregarded entity)
Hello! I have a new organization-level Apple Developer account and I'm stuck on the Tax Forms step in App Store Connect (https://appstoreconnect.apple.com/business). The system is showing me U.S. Form W-9 as the only option, but in my case filling out a W-9 would be incorrect — and I'd appreciate guidance from anyone who has resolved this. My setup: I am a non-US individual (not a US citizen, not a US resident, never lived in the US). I am the sole owner of a single-member LLC registered in the US (set up via Firstbase specifically to distribute a mobile app). For US federal tax purposes, this LLC is a disregarded entity — it's not treated as a separate taxpayer from its owner. Why W-9 is not the correct form in my case: The IRS instructions for Form W-9 explicitly state: "If the owner of the disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9. This is the case even if the foreign person has a U.S. TIN." Form W-9 also requires me to certify, under penalty of perjury, that I am a US person — which I am not. The LLC itself doesn't certify anything on a W-9 because it's disregarded; the IRS looks through to the beneficial owner, who in my case is a foreign individual. The correct form for me should be W-8BEN (Certificate of Foreign Status of Beneficial Owner — Individuals). What I've already tried: I opened two support cases 4 days ago and have not received a substantive response yet: Apple Developer Support — Case ID: 20000112974233 Ack Tax / Tax category settings — Team ID: 7YYWN3MYCY, Case ID: 19944616 My questions: Has anyone in the same situation (non-US individual, sole owner of a US single-member LLC) successfully switched the tax form from W-9 to W-8BEN inside App Store Connect? If so, how? Is there a specific path in the Business / Tax Forms section to declare the beneficial owner as a foreign individual that I might be missing? Is there an escalation channel beyond the standard support cases for tax-form issues that are blocking onboarding? Thanks in advance for any pointers.
22
9
3.1k
21h
Title: First submission stuck in "Waiting for Review" since 14 Oct 2026 (8 days)
Hello App Review team, My app "Money AI" (Apple ID 6815103496), version 1.0 (build 12), together with its first subscription group "Money AI Plans" (3 auto-renewable subscriptions), has been in "Waiting for Review" since 14 October 2026, 7:19 AM SGT, with no messages in App Store Connect. I have contacted App Review through the contact form twice. One detail that may be relevant: my Paid Apps Agreement shows an effective date of 15 October 2026, one day after I submitted. Could you please check whether the submission needs anything from me, or whether it needs to be resubmitted now that the agreement is active? Thank you for your help.
0
0
24
21h
Resubmitted app still “Waiting for Review” after six days — correct escalation path?
Hi, My iOS app was initially reviewed and rejected very quickly—within about a minute. I addressed the requested items, provided all of the requested information, including a screen recording showing the relevant app flows, and resubmitted on October 15. As of October 21, the submission is still “Waiting for Review,” which is nearly a week without a further update. I understand that review times vary, but the contrast between the near-immediate initial rejection and the prolonged wait after providing the requested materials makes it unclear whether the resubmission is progressing normally. Have other developers experienced a similar delay after resubmitting with the requested documentation? Is waiting the correct course, or is there a specific escalation path or additional step I should take to ensure the submission has not stalled? Thank you.
1
0
37
21h
Individual enrollment rejected – only driver's license offered as ID document for a German account
I have been unable to complete Individual enrollment in the Apple Developer Program for several months. Every attempt ends with "ID verification rejected" and a message telling me to contact Support. Support has reset my enrollment once; the next attempt failed in exactly the same way. A manual review by a specialist team was promised on the phone but, as far as I can tell, never happened. I have narrowed the problem down and would like to share the findings, because I believe they point to something on Apple's side rather than a user error. What I observe: During identity verification, the Apple Developer app offers me the driver's license as the only accepted document. National ID card and passport are not selectable. For Germany, those two are the standard identity documents. The behaviour is identical on iPhone, iPad and Mac – across two platforms and in two different display languages. So it is not device- or language-specific. My Apple Account is set to Germany throughout: country/region, language, shipping and billing address, and the trusted phone number. I have no phone number from another country and no second Apple Account. The German driver's license does not contain a residential address. Any verification step that relies on an address match cannot succeed with this document. Face verification never happens. The rejection occurs immediately after the document is submitted, before that step is reached. One possibly relevant detail: my surname was originally stored in my Apple Account in its transliterated form ("Xxxuexxx") and I later changed it to the spelling that matches my passport and national ID ("Xxxxüxxx"). The enrollment problems began around that time. I have asked Support to check whether a duplicate person record exists, but have not received an answer to that question. Notably, Apple Support initially told me the cause was that my trusted device was already linked to another Apple Account enrolled in a developer program. I could not find any such account, and Support never clarified which account was meant. If a duplicate person record was created by the spelling change, that message would make sense — the "other account" would in fact be my own earlier record. What I have already tried: Verified trusted devices and phone numbers – only my own, currently used devices and my own number are listed. Confirmed that nobody else in my household has a developer account. Tried enrollment from different devices. Removed a secondary display language, reinstalled the app – no change to the document selection. Phone callback and multiple email exchanges with Developer Support. My questions: Which country is stored in my enrollment record? The restricted document selection suggests it differs from the country set on my Apple Account. Why are national ID card and passport not offered, and can the document selection for my record be corrected? Is there a way to get this reviewed by the enrollment or identity verification team? Could a duplicate person record under the transliterated spelling be causing both the "other account" message and the restricted document list? Case number: 20000132833454 Region: Germany I am willing to provide any identity document required – as soon as the system actually offers it. Any pointers from people who have seen the same restricted document list would be very welcome.
1
1
98
21h
DSA Trader Verification stuck "In Review" since 11 August 2026 - app blocked in all 27 EU countries
Hello, my app "YOGO Loops" (Apple ID: 6799279746) has been approved and is "Ready for Distribution", but it is unavailable in all 27 EU countries. App Store Connect > Business > Compliance shows: Digital Services Act | 27 countries or regions | Last Updated: 11 Aug 2026 | Status: In Review Pricing and Availability shows "Trader status not provided" / "Cannot sell" for all EU territories. Everything else is Active: Tax forms (W-8BEN): Active Administrative Cooperation Directive (7th amendment): Enabled Trader information (address, phone, email): submitted I am an individual developer based in Germany, so my main market is completely blocked. Apple states a review time of about 5 business days, I am now at day 38. I have already filed a support request with Apple. Has anyone had a DSA verification unstuck after a delay like this? Is there an escalation path beyond the standard support form? Thank you.
0
0
159
21h
DSA Trader compliance stuck In Review — blocking EU sale before time-sensitive event
Hi all, Our app "Na šipky!" (bundle ID cz.czechdartsopen.app, App Store ID 6802246248) was approved (READY_FOR_SALE), but is currently removed from sale in all EU territories pending Digital Services Act Trader status verification. We submitted the Trader compliance declaration and supporting documents on September 1, 2026 — status has been "In Review" since submission. This is time-critical for us: the app is the official companion app for the Czech Darts Open tournament, September 4-6, 2026, in Prague. We need EU availability (Czech Republic specifically) before the event. I've also opened a support case with Apple Developer Support (Case ID: 102950641374, submitted via Contact Us, awaiting reply) — phone support isn't offered for this topic in our region. Has anyone dealt with a stuck DSA Trader review before, and if so, how long did it take / did anything help speed it up? Any advice appreciated. Thanks!
0
0
97
21h
MusicKit playback alongside cosmetic in-app purchases: allowed under 3.3.6(D)?
I'm planning an iOS app that uses MusicKit for playback and want to confirm the setup complies with the Apple Developer Program License Agreement (section 3.3.6(D)) and App Review Guideline 4.5.2 before I build further. How music works in the app: • Songs come only from the Apple Music catalog through MusicKit. • The only prompt is the standard iOS permission request for Apple Music access. • Apple Music subscribers hear full songs. Non-subscribers hear the 30-second preview only. • The app has no sign-in and shows no subscription offers. Users manage Apple Music entirely in the Apple Music app. • Playback always starts from a user tap, with standard play, pause and skip controls. • Every playing song shows a link that opens it in the Apple Music app. • A simple on-screen animation runs while music plays, as a playback indicator only. It isn't synced to the audio, and nothing is recorded, saved or shared. • No ads, no subscriptions, and no limits on playback. How the app makes money: • Optional one-time in-app purchases of purely cosmetic visual themes. They change only how the app looks and don't unlock, improve or affect music access in any way. Questions: 1. Does selling cosmetic in-app purchases in an app like this count as "indirectly monetizing access to the Apple Music service"? 2. Is a visual animation that runs during playback (not synced to the audio) acceptable, or does it count as "synchronizing MusicKit Content with other content"? 3. For non-subscribers, is playing MusicKit's preview assets, with a link to the song in Apple Music and no subscription offer, an acceptable setup? Thanks for any guidance.
1
0
72
21h
DSA Trader Status "In Review" for 6 Days — App Blocked in 27 EU Countries
Hello, My DSA trader status compliance submission has been stuck in "In Review" since May 29, 2026 — 6 days with no update. As a result, my app Score Battle (Apple ID: 6769828159) is unavailable in all 27 EU App Store territories. Details: Individual developer account based in Germany All trader information submitted (address, phone, email) App is live in 146 non-EU countries with version 1.0.1 App Store Connect > Business > Compliance shows: Digital Services Act | 27 Countries | Last Updated: 29 May 2026 | Status: In Review I've also submitted a support request but haven't received a response yet. This is time-sensitive as my app is a football prediction game and the FIFA World Cup 2026 starts on June 11. Germany is a key market and I'm based here — I can't even see my own app in the store. Has anyone experienced similar delays with DSA trader verification recently? Any guidance on how to move this forward would be appreciated. Thank you.
0
0
81
21h
DSA Trader Verification "In Review" for 49 Days — EU Distribution Blocked
Hello, My app "Glow Mode: AI Skin Scanner" (Apple ID: 6762376419) has been blocked from distribution in all 27 European Union countries for 49+ days due to Digital Services Act trader verification stuck in "In Review" state. Current state in App Store Connect: • Business → Compliance → Digital Services Act: "In Review" since 24 March 2026 • Pricing and Availability → Manage Availability: all 27 EU countries show "Trader Status Not Provided" → "Cannot Sell" • App-level: declared as "trader app" ✓ • Account: published in 148 other countries, all agreements / banking / tax forms verified and Active Apple's stated typical review time is 5 business days. I'm at day 49. Several other developers have reported identical issues in recent threads: • https://developer.apple.com/forums/thread/822744 — DSA Review stuck • https://developer.apple.com/forums/thread/822857 — App not available in EU • https://developer.apple.com/forums/thread/818244 — Review stuck 2+ months I've also filed a support case (ID: 20000114608599) but wanted public visibility in case this is a systemic issue affecting multiple developers. Questions for Apple staff and the community: Has anyone resolved a DSA verification stuck this long? If so, how? Is there a backend status that may already show "approved" while the UI continues to show "In Review"? What is the recommended escalation path beyond the standard support form? Thanks in advance for any insight.
4
1
376
21h
App approved but EU distribution blocked due to DSA verification – is this normal?
Hello, I’m experiencing a situation with my app Waspp that I’m trying to understand. The app was approved by App Review on Feb 24, 2026 and is currently available on the App Store in the United States. However, distribution in the European Union (Belgium and France) is blocked due to the Digital Services Act (DSA) trader verification, which still shows “In Review” in App Store Connect. Some details: App Review completed: Feb 24 DSA compliance submitted: Feb 25 Status: Still “In Review” after more than two weeks Documents requested by Apple Support have already been uploaded via their secure link App availability shows “Cannot Sell” for Belgium and France The app is live and downloadable in the US Because of this, the launch of the app in the EU is currently blocked even though the app itself has been approved. My questions: Is it normal for the DSA trader verification to take this long? Has anyone experienced a similar delay with EU distribution? Is there anything else that can be done from the developer side to unblock the verification? Any feedback or similar experiences would be greatly appreciated. Thanks!
0
0
193
21h
App approved but EU distribution blocked – DSA compliance stuck “In Review”
Hello, My app “DeepTone” has been fully approved and is marked as Ready for Distribution in App Store Connect. However, the app is not available in EU countries due to Digital Services Act (DSA) compliance still showing “In Review”. details: DSA verification was submitted and confirmed as completed by Apple Developer Support (case ID available). App Review has already approved the app. The app is currently live in non-EU regions but blocked in the EU. App Store Connect still shows: Digital Services Act (DSA) compliance – In Review Encryption Self-Declaration (France) – In Review This appears to be a backend compliance status issue rather than an app review issue. Has anyone experienced a similar situation where DSA compliance remained “In Review” after approval? Is there a known escalation path or expected resolution timeframe for this? Thank you for any guidance.
3
2
354
21h
iOS submission stuck in Waiting for Review for over 48 hours after a What's New-only resubmission
Hello App Review team, Our iOS app Ohripa (version 1.5, build 25166424) has been in "Waiting for Review" since October 21, 2026 at 9:44 AM (Taiwan time, UTC+8), which is now more than 48 hours. Submission ID: 72c92e5e-3eb8-4cd7-92f2-032e093d6097 The previous submission of version 1.5 was rejected under Guideline 1.1 because of wording in the What's New text. We revised only the What's New text and resubmitted the same build (25166424). We have not received any message since resubmitting, and the Reply to App Review option is no longer available in App Store Connect while the submission is waiting. Could you check whether anything is needed from us to move this submission forward? We are happy to provide any additional information. Thank you.
0
0
19
21h
iOS 27: domain-bound SMS one-time codes are not offered in an associated app ("Could not fetch application record"), worked on iOS 26.6 and 18
Since iOS 27.0, domain-bound SMS one-time codes are no longer offered above the keyboard in our app, where the code is entered on a web page in a WKWebView, although the app is associated with the domain through webcredentials. The same SMS is offered in Safari on the same device, and it is offered in our app on iOS 26.6 and iOS 18. SMS format (last line per the domain-bound code format): Your verification code is: 123456 @app.example.com #123456Setup Several builds of the same app with different bundle IDs (App Store, internal, development), all under one team Entitlement com.apple.developer.associated-domains: webcredentials:app.example.com (plus two more environments of the same domain) AASA at https://app.example.com/.well-known/apple-app-site-association: 200, application/json, no redirect, same content on app-site-association.cdn-apple.com: {"webcredentials":{"apps":["TEAMID.com.example.app","TEAMID.com.example.app.internal","TEAMID.com.example.app.dev"]}} The code field is an <input type="tel" autocomplete="one-time-code"> in a WKWebView showing a page on that domain. We also tested a native field with the one-time-code content type (the app is built with Flutter; the field is a Flutter TextField with the one-time-code autofill hint). Steps Open the verification page in the app and focus the code field. Receive the SMS above. Expected: the code is offered in the QuickType bar, as it is in Safari on the same domain and as it is in our app on iOS 26.6 and iOS 18. Actual: nothing is offered. The keyboard log: kbd Received verification code from Messages kbd One Time Code field has been entered. kbd Retrieving Current One-Time Codes for App kbd Current verification code is domain-bound to <mask.hash: '…'>. kbd Domain-bound verification code is NOT valid for app <mask.hash: 'X'>. E kbd Could not fetch application record for application identifier: <mask.hash: 'X'>. kbd Returning 0 available one-time codesWhat we checked swcd downloads the AASA for all domains without errors after a reinstall. The installed app's entitlements (read from the device) contain the expected application-identifier and associated domains; the profile is validated. The failure is the same in the WKWebView field and in a native one-time-code field, in the App Store build, a distribution-signed internal build and a development build, and in an older app version that used to work. The masked application identifier in the log (X above) is the same for two builds with different bundle IDs, so the lookup does not seem to use the app's bundle ID. All our builds share CFBundleExecutable = Runner (the Flutter default) and the same CFBundleName. The same app build and the same SMS work on iOS 26.6 and iOS 18.x, so the change happened between iOS 26.6 and 27.0. An SMS without the @domain #code line is offered in the app on iOS 27 (Returning 1 available one-time code), although Could not fetch application record is still logged. Questions Is this a known iOS 27 regression, or is there a new requirement for apps to receive domain-bound codes? What application identifier does the keyboard use for this lookup, and can anything in the app's configuration (for example the executable name) affect it? Device: iPhone 17 Pro Max, iOS 27.0
3
0
85
21h
PHASE occluder silences direct sound instead of muffling it
I’m using PHASE for an outdoor soundscape with only .directPathTransmission enabled. A point source and listener are 2 metres apart. Between them is a PHASEOccluder built from a 2 × 2 × 0.02 metre MDLMesh box, with a .cardboard material assigned to every shape element. Without the occluder, the sound is loud. With it, the sound is completely inaudible. Switching to .glass and setting the sampler’s cullOption to .doNotCull makes no audible difference. This happens on both iOS Simulator and a physical iPhone. Adding .lateReverb produces faint audible sound, but room reverb is inappropriate for this outdoor scene and doesn’t establish whether direct transmission works. Is this expected attenuation, or is additional configuration required to hear muffled sound through an occluder? Is there a working sample demonstrating material-dependent transmission with reverb disabled?
Replies
3
Boosts
1
Views
1.6k
Activity
21h
AirSystem HQ – Waiting for Review since Oct 17, expedite requested Oct 18
Hello App Review team, Our app AirSystem HQ (Apple ID: 6821436401, bundle ID: com.airsystemhq.app) has been in Waiting for Review since October 17, 2026. We submitted an expedited review request on October 18 and have had no movement since. An earlier submission received a reviewer question about pricing. We corrected the pricing and resubmitted, and nothing is pending on our side. AirSystem HQ is a service and sales platform for compressed-air service companies, and customers are waiting to onboard. Could someone check whether anything is holding this submission and help move it forward? Case number: 102996856121 Thank you, Michael Moore Moore Managed IT Inc
Replies
0
Boosts
0
Views
32
Activity
21h
Our app DeltaYa (Apple ID: [número]) has been stuck in App Review for nearly two weeks, and we have run out of ways to get it moving.
Oct 13: submitted for review. Oct 13 – 21: "Waiting for Review" for 8 days. We contacted Developer Support and submitted an expedited review request. No reply to either. Oct 21: finally reviewed. The review itself took less than 30 minutes. Rejected under 5.1.1(v) for two privacy items: an optional field shown as required, and account deletion that was hard to find. Same day: both issues fixed, the screen recording Apple requested attached, new build resubmitted. Today: back in "Waiting for Review", again with no movement. DeltaYa is a delivery service for the islands of the Tigre Delta in Argentina, communities that can only be reached by boat. Our Android app is already live. Stores, boat drivers and customers are ready. We have postponed our launch day after day because we planned around Apple's own statement that most reviews are completed within 24–48 hours. What we can't understand: Why a review that takes 30 minutes needs 8 days just to start. Why a resubmission that only fixes the exact points flagged by the reviewer goes back to the end of the queue. Why the expedited review request, the process that exists for exactly this situation, gets no response at all. We are a small company. Every day of delay costs us money and credibility with the community that is waiting for this service. Is anyone else seeing these delays right now? And if anyone from the App Review team reads this: we would really appreciate it if someone could look at our resubmission. It only fixes the points already raised.
Replies
0
Boosts
0
Views
34
Activity
21h
Location Services stopped working across the system on macOS
MacBook Air (M4) Current build: macOS 27 Developer Beta (26A5368g) I have a system-wide Location Services failure affecting Apple Maps, Safari geolocation APIs, and any application requesting the current location. Symptoms: Apple Maps cannot determine current location. Safari and browser geolocation APIs fail. Websites report that location cannot be found. Location Services are enabled and permissions are granted. The issue has persisted across: macOS 26.5 beta macOS 26.6 beta macOS 26.6 beta 2 macOS 27 Developer Beta Troubleshooting already performed: Multiple Wi-Fi networks tested. iPhone hotspot tested. VPN enabled and disabled. Location Services reset. Permissions reset and reauthorized. New clean local user account created (no Apple ID, no third-party software). Issue reproduces identically in the clean account. Technical observations: locationd logs repeatedly show: knownCount = 0 AlsWifi = unknown while Wi-Fi scanning itself appears successful: queryMacAddresses.size = 57 The system sees dozens of nearby access points, but none appear to be recognized for Wi-Fi positioning. Additional findings: Wi-Fi hardware functions normally. Internet connectivity is normal. Bluetooth and Find My device presence work. GeoServices resources are present on disk. No successful location fix is ever produced. Has anyone seen similar CoreLocation / GeoServices behavior where Wi-Fi scans succeed but knownCount always remains 0 and no location fix is generated?
Replies
9
Boosts
2
Views
1.9k
Activity
21h
W-9 shown for single-member US LLC owned by a non-US individual — should be W-8BEN (disregarded entity)
Hello! I have a new organization-level Apple Developer account and I'm stuck on the Tax Forms step in App Store Connect (https://appstoreconnect.apple.com/business). The system is showing me U.S. Form W-9 as the only option, but in my case filling out a W-9 would be incorrect — and I'd appreciate guidance from anyone who has resolved this. My setup: I am a non-US individual (not a US citizen, not a US resident, never lived in the US). I am the sole owner of a single-member LLC registered in the US (set up via Firstbase specifically to distribute a mobile app). For US federal tax purposes, this LLC is a disregarded entity — it's not treated as a separate taxpayer from its owner. Why W-9 is not the correct form in my case: The IRS instructions for Form W-9 explicitly state: "If the owner of the disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9. This is the case even if the foreign person has a U.S. TIN." Form W-9 also requires me to certify, under penalty of perjury, that I am a US person — which I am not. The LLC itself doesn't certify anything on a W-9 because it's disregarded; the IRS looks through to the beneficial owner, who in my case is a foreign individual. The correct form for me should be W-8BEN (Certificate of Foreign Status of Beneficial Owner — Individuals). What I've already tried: I opened two support cases 4 days ago and have not received a substantive response yet: Apple Developer Support — Case ID: 20000112974233 Ack Tax / Tax category settings — Team ID: 7YYWN3MYCY, Case ID: 19944616 My questions: Has anyone in the same situation (non-US individual, sole owner of a US single-member LLC) successfully switched the tax form from W-9 to W-8BEN inside App Store Connect? If so, how? Is there a specific path in the Business / Tax Forms section to declare the beneficial owner as a foreign individual that I might be missing? Is there an escalation channel beyond the standard support cases for tax-form issues that are blocking onboarding? Thanks in advance for any pointers.
Replies
22
Boosts
9
Views
3.1k
Activity
21h
Title: First submission stuck in "Waiting for Review" since 14 Oct 2026 (8 days)
Hello App Review team, My app "Money AI" (Apple ID 6815103496), version 1.0 (build 12), together with its first subscription group "Money AI Plans" (3 auto-renewable subscriptions), has been in "Waiting for Review" since 14 October 2026, 7:19 AM SGT, with no messages in App Store Connect. I have contacted App Review through the contact form twice. One detail that may be relevant: my Paid Apps Agreement shows an effective date of 15 October 2026, one day after I submitted. Could you please check whether the submission needs anything from me, or whether it needs to be resubmitted now that the agreement is active? Thank you for your help.
Replies
0
Boosts
0
Views
24
Activity
21h
Resubmitted app still “Waiting for Review” after six days — correct escalation path?
Hi, My iOS app was initially reviewed and rejected very quickly—within about a minute. I addressed the requested items, provided all of the requested information, including a screen recording showing the relevant app flows, and resubmitted on October 15. As of October 21, the submission is still “Waiting for Review,” which is nearly a week without a further update. I understand that review times vary, but the contrast between the near-immediate initial rejection and the prolonged wait after providing the requested materials makes it unclear whether the resubmission is progressing normally. Have other developers experienced a similar delay after resubmitting with the requested documentation? Is waiting the correct course, or is there a specific escalation path or additional step I should take to ensure the submission has not stalled? Thank you.
Replies
1
Boosts
0
Views
37
Activity
21h
Individual enrollment rejected – only driver's license offered as ID document for a German account
I have been unable to complete Individual enrollment in the Apple Developer Program for several months. Every attempt ends with "ID verification rejected" and a message telling me to contact Support. Support has reset my enrollment once; the next attempt failed in exactly the same way. A manual review by a specialist team was promised on the phone but, as far as I can tell, never happened. I have narrowed the problem down and would like to share the findings, because I believe they point to something on Apple's side rather than a user error. What I observe: During identity verification, the Apple Developer app offers me the driver's license as the only accepted document. National ID card and passport are not selectable. For Germany, those two are the standard identity documents. The behaviour is identical on iPhone, iPad and Mac – across two platforms and in two different display languages. So it is not device- or language-specific. My Apple Account is set to Germany throughout: country/region, language, shipping and billing address, and the trusted phone number. I have no phone number from another country and no second Apple Account. The German driver's license does not contain a residential address. Any verification step that relies on an address match cannot succeed with this document. Face verification never happens. The rejection occurs immediately after the document is submitted, before that step is reached. One possibly relevant detail: my surname was originally stored in my Apple Account in its transliterated form ("Xxxuexxx") and I later changed it to the spelling that matches my passport and national ID ("Xxxxüxxx"). The enrollment problems began around that time. I have asked Support to check whether a duplicate person record exists, but have not received an answer to that question. Notably, Apple Support initially told me the cause was that my trusted device was already linked to another Apple Account enrolled in a developer program. I could not find any such account, and Support never clarified which account was meant. If a duplicate person record was created by the spelling change, that message would make sense — the "other account" would in fact be my own earlier record. What I have already tried: Verified trusted devices and phone numbers – only my own, currently used devices and my own number are listed. Confirmed that nobody else in my household has a developer account. Tried enrollment from different devices. Removed a secondary display language, reinstalled the app – no change to the document selection. Phone callback and multiple email exchanges with Developer Support. My questions: Which country is stored in my enrollment record? The restricted document selection suggests it differs from the country set on my Apple Account. Why are national ID card and passport not offered, and can the document selection for my record be corrected? Is there a way to get this reviewed by the enrollment or identity verification team? Could a duplicate person record under the transliterated spelling be causing both the "other account" message and the restricted document list? Case number: 20000132833454 Region: Germany I am willing to provide any identity document required – as soon as the system actually offers it. Any pointers from people who have seen the same restricted document list would be very welcome.
Replies
1
Boosts
1
Views
98
Activity
21h
DSA Trader Verification stuck "In Review" since 11 August 2026 - app blocked in all 27 EU countries
Hello, my app "YOGO Loops" (Apple ID: 6799279746) has been approved and is "Ready for Distribution", but it is unavailable in all 27 EU countries. App Store Connect > Business > Compliance shows: Digital Services Act | 27 countries or regions | Last Updated: 11 Aug 2026 | Status: In Review Pricing and Availability shows "Trader status not provided" / "Cannot sell" for all EU territories. Everything else is Active: Tax forms (W-8BEN): Active Administrative Cooperation Directive (7th amendment): Enabled Trader information (address, phone, email): submitted I am an individual developer based in Germany, so my main market is completely blocked. Apple states a review time of about 5 business days, I am now at day 38. I have already filed a support request with Apple. Has anyone had a DSA verification unstuck after a delay like this? Is there an escalation path beyond the standard support form? Thank you.
Replies
0
Boosts
0
Views
159
Activity
21h
DSA Trader compliance stuck In Review — blocking EU sale before time-sensitive event
Hi all, Our app "Na šipky!" (bundle ID cz.czechdartsopen.app, App Store ID 6802246248) was approved (READY_FOR_SALE), but is currently removed from sale in all EU territories pending Digital Services Act Trader status verification. We submitted the Trader compliance declaration and supporting documents on September 1, 2026 — status has been "In Review" since submission. This is time-critical for us: the app is the official companion app for the Czech Darts Open tournament, September 4-6, 2026, in Prague. We need EU availability (Czech Republic specifically) before the event. I've also opened a support case with Apple Developer Support (Case ID: 102950641374, submitted via Contact Us, awaiting reply) — phone support isn't offered for this topic in our region. Has anyone dealt with a stuck DSA Trader review before, and if so, how long did it take / did anything help speed it up? Any advice appreciated. Thanks!
Replies
0
Boosts
0
Views
97
Activity
21h
MusicKit playback alongside cosmetic in-app purchases: allowed under 3.3.6(D)?
I'm planning an iOS app that uses MusicKit for playback and want to confirm the setup complies with the Apple Developer Program License Agreement (section 3.3.6(D)) and App Review Guideline 4.5.2 before I build further. How music works in the app: • Songs come only from the Apple Music catalog through MusicKit. • The only prompt is the standard iOS permission request for Apple Music access. • Apple Music subscribers hear full songs. Non-subscribers hear the 30-second preview only. • The app has no sign-in and shows no subscription offers. Users manage Apple Music entirely in the Apple Music app. • Playback always starts from a user tap, with standard play, pause and skip controls. • Every playing song shows a link that opens it in the Apple Music app. • A simple on-screen animation runs while music plays, as a playback indicator only. It isn't synced to the audio, and nothing is recorded, saved or shared. • No ads, no subscriptions, and no limits on playback. How the app makes money: • Optional one-time in-app purchases of purely cosmetic visual themes. They change only how the app looks and don't unlock, improve or affect music access in any way. Questions: 1. Does selling cosmetic in-app purchases in an app like this count as "indirectly monetizing access to the Apple Music service"? 2. Is a visual animation that runs during playback (not synced to the audio) acceptable, or does it count as "synchronizing MusicKit Content with other content"? 3. For non-subscribers, is playing MusicKit's preview assets, with a link to the song in Apple Music and no subscription offer, an acceptable setup? Thanks for any guidance.
Replies
1
Boosts
0
Views
72
Activity
21h
DSA Trader Status "In Review" for 6 Days — App Blocked in 27 EU Countries
Hello, My DSA trader status compliance submission has been stuck in "In Review" since May 29, 2026 — 6 days with no update. As a result, my app Score Battle (Apple ID: 6769828159) is unavailable in all 27 EU App Store territories. Details: Individual developer account based in Germany All trader information submitted (address, phone, email) App is live in 146 non-EU countries with version 1.0.1 App Store Connect > Business > Compliance shows: Digital Services Act | 27 Countries | Last Updated: 29 May 2026 | Status: In Review I've also submitted a support request but haven't received a response yet. This is time-sensitive as my app is a football prediction game and the FIFA World Cup 2026 starts on June 11. Germany is a key market and I'm based here — I can't even see my own app in the store. Has anyone experienced similar delays with DSA trader verification recently? Any guidance on how to move this forward would be appreciated. Thank you.
Replies
0
Boosts
0
Views
81
Activity
21h
DSA Trader Verification "In Review" for 49 Days — EU Distribution Blocked
Hello, My app "Glow Mode: AI Skin Scanner" (Apple ID: 6762376419) has been blocked from distribution in all 27 European Union countries for 49+ days due to Digital Services Act trader verification stuck in "In Review" state. Current state in App Store Connect: • Business → Compliance → Digital Services Act: "In Review" since 24 March 2026 • Pricing and Availability → Manage Availability: all 27 EU countries show "Trader Status Not Provided" → "Cannot Sell" • App-level: declared as "trader app" ✓ • Account: published in 148 other countries, all agreements / banking / tax forms verified and Active Apple's stated typical review time is 5 business days. I'm at day 49. Several other developers have reported identical issues in recent threads: • https://developer.apple.com/forums/thread/822744 — DSA Review stuck • https://developer.apple.com/forums/thread/822857 — App not available in EU • https://developer.apple.com/forums/thread/818244 — Review stuck 2+ months I've also filed a support case (ID: 20000114608599) but wanted public visibility in case this is a systemic issue affecting multiple developers. Questions for Apple staff and the community: Has anyone resolved a DSA verification stuck this long? If so, how? Is there a backend status that may already show "approved" while the UI continues to show "In Review"? What is the recommended escalation path beyond the standard support form? Thanks in advance for any insight.
Replies
4
Boosts
1
Views
376
Activity
21h
App approved but EU distribution blocked due to DSA verification – is this normal?
Hello, I’m experiencing a situation with my app Waspp that I’m trying to understand. The app was approved by App Review on Feb 24, 2026 and is currently available on the App Store in the United States. However, distribution in the European Union (Belgium and France) is blocked due to the Digital Services Act (DSA) trader verification, which still shows “In Review” in App Store Connect. Some details: App Review completed: Feb 24 DSA compliance submitted: Feb 25 Status: Still “In Review” after more than two weeks Documents requested by Apple Support have already been uploaded via their secure link App availability shows “Cannot Sell” for Belgium and France The app is live and downloadable in the US Because of this, the launch of the app in the EU is currently blocked even though the app itself has been approved. My questions: Is it normal for the DSA trader verification to take this long? Has anyone experienced a similar delay with EU distribution? Is there anything else that can be done from the developer side to unblock the verification? Any feedback or similar experiences would be greatly appreciated. Thanks!
Replies
0
Boosts
0
Views
193
Activity
21h
App approved but EU distribution blocked – DSA compliance stuck “In Review”
Hello, My app “DeepTone” has been fully approved and is marked as Ready for Distribution in App Store Connect. However, the app is not available in EU countries due to Digital Services Act (DSA) compliance still showing “In Review”. details: DSA verification was submitted and confirmed as completed by Apple Developer Support (case ID available). App Review has already approved the app. The app is currently live in non-EU regions but blocked in the EU. App Store Connect still shows: Digital Services Act (DSA) compliance – In Review Encryption Self-Declaration (France) – In Review This appears to be a backend compliance status issue rather than an app review issue. Has anyone experienced a similar situation where DSA compliance remained “In Review” after approval? Is there a known escalation path or expected resolution timeframe for this? Thank you for any guidance.
Replies
3
Boosts
2
Views
354
Activity
21h
iOS submission stuck in Waiting for Review for over 48 hours after a What's New-only resubmission
Hello App Review team, Our iOS app Ohripa (version 1.5, build 25166424) has been in "Waiting for Review" since October 21, 2026 at 9:44 AM (Taiwan time, UTC+8), which is now more than 48 hours. Submission ID: 72c92e5e-3eb8-4cd7-92f2-032e093d6097 The previous submission of version 1.5 was rejected under Guideline 1.1 because of wording in the What's New text. We revised only the What's New text and resubmitted the same build (25166424). We have not received any message since resubmitting, and the Reply to App Review option is no longer available in App Store Connect while the submission is waiting. Could you check whether anything is needed from us to move this submission forward? We are happy to provide any additional information. Thank you.
Replies
0
Boosts
0
Views
19
Activity
21h
iOS 27: domain-bound SMS one-time codes are not offered in an associated app ("Could not fetch application record"), worked on iOS 26.6 and 18
Since iOS 27.0, domain-bound SMS one-time codes are no longer offered above the keyboard in our app, where the code is entered on a web page in a WKWebView, although the app is associated with the domain through webcredentials. The same SMS is offered in Safari on the same device, and it is offered in our app on iOS 26.6 and iOS 18. SMS format (last line per the domain-bound code format): Your verification code is: 123456 @app.example.com #123456Setup Several builds of the same app with different bundle IDs (App Store, internal, development), all under one team Entitlement com.apple.developer.associated-domains: webcredentials:app.example.com (plus two more environments of the same domain) AASA at https://app.example.com/.well-known/apple-app-site-association: 200, application/json, no redirect, same content on app-site-association.cdn-apple.com: {"webcredentials":{"apps":["TEAMID.com.example.app","TEAMID.com.example.app.internal","TEAMID.com.example.app.dev"]}} The code field is an <input type="tel" autocomplete="one-time-code"> in a WKWebView showing a page on that domain. We also tested a native field with the one-time-code content type (the app is built with Flutter; the field is a Flutter TextField with the one-time-code autofill hint). Steps Open the verification page in the app and focus the code field. Receive the SMS above. Expected: the code is offered in the QuickType bar, as it is in Safari on the same domain and as it is in our app on iOS 26.6 and iOS 18. Actual: nothing is offered. The keyboard log: kbd Received verification code from Messages kbd One Time Code field has been entered. kbd Retrieving Current One-Time Codes for App kbd Current verification code is domain-bound to <mask.hash: '…'>. kbd Domain-bound verification code is NOT valid for app <mask.hash: 'X'>. E kbd Could not fetch application record for application identifier: <mask.hash: 'X'>. kbd Returning 0 available one-time codesWhat we checked swcd downloads the AASA for all domains without errors after a reinstall. The installed app's entitlements (read from the device) contain the expected application-identifier and associated domains; the profile is validated. The failure is the same in the WKWebView field and in a native one-time-code field, in the App Store build, a distribution-signed internal build and a development build, and in an older app version that used to work. The masked application identifier in the log (X above) is the same for two builds with different bundle IDs, so the lookup does not seem to use the app's bundle ID. All our builds share CFBundleExecutable = Runner (the Flutter default) and the same CFBundleName. The same app build and the same SMS work on iOS 26.6 and iOS 18.x, so the change happened between iOS 26.6 and 27.0. An SMS without the @domain #code line is offered in the app on iOS 27 (Returning 1 available one-time code), although Could not fetch application record is still logged. Questions Is this a known iOS 27 regression, or is there a new requirement for apps to receive domain-bound codes? What application identifier does the keyboard use for this lookup, and can anything in the app's configuration (for example the executable name) affect it? Device: iPhone 17 Pro Max, iOS 27.0
Replies
3
Boosts
0
Views
85
Activity
21h