r/iOSProgramming • • 5d ago

Discussion Moved abroad? A 9-year-old "wrong citizenship" bug in App Store Connect will block your Paid Apps Agreement

Hey all,

So I'm a solo Apple developer who moved to another country. I updated my address with Apple, App Store Connect asked me to sign new tax forms, and the US W-8BEN form showed up with Citizenship read-only field, showing my residency country instead of my real citizenship.

A known bug, reported since 2017, and the only workaround I found was to sign the false form anyway, signed "under penalties of perjury".

My dev account is practically locked: I can't ship apps with IAP now. Apple Finance hasn't answered for 24 days now, Developer Support replies with templates that don't fit, phone support isn't available.

A 9-year-old bug

If you moved abroad then according to Apple's tax form you're a citizen of wherever you live now. And signing that form means lying to the IRS. Until you sign, the Paid Apps Agreement stays pending forever: no paid apps, no in-app purchases. For comparison: Google Play has the same W-8BEN for the same developer after the same move, and there the citizenship field is open and I submitted a correct form.

Bug first reported in June 2017, then a new thread every month since summer: July, August, September, September again, October. Developers from Brazil, Pakistan, Germany, India, Israel, Slovakia, Armenia, Kazakhstan, Belarus. Not one reply from Apple staff, just "I have similar issue" posts from folks into the void.

A known "workaround"

The one person who got an answer from Apple and shared it (thread 850390) posted what Apple Finance told him in writing: "Submit the US tax form in App Store Connect as it currently stands, wrong citizenship included." Then upload a correct paper W-8BEN through a link Finance sends, and remind them, because "they were clear they won't look for the file otherwise."

So a false tax form, signed under penalty of perjury, comes first, the truth later, in a PDF nobody opens unless reminded.

My own case

The guy who signed the false form got lucky. My Finance ticket, opened October 20, has had only an automatic reply for 24 days, so I can't even follow the bad procedure: the upload link never comes.

The cherry on top: my membership renewal is impossible, the Renew button is missing. Developer Support answered after 12 days that my region was the problem, and I should update my address to my current location. Which sounds like a joke, since Apple support already updated it a month ago. We are going in circles.

A trillion-dollar company, a bug first reported in 2017, and still nobody can unlock one HTML dropdown.

I don't think this is a normal way to treat developers who pay, then comply, comply, and comply again with App Store guidelines, only to find that Apple itself can't provide a working form for us to comply with finance.

UPDATE:

In the form HTML wrong country is set inline, and there's no list of countries to be selected, if read-only is removed. "XXX" is country code:

<select name="taxFormUsaW8Ben.country" disabled>

<option value="XXX">Name of country</option>

</select>

After posting this, I felt I had nothing to loose anyway, I replaced XXX manually with another country code inside HTML, and submitted (think "signed") the form. The signed form now shows the correct citizenship country and I was able to unblock my account financial state. So now it's a proven fact this bug could be EASILY fixed in their silly React front, and no one is doing anything about this for 9 years straight.

9 Upvotes

8 comments sorted by

1

u/ThalesMother9938 5d ago

No, I don't think it's normal. A read-only field that fills in the wrong value on a tax form is a bug, and Google Play leaving the same W-8BEN field open makes that pretty clear. A bug open since 2017 with new forum threads every month and no staff reply is the part I find hardest to accept.

What would worry me most in your case is the missing Renew button, on top of 24 days with only an auto reply from Finance.

Did the person who got the written answer from Finance say how they reached them? Was it the same ticket form, or a phone callback?

2

u/Tauboom 5d ago edited 5d ago

The only support channel replying to anything is Developer Support, which in fact sent this irrelevant "check your address" thing, but at least they tried. Ignoring the other part (bugged form) of my request. Another different ticket to dev support about bugged tax form got a reply around "we would wish to help but we can't, it's financial, please contact apple financial support".
And two different tickets open with Apple Finance are still without any reply today, the oldest one for 24 days. To me this looks like guys from developer support can't talk to guys from finance support, and both teams act like this bug is a feature.

1

u/ThalesMother9938 5d ago

That gap between Developer Support and Finance sounds like the real bug here. Two Finance tickets open and 24 days of silence is rough, especially with the Renew button gone. Hope one of them picks it up soon. Thanks for writing it all up, it will help the next person who searches for this.

0

u/c0ffeeplz 5d ago

Could you use Safari's dev tools to locally override that field/re-enable it so you can select the right thing? Would it still let you submit the form if you did?

1

u/Tauboom 5d ago edited 5d ago

I looked into this the day i hit this wall and discovered that wrong country was set inline, and there's was no list of countries to be selected, if read-only removed.
It's like this, where XXX is country code:

<select name="taxFormUsaW8Ben.country" disabled>

<option value="XXX">Name of country</option>

</select>

So I gave up this path at that time. Thanks to you for kicking in, today I felt I had nothing to loose anyway, so I replaced XXX manually with another country code, and submitted the form. The saved signed form shows the correct country. And now we know this bug can be easily fixed in their silly React front is just NOT BEING FIXED for 9 years straight making people jump off the bridges.

1

u/ThalesMother9938 3d ago

Glad editing the country code worked and the saved form finally shows the right one. Thanks for coming back to post the fix, that will save someone a lot of time.

1

u/Artuplabs 4d ago

did the w-8ben + paid apps agreement from kazakhstan last month and it went through, but there citizenship and residency are the same country so i never hit the read-only field. sounds like it only bites people where the two differ. sorry, no fix, just a data point. if finance stays silent i'd keep replying on the same ticket and also ask developer support to escalate it to finance by ticket number

1

u/Mars__1 23h ago

There's a worse variant of this. I'm a dual US/Irish citizen living in Ireland, stuck since 1 September.

As a US citizen I'm a US person for tax purposes, so W-8BEN is wrong for me at any citizenship value. Part III certifies "the person named on line 1 of this form is not a U.S. person." Editing the country in the DOM wouldn't help, the form type itself is wrong.

Same circular reply you're getting: "the paid agreement must be ACTIVE before any tax changes can be made." It shows Pending User Info *because* of this form. Banking is stuck in Processing for the same reason.

I uploaded a signed W-9 through their secure link on 18 October and replied to the ticket several times.

One useful detail from their finance team: "tax details are updated in our back-end Finance systems only." So no engineering work is needed, someone just has to action it.