Post

Replies

Boosts

Views

Activity

Reply to MapKit JS 401 Not Authorized (details empty) even with multiple token variants
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.
5h
Reply to MapKit JS 401 Not Authorized (details empty) even with multiple token variants
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.
Replies
Boosts
Views
Activity
5h