MapKit JS 401 Not Authorized (details empty) even with multiple token variants

Question

JakubHon OP

Created 9h

Replies 2

Boosts 3

Participants 2

Hi everyone, I’m troubleshooting a persistent MapKit JS auth issue and would appreciate any advice.

I have:

Active Apple Developer account/team Maps configuration created and linked Active Maps-enabled signing key Domain-restricted token setup I tested multiple JWT variants:

with origin without origin (basic example style) with and without exp exact domain and wildcard domain variants I also tested using a minimal/basic MapKit JS integration and still got the same result.

Bootstrap request:

`curl -s --compressed -D - \
'https://cdn.apple-mapkit.com/ma/bootstrap?apiVersion=2&mkjsVersion=5.81.60&poi=1' \
-H 'Authorization: Bearer <JWT>' \
-H 'Origin: https://<my-domain>' \
-H 'Referer: https://<my-domain>/...'
Result is always:`

HTTP 401
{"error":{"message":"Not Authorized","details":[]}}
Important detail:

mapkit.core.js loads successfully (HTTP 200) failure happens only on bootstrap auth Has anyone seen this exact behavior with empty details and found what was wrong? Any checklist for hidden misconfiguration points (key linkage, token generation method, domain restriction behavior, propagation timing) would help.

Boost

Answer 1

alternatebit OP

4h

Receiving the same result. Tokens that were originally working and non-expired suddenly began returning the same as the above. Tokens were all generated from https://developer.apple.com/account/resources/services/maps-tokens with accurate domains.

curl 'https://cdn.apple-mapkit.com/ma/bootstrap?apiVersion=2&mkjsVersion=5.81.60&poi=1' \
  -H 'accept: */*' \
  -H 'accept-language: en-US,en;q=0.9' \
  -H 'authorization: Bearer {token]' \
  -H 'origin: {url}' \
  -H 'priority: u=1, i' \
  -H 'referer: {url}' \

{"error":{"message":"Not Authorized","details":[]}}

I additionally have exhausted all options including generating tokens from a p8.

By all evaluation it appears to be an issue on Apple's side.

I hope this can be resolved soon, as it's been a great inconvenience, especially having recently migrated from OpenStreetMaps to MapkitJS.

0

Answer 2

seskis OP

1h

same issue its really annoying

1