Post

Replies

Boosts

Views

Activity

403 / 40300 "Invalid authentication" on every /me request, even with a new key and Media ID
My MusicKit setup worked for about a week, then every request that uses a Music User Token started failing with 403, code 40300, "Invalid authentication". That includes GET /v1/me/storefront. Catalogue requests with the same developer token still work. What I've tried, none of which helped: Signing in again through MusicKit JS (the sign-in itself succeeds) A new MusicKit key, twice A new Media ID with a new key tied to it Accepting the latest program agreements, then signing in again MusicKit JS in Safari gets the same refusal right after sign-in, so it isn't my server code. My Apple Music subscription is active, and I'm signing in with the account that holds it. Has anyone seen user tokens rejected like this and found the cause? I've seen a suggestion that an Apple Account password change can trigger it, but nothing about how to recover. Feedback filed as FB25575398
1
0
244
3h
403 / 40300 "Invalid authentication" on every /me request, even with a new key and Media ID
My MusicKit setup worked for about a week, then every request that uses a Music User Token started failing with 403, code 40300, "Invalid authentication". That includes GET /v1/me/storefront. Catalogue requests with the same developer token still work. What I've tried, none of which helped: Signing in again through MusicKit JS (the sign-in itself succeeds) A new MusicKit key, twice A new Media ID with a new key tied to it Accepting the latest program agreements, then signing in again MusicKit JS in Safari gets the same refusal right after sign-in, so it isn't my server code. My Apple Music subscription is active, and I'm signing in with the account that holds it. Has anyone seen user tokens rejected like this and found the cause? I've seen a suggestion that an Apple Account password change can trigger it, but nothing about how to recover. Feedback filed as FB25575398
Replies
1
Boosts
0
Views
244
Activity
3h