Just bumping this thread to note that FB10581868 has been resolved as of beta 4 and I no longer see failures for negative MPMediaItemPropertyAlbumPersistentID values. Hooray! Thanks for that. The other feedbacks mentioned this thread are still unresolved. 🤞

This happens to me too, even if I've set the function as a @MainActor. I posted about it here and submitted FB10967076 about it.

I'm having this issue too. Glad I checked the forums! I submitted FB11388263 and mentioned the other two FBs in this thread.

Disappointing that this wasn't fixed by the iOS 16 RC but I'm hoping that since it's working in iPadOS 16.1 that it will be fixed as of iOS 16.1.

I recently finished implementing programmatic SwiftUI navigation in my app and I ran into this. In my experience, it was related to using a different custom type for the navigationDestinations on different screens and having their root NavigationStack path bound to a NavigationPath. To fix it, I ended up making my own NavigationDestination enum with a list of all possible navigation destinations in my app. Now, every .navigationDestionation in my app is for NavigationDestination.self and the root NavigationStack is bound to an array of [NavigationDestination]. No more freezing!

Well isn't this interesting! With absolutely no disrespect meant to the MusicKit team, who are no doubt limited by time, resources, and internal corporate priorities us outsiders have no idea about, It is frustrating to play around with this token and see so many of the features I would love to include in my app, such as: Deleting library items Time-synced lyrics Artist images Available audio qualities The MusicKit API and web API have already come a long way towards leveling the playing field for third party Apple Music apps, but there are still lots of gaps, which can make our apps feel like second-class citizens. Maybe there are licensing issues preventing features like lyrics, but it is impossible for developers to know the surrounding context, and we are just stuck filing feedbacks and awaiting WWDC each year. If the permissions included in this token were officially supported, my app would be better for it. Here's hoping!

This is still an issue in the second beta seeds of Sonoma and Xcode.

I've been seeing intermittent crashes like this for years working with applicationQueuePlayer and now ApplicationMusicPlayer. I've heard from more users seeing this issue than usual since iOS 16.5 came out. Below is one such crash log I got today. I submitted FB12464849 just now with a couple of crash logs. Unfortunately I don't have a sysdiagnose to include, but I'll try to get one from any additional users that report issues like this. Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: FRONTBOARD 2343432205 <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:[application<com.talkingsmall.Albums>:11253] failed to terminate gracefully after 5.0s ProcessVisibility: Background ProcessState: Running WatchdogEvent: process-exit WatchdogVisibility: Background WatchdogCPUStatistics: ( "Elapsed total CPU time (seconds): 3.530 (user 2.080, system 1.450), 11% CPU", "Elapsed application CPU time (seconds): 0.008, 0% CPU" ) reportType:CrashLog maxTerminationResistance:Interactive> Triggered by Thread: 0 Thread 0 Crashed: 0 libsystem_kernel.dylib 0x20ecd3c84 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x20ece6b54 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x20ece6e2c mach_msg_overwrite + 540 3 libsystem_kernel.dylib 0x20ecd41c8 mach_msg + 24 4 libdispatch.dylib 0x1d727a20c _dispatch_mach_send_and_wait_for_reply + 548 5 libdispatch.dylib 0x1d727a59c dispatch_mach_send_with_result_and_wait_for_reply + 60 6 libxpc.dylib 0x22fb6f218 xpc_connection_send_message_with_reply_sync + 240 7 Foundation 0x1ca0f7f38 __NSXPCCONNECTION_IS_WAITING_FOR_A_SYNCHRONOUS_REPLY__ + 16 8 Foundation 0x1ca08b2e4 -[NSXPCConnection _sendInvocation:orArguments:count:methodSignature:selector:withProxy:] + 2192 9 Foundation 0x1ca089ae0 -[NSXPCConnection _sendSelector:withProxy:arg1:] + 116 10 Foundation 0x1ca089a18 _NSXPCDistantObjectSimpleMessageSend1 + 60 11 MediaPlayer 0x1dfe52108 -[MPMusicPlayerApplicationController _establishConnectionIfNeeded] + 1768 12 MediaPlayer 0x1dfe1b8dc -[MPMusicPlayerController onServer:] + 52 13 MediaPlayer 0x1dfe1a9b8 -[MPMusicPlayerController _nowPlaying] + 372 14 MediaPlayer 0x1dfe21adc -[MPMusicPlayerController nowPlayingItem] + 24 15 MusicKit 0x23b98a7d0 -[MusicKit_SoftLinking_MPMusicPlayerController nowPlayingItem] + 24 16 MusicKit 0x23bedc7f4 0x23b966000 + 5728244 17 MusicKit 0x23bedce34 0x23b966000 + 5729844 18 MusicKit 0x23bede139 0x23b966000 + 5734713 19 MusicKit 0x23bdb629d 0x23b966000 + 4522653 20 MusicKit 0x23bb12fa1 0x23b966000 + 1757089 21 libswift_Concurrency.dylib 0x1da155dd9 completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) + 1

This is still an issue in the latest builds of 16.6 and 17

Both of these are still an issue when building with Xcode 15 beta 5.

FB12301908 was resolved in beta Sonoma beta 4. Thanks to the MusicKit team for taking care of that! FB12301718 still seems to be an issue.

This shipped in 16.6 and is still an issue in the latest build of 17.

Happens for me too!

I filed FB12970187 for the same issue

This is still broken in beta 7.