Post

Replies

Boosts

Views

Activity

sessionToken.contentProviderPublicId is null — iTC backend 403s, can't sign Paid Apps Agreement
I'm the Account Holder on an individual developer account and I've been blocked from signing the Paid Apps Agreement for over a month. Digging through the network/console, this looks like a backend session-binding bug, not a UI bug. Symptom (in browser): App Store Connect → Business → Paid Apps Agreement → "View and Agree to Terms" → tick the box → Agree → page reloads with no confirmation. Console shows: HTTP 403 on /WebObjects/iTunesConnect/.../locales/en-US (the legacy iTC backend) TypeError: Failed to execute 'removeChild' on 'Node' "An array is needed to render meta tags" Root cause (looks like): the session token returned by /WebObjects/iTunesConnect.woa/ra/user/detail has sessionToken.contentProviderPublicId = null, even though the same response contains a valid publicId in associatedAccounts[0].contentProvider. Because team-scoped iTC backend calls authorize via the publicId in the session token, with it null every team call 403s and the agreement page can't load. This reproduces 100% in a fresh Safari Incognito after a clean re-login — so it's not cookies, cache, or extensions. My roles are Legal + Admin, isLegalUser is true, permittedActivities includes Contracts and AgreementsTaxAndBankingGeneral — so it's not a permissions issue either. The Free Apps Agreement is Active on the same account; only the Paid one is blocked. Developer Support has been looping on browser-troubleshooting suggestions. Filing Feedback Assistant now with the JSON dumps. Questions for anyone who's seen this: Has anyone had sessionToken.contentProviderPublicId return null and resolve without Apple resetting it on the backend? If you got Apple to fix it, who did you reach / what was the magic word? Any known cause for the publicId not binding to a session token (account migration, account creation flow, country change, etc.)? Happy to share the JSON privately with Apple staff looking at this.
1
0
106
Jun ’26
Cannot sign Paid Applications Agreement — "Agree" reloads with a 401, blocking all submissions (1+ month)
I'm the Account Holder and I've been stuck for over a month. In App Store Connect → Business → Paid Applications Agreement, I tick "I have read and agree" and click Agree — the page just reloads, no confirmation, status never goes Active. Because of that, my app gets rejected and my In-App Purchases are returned. In the Network tab, the submit request comes back 401 Unauthorized. Already tried (no effect): Signing from both the Business tab and the Agreements page Safari, Chrome, Firefox — private windows, no extensions, no VPN, cookies/cache cleared Re-saved my legal address; Tax and Banking sections are complete Confirmed I'm the Account Holder Developer Support hasn't resolved it. Has anyone hit this exact 401 on agreement signing — and what actually fixed it? A backend reset from Apple, some account/role detail, or did it just clear on its own after a while?
1
0
248
May ’26
sessionToken.contentProviderPublicId is null — iTC backend 403s, can't sign Paid Apps Agreement
I'm the Account Holder on an individual developer account and I've been blocked from signing the Paid Apps Agreement for over a month. Digging through the network/console, this looks like a backend session-binding bug, not a UI bug. Symptom (in browser): App Store Connect → Business → Paid Apps Agreement → "View and Agree to Terms" → tick the box → Agree → page reloads with no confirmation. Console shows: HTTP 403 on /WebObjects/iTunesConnect/.../locales/en-US (the legacy iTC backend) TypeError: Failed to execute 'removeChild' on 'Node' "An array is needed to render meta tags" Root cause (looks like): the session token returned by /WebObjects/iTunesConnect.woa/ra/user/detail has sessionToken.contentProviderPublicId = null, even though the same response contains a valid publicId in associatedAccounts[0].contentProvider. Because team-scoped iTC backend calls authorize via the publicId in the session token, with it null every team call 403s and the agreement page can't load. This reproduces 100% in a fresh Safari Incognito after a clean re-login — so it's not cookies, cache, or extensions. My roles are Legal + Admin, isLegalUser is true, permittedActivities includes Contracts and AgreementsTaxAndBankingGeneral — so it's not a permissions issue either. The Free Apps Agreement is Active on the same account; only the Paid one is blocked. Developer Support has been looping on browser-troubleshooting suggestions. Filing Feedback Assistant now with the JSON dumps. Questions for anyone who's seen this: Has anyone had sessionToken.contentProviderPublicId return null and resolve without Apple resetting it on the backend? If you got Apple to fix it, who did you reach / what was the magic word? Any known cause for the publicId not binding to a session token (account migration, account creation flow, country change, etc.)? Happy to share the JSON privately with Apple staff looking at this.
Replies
1
Boosts
0
Views
106
Activity
Jun ’26
Cannot sign Paid Applications Agreement — "Agree" reloads with a 401, blocking all submissions (1+ month)
I'm the Account Holder and I've been stuck for over a month. In App Store Connect → Business → Paid Applications Agreement, I tick "I have read and agree" and click Agree — the page just reloads, no confirmation, status never goes Active. Because of that, my app gets rejected and my In-App Purchases are returned. In the Network tab, the submit request comes back 401 Unauthorized. Already tried (no effect): Signing from both the Business tab and the Agreements page Safari, Chrome, Firefox — private windows, no extensions, no VPN, cookies/cache cleared Re-saved my legal address; Tax and Banking sections are complete Confirmed I'm the Account Holder Developer Support hasn't resolved it. Has anyone hit this exact 401 on agreement signing — and what actually fixed it? A backend reset from Apple, some account/role detail, or did it just clear on its own after a while?
Replies
1
Boosts
0
Views
248
Activity
May ’26