MapKit JS token returns 401 only for mainland China while Apple's official sample works

Hello Apple engineers,

Feedback Assistant report: FB25612837 (submitted under our developer team).

We are investigating a production Web MapKit JS authorization failure. Our native iOS App works normally; this report concerns Web MapKit JS only.

Observed on 14 November 2026:

  • Our portal-generated MapKit JS token returned HTTP 401 for mainland-China bootstrap authorization and HTTP 200 for US authorization.
  • Apple's official embedded-map example worked in the same browser and network, returning countryCode CN and displaying Amap attribution.
  • A minimal page using SDK 6.1.205 on our production Web domain also returned 401. SDK 5.81.72 had the same result.
  • Exact-domain, wildcard-domain, expiring, and temporarily unrestricted diagnostic tokens produced the same China-only failure. The unrestricted token was revoked immediately after the test and was never deployed.

Rechecked on 17 November 2026:

  • The locally configured production token, whose hash matches the token inspected in production on 14 November, still returns HTTP 401 with {"error":{"message":"Not Authorized","details":[]}}.
  • It uses ES256, scope mapkit_js, and an origin matching our Web domain pattern. It is not expired and has no duplicate header or payload claims.
  • Separately configured root-domain MapKit JS tokens also return 401 when tested with their matching origin.
  • These 17 November probes used locally configured tokens; the authenticated production token value was not freshly read back that day.

We found matching reports:
https://developer.apple.com/forums/thread/766180
https://developer.apple.com/forums/thread/748764
https://developer.apple.com/forums/thread/684701

We checked the duplicate-claims fix described here and ruled it out for our configured token:
https://developer.apple.com/forums/thread/113670

Questions:

  1. Is any additional team provisioning or authorization required for the mainland-China MapKit JS service?
  2. Can regional validation treat portal-generated tokens differently, despite the same token being accepted by another region?
  3. Is there a supported corrective configuration we can apply? We have not found one in the current Maps token documentation.

Developer Support case 30000015236904 directed us to the forums. We can provide account-specific details privately through Feedback Assistant. This public question intentionally omits tokens, private keys, account identifiers, customer data, and production logs.