When attempting to authenticate with the musickit-js v3, the page that gets loaded from authorize.music.apple.com results in an error "Cannot parse response" On the desktop, this does not happen. The authentication code in question is async login() { const mkInst = MusicKit.getInstance(); await mkInst.authorize(); } Not sure if this is limited to V3, as it's technically not officially released, but figured it was worth bringing to attention.

Working with MusicKitJS V3, and with the extend key being used, I'm trying to request the animated editorialVideo in my app. this.musicKitInstance.api.music( `v1/catalog/${this.musicKitInstance.storefrontId}/albums/${id}`, { extend: 'artistUrl,composerUrl,trackCount,editorialVideo,editorialArtwork', } ) Looking at how music.apple.com does it, this appears to be the correct format, but the API never returns the editorialVideo in the response. Which stands out as the API will return the artistUrl in the response, just not the editorialVideo. Is this a limitation of the API?

When working with embedded web content inside a native app, any calls to MusicKit.authorize will not be properly authenticate. Calling authenticate will open Safari, allow the user to login, then ask for user confirmation, but the window will not navigate back to the native app. Is it expected that developers would have to enable associated domains for the native app?

I have a few reports of users with music purchased outside iTunes/Apple Music not displaying the album artwork when they play it. I was able to reproduce this on my end, but not sure why this would be happening. Is there a setting that needs to be enabled from Apple Music when adding external music? From my end, is there anything I need to when calling setQueue? async playAlbum(album: string, startPosition: number, shuffle = false) { this.toggleShuffle(shuffle); await this.mkInstance.setQueue({ album, startPosition }); await this.play(); } Right now, I just pass the album ID and call that. Should I be doing this differently?