Additional impact: Apple Music 6.5.2 authentication regression prevents playback of newly released music I want to emphasize the urgency and practical impact of this issue. Apple Music 5.2.1 can still complete MusicKit for Android authentication, but it cannot reliably play some newly released songs whose current Apple Music catalogue IDs are larger than the range handled successfully by that older player. For example, newly released tracks returned by the Apple Music API have valid catalogue/playback IDs such as: 6778161147 6797908352 6798544240 The API returns valid metadata, playParams, duration, and preview information for these records. PartyAux preserves the complete ID as a string and passes it to MusicKit without truncation or numeric conversion. However, with Apple Music 5.2.1, the selected item may be acknowledged while playback position never advances and no audio begins. Older catalogue IDs continue to play on the same device. Updating to Apple Music 6.5.2 is not currently a solution because MusicKit authorization stalls inside Apple Music’s SDKLandingActivity. It remains on the loading spinner and never returns a Music User Token. If the user presses Back to escape, the calling application receives: RESULT_CANCELED music_user_token_error=0 TokenResult.isError=true TokenResult.error=USER_CANCELLED musicUserToken=null This leaves Android MusicKit applications trapped between two incompatible outcomes: Apple Music 5.2.1 authenticates, but cannot reliably play some newly released catalogue records. Apple Music 6.5.2 should support the current catalogue, but its MusicKit authorization handshake does not complete. There is no viable application-side workaround for newly released songs. Catalogue IDs cannot be truncated or replaced because Apple documents them as string identifiers, and the Apple Music API does not provide third-party applications with an alternative full-track streaming mechanism. Please prioritize a fix for the MusicKit authorization flow in Apple Music for Android 6.5.2 or provide an updated, supported Android MusicKit authentication SDK. This regression now prevents third-party Android MusicKit applications from both authenticating with the current Apple Music app and reliably supporting newly released music. Existing Feedback report: FB24599163 Related Feedback report: FB24520173 Related forum thread: https://developer.apple.com/forums/thread/838633

I completed another controlled test with Apple Music 6.5.2. Environment: Google Pixel 8 Android 17 / API 37 Apple Music 6.5.2, versionCode 1586 musickitauth-release-1.1.2.aar Standalone minimal reproduction app The developer-token endpoint returned HTTP 200. Apple Music opened SDKLandingActivity, then logged: ams.error Code 8: failed to load the Mescal prime session ams.network Code 303: failed to parse a Finance response Missing bag key: isEligibleForPhoneCreate WebContainer subsequently reported Bootstrap: Succeeded Despite reporting a successful bootstrap, SDKLandingActivity remained on its loading spinner. It did not show consent or return any Activity result. After approximately 66 seconds, I pressed Back to escape the stuck screen. Only then did the caller receive: resultCode=RESULT_CANCELED music_user_token_error=0 TokenResult.isError=true TokenResult.error=USER_CANCELLED musicUserToken=null This independently confirms the 6.5.2 non-terminating authorization behavior. The USER_CANCELLED result is generated only after the user presses Back to escape Apple Music’s stalled SDK screen; it is not the original cause of the failure. The same standalone application and developer-token service successfully returned a valid Music User Token with Apple Music 5.2.1.

I can confirm the same regression with a standalone minimal reproduction app. Environment: Device: Google Pixel 8 Android: 16 / API 36 Apple Music: 6.5.0 (versionCode 1580) MusicKit authentication AAR: musickitauth-release-1.1.2.aar Developer token endpoint returns HTTP 200 Developer token was tested with two separate Apple Media Services keys/configurations The user completes Apple Music sign-in and does not cancel. Logcat then shows: Successfully authenticated the account. Successfully completed IdMS authentication AMSIDMSAuthenticationCompleteAction succeeded Failed to post account changed event: ams.error Code 1 DialogConnectorViewModel.cancelAction() The Activity subsequently returns: resultCode = RESULT_CANCELED returned Intent = non-null Intent extras = [music_user_token_error] music_user_token_error = 0 TokenResult.isError = true TokenResult.error = USER_CANCELLED musicUserToken = null The same result occurs in both the production application and a brand-new minimal Android app using Apple’s documented authentication flow. It also persists after using a completely new Media ID, private key, and Key ID. The equivalent iOS authentication works with the same backend. This appears to be an Apple Music 6.5.0 Android regression after successful IdMS authentication, specifically during the internal account-change/dialog completion step. The SDK is reporting a user cancellation even though the user completed authentication. Could Apple please confirm whether this is a known issue and whether an Apple Music Android update is planned? Update: I downgraded the Apple Music Android app from 6.5.0 to 5.2.1 using APKMirror. Without changing my application, backend, developer token, Media ID, or Media Services key, authentication immediately succeeded. RESULT_OK was returned, TokenResult.isError=false, and a valid Music User Token was received. Upgrading back to 6.5.0 reproduces the USER_CANCELLED failure. This strongly indicates the regression was introduced in the Apple Music 6.5.0 Android app.

Update: I downgraded the Apple Music Android app from 6.5.0 to 5.2.1 using APKMirror. Without changing my application, backend, developer token, Media ID, or Media Services key, authentication immediately succeeded. RESULT_OK was returned, TokenResult.isError=false, and a valid Music User Token was received. Upgrading back to 6.5.0 reproduces the USER_CANCELLED failure. This strongly indicates the regression was introduced in the Apple Music 6.5.0 Android app.