“Apple Maps Guides”

The behavior you're seeing — processContentKeyRequest(withIdentifier:initializationData:options:) silently skipping a repeated call for the same identifier — is not explicitly documented. The SDK header for this method describes it as a way to generate an AVContentKeyRequest from request initialization data already in hand, without awaiting such data during the processing of media data of an associated recipient — but says nothing about what happens on repeated calls for the same identifier. For your use case — proactive offline license renewal when you only have the identifier and no live AVContentKeyRequest — there are two approaches to consider: Revoke the content key, then re-request (iOS 17.4+) If you can target iOS 17.4 or later, AVContentKey.revoke() is likely the best fit. The SDK header states explicitly: Once revoked, the AVContentKey is no longer eligible to be used with any media. If the key is required again, or if the key is requested to be loaded by the application, a new AVContentKeyRequest wi

I just checked on FB22286320 and it seems that you pushed back on this. Thanks. Given that there’s a workaround for the immediate issue, I think your bug report is the right path forward for future improvements. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks @kelin Yeah in Apple Watch there are still a few limitations. There is a good documentation to see the difference and how to test per device: https://developer.apple.com/documentation/xcode/allowing-apps-and-websites-to-link-to-your-content/#Support-universal-links openSystemURL(_:) in watchOS I think you finding the limitations of what app will open. I would recommend to fill an enhancement request for the watch if you want to behave like an iOS device: If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

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.

Hi, the Apple Support team, just wanted to let everyone know that I also have an open support case (Case ID: 102861576902) related to this issue. Unfortunately, the system no longer allows me to add comments to it directly, so I just wanted to make sure it's visible here. Hoping it gets picked up soon — thank you all for your patience and support! 🙏

Not only you. I currently have 2 app updates still stuck in Waiting for Review, and another app has been sitting there for more than 30 days. I’ve already tried resubmitting, contacting support, and submitting expedited review requests, but nothing has helped. I know Apple probably has a huge number of submissions, but it’s still very frustrating when my apps are stuck for weeks while friends get new apps reviewed in 1–2 days and updates approved within hours. It honestly makes the whole review process feel very unfair and discouraging.

Step 1: Account Registration and Setup: Creation and validation of the account in the Apple Developer Program. Without an active and regularized account, the process cannot begin. Step 2: Development Entitlement Request: Completion of the Apple form to download the Payment Service Provider (PSP) — in this case, Stripe — and the regions of operation. Step 3: Design and Construction (Development Phase): Technical implementation following the High-Quality Guideline (HIG) and functional requirements. Step 4: Publication Right Request: Audit phase where Apple reviews the workflow recording and delivery to meet the requirements to allow distribution via TestFlight and the App Store. Step 5: Submission and Release: Final App Store review and publication for general availability (GA).

If apple community support or developer support is reading this, Please ensure that my request is carried out and my developer account is terminated and that this is escalated to the appropriate teams to process and carry this out. I have already tried contacting developer support through the developer website and choosing the correct categories and no response and case gets close so please make sure that my apple developer account is permanently terminated and deleted.