I checked the bundle id again. Actually Push Notifications are enabled but there's no certificates for them.

Also, both APS and SignIn w. Apple were disabled in Xcode for that target.

The issue was with preview. Other people reported it too.

You ignore the fact that tech support usually don't look at diagnostic reports, test projects, screen recordings and so on. And you suggest us to waste our time waiting while somebody solves issue for us, which is very naive.

For more information, read this https://stackoverflow.com/questions/30792520/in-xcode-i-see-no-paired-apple-watch-even-though-the-watch-is-paired-and-the-w?answertab=modifieddesc#tab-top and this https://stackoverflow.com/questions/78511979/apple-watch-cant-always-reconnect threads on SO. Dozens of people wasting their time trying to connect their watch to Xcode, while they could be developing new amazing apps. Unfortunately, filling up those Feedback forms isn't very rewording.

What Xcode do you use, @AlelinApps? I don't have** Supported Intents sectio**n in my 15.4. Will check on beta...

Hi, Boris! I found your blog by your name :) If you struggle with pasting URL give a unique article or blog name so people can paste it in web search. Don't give up!

I shocked by the fact that the user have to touch "Open" button to activate the deeplink. In the case of poor connection or a hefty package the attribution will be lost.

You mean your replaced a heavy image with 50 KB one?

+1 for Springboard. It's really good with all sorts of system alerts.

Maybe stop send us to feedback assist, huh? That feedback requires videos and screenshots from us, as well as tons of text, but at the end issue gets closed without anyone even watching that video. Respect our time, because we helping to improve your product for free.

Thanks for the input. I still don't trust Apple bugreport. In the beginning of my career I reported about 15 bugs following thoroughly all the steps and providing all the logs and sometimes screenshots. Some bugs were closed due "duplicates", some were ignored for 5+ years then closed later when "outdated". Only few were actually fixed. Overall filling all that forms without any adequate feedback is a waste of resource. Since we, developers, always have OUR job to do.

And your job is to provide service to us, since we pay for all that devices, developer programs and fees. If I'd be "serious about engineering with you" I would pass the interview and become part of the team. Otherwise I suggest you to start reading forums, as all other big companies do. At least the Apple forum. Here's a 39 replies thread https://developer.apple.com/forums/thread/734694 named "Apple Watch cannot reconnect". It indicates that many people have the issue, and it worth attention.

Thanks for the answer, I'm having similar crash. What's "hopping" between executors, can you tell more about it? I thought tasks are detatched. Regarding the crash, I understand that we shouldn't use async versions of the delegate?

Oh, it exists only on iOS, but not on watchOS.