Still very much broken for me. Unfortunately I think it's an intermittent problem which is letting the occasion build through and is thereby convincing people who just tried something random that they found a "fix".

Hi @JoeKun. Is there any update on this issue? My app adds Apple Music tracks to playlists and is seeing a similar problem. Basically it gets an http 20x reply (indicating success) after adding tracks to a playlist but some of the tracks are not actually getting added. Seems to have started in the last couple of weeks and only impacts certain users. Am very concerned in case this is a new server api release which is being rolled-out to a few initial servers. A lot of apps depend on this endpoint and it seems completely broken at the moment for impacted users. Thanks!

I've just noticed the detail text for the error is: "Conformance of 'Playlist' to 'MusicLibraryRequestable' has been explicitly marked unavailable here (MusicKit.Playlist)" Is the new MusicKit functionality not yet working on Catalyst? Surely we can't have reached Beta 3 without this working?!

Am going to answer my own question here for when others hit the same issue: according to both the documentation and my direct experience, these new MusicLibrary calls are NOT supported on macOS Ventura, either natively or via Catalyst. They are only supported on iOS-derived platforms. I find it deeply concerning that new APIs are being introduced which aren’t available on Catalyst in particular. It calls into question Apple’s commitment to the platform - I’m surprised this hasn’t received more publicity.

Apologies if it's a bit obvious but probably the first thing to check is that you've actually granted permission for your app to access Apple Music on your Mac. i.e. in the System Preferences app, Security & Privacy -> Privacy -> Media & Apple Music. Is your app listed there and is access enabled? Just to confirm, this call is working Ok for me on Ventura (unlike any of the newer MusicKit functions).

I hit the exact same error (see here). By the way you might want to try adding the MusicKit tag to your post. So far for the WWDC22 enhancements to MusicKit I’m finding: Catalyst isn’t supported, period iPad is meant to be supported but doesn’t work iPhone kind-of works but good luck getting any help or support when you have questions I’m disappointed, to put it mildly.

I’ve created FB11529157 for this

Still broken in iPadOS 16 beta 9 (20B5050f)

Seems fixed in iPadOS 16 beta 10 (20B5056e)

It’s the same app and same IAP. Catalyst allows you to do this.

Thank you - requested details now added to FB11733455. Unfortunately I can't provide a sysdiagnose as we are unable to reproduce (it works fine in our dev & test environments). We will look in to implementing "Proactive Restore" - it looks like a much smoother process for our customers.

I'm getting this too, on 14.1 RC2. Errors flash-up in the Issue Navigator, then vanish, leaving you with a failed build and no clue as to why. These last couple of Xcode builds have been virtually unusable. Can someone at Apple PLEASE look at this urgently.

We are seeing this too

Hi - is there any update on this please? I've just added additional details to FB11733455 as error reports are continuing to come in from users.

I’m seeing this too: the call arbitrarily blows-up when saving larger playlists. There doesn’t seem to be a specific upper limit - sometimes 3,000 tracks will fail, other times 6,000 tracks will work fine. Suspect it depends on server loads (fyi 500 is a gateway error). It wouldn’t be so bad if you could break the call up and add to a playlist chunk by chunk but the “new” MusicKit call to add to a playlist is completely unusable as it seems to map to the old (comically slow) MPMediaPlaylist.addItem method. The other interesting thing you will find is that if you read the playlist tracks immediately after creating a new playlist, there aren’t any. They come along a few seconds later. So much for async/await. Worse still, if there’s a failure between when the call apparently “succeeded” and when the tracks subsequently appear, it’s completely silent. You just end up with a playlist with no tracks. I get the impression that Apple are not eating what they cook when it comes to MusicKit. And incidentally all of the above issues have been reported by me via Feedback Assistant for months without so much as an acknowledgement.