I wouldn't expect calling retrieveConnectedPeripherals(withServices:) or retrievePeripherals(withIdentifiers:) on the watch to be able to retrieve peripherals connected via ASK on the phone, was that the case when both apps were using Core Bluetooth?

^ That's for the enumeration, the documentation for MPNowPlayingInfoCenter's playbackState instance property specifies it's only for MacOS under Discussion: "This property only applies to macOS. You must set this property every time the app begins or halts playback, otherwise remote control functionality may not work as expected." https://developer.apple.com/documentation/mediaplayer/mpnowplayinginfocenter/2588243-playbackstate

I was able to "fix" this crash by building the app using Xcode 16

Feedback report response: It looks like you were able to attach the crash report using Quinn’s guide: https://developer.apple.com/forums/thread/688669. Thank you for your feedback. We're closing this out as resolved. Thanks Ryan!

@Frameworks Engineer I don't see any update in the Feedback Assistant app for FB15291613 showing there's a fix in progress. Should I expect to see an update there?

I submitted this feedback report (FB13364783) last November as suggested by a DTS engineer after receiving code-level support. Was this issue ever followed up on internally? @DTS Engineer @Frameworks Engineer

Feedback report for not being able to post crash report on Apple Developer Forums: FB15292000

Feedback report: FB15291613

Then again, I'm not seeing this crash being reported in the Organizer window, which makes me suspect it's occurring somewhere external to the app. Luckily the user reporting the bug reached out to me directly via email and was able to export the logs from his watch using Xcode, it would have been quite difficult for me to provide the crash report otherwise.

I've received a video recording of the crash occurring on an Apple Watch Series 10, and it definitely appears to crash when an activity indicator is presented. I'm not able to tell whether this is the activity indicator that I present myself immediately after launching or if it's the one presented by the OS when all apps are launched. Frame 5, PUICActivityIndicatorView setColor:, does lead me to believe that it may be the activity indicator that I'm presenting as I do set its colour.

Video recording of crash on Apple Watch Series 10 42 mm: https://www.dropbox.com/scl/fi/v3m6zxdj8xybn1zlre573/watchcloud_10series_42mm_crash.mov?rlkey=ozlcs1g2cqk5r4474u5amg7w5&st=ow7pb1cz&dl=0

Thanks for your detailed response, Quinn! I'm struggling to understand how this can occur on one watch model and not another, despite running the same version of watchOS (11.0 22R349). I'm also quite curious to know whether other apps built using Xcode 15.4 (or < 16.0) are also having the same problem on the Apple Watch Series 10, and, if not, what it is about my app that's causing this crash.

Thanks for listing out these steps! I also had to add the watchOS app to the "Frameworks, Libraries, and Embedded Content" of the iOS target

This was the solution for me! CMD + Shift + K all day!

The string catalogue for my Swift Package wasn't updating until I starting using String(localized: ,bundle:) to initialize all the strings instead of just let string = "". Thanks! 🤝