FWIW, I recently managed to get a 15ms connection interval negotiated (initiated by the peripheral), so 60KB/sec is now possible with an Apple device as the central.

Nothing new, I reckon? Given that we're 8 years in with that feature request, I don't hold my breath. Still I duped the radar and am crossing fingers.

As expected, it's still broken in Xcode 18 beta 1.

Ok, this is looking good now. If my tests are not wrong (it's a bit hard to match the exact requirements), the relevant delegate call urlSessionDidReceiveChallenge is now being called in a background session!

I'd like to know this as well. It doesn't seem to documented properly.

It's a complete joke nowadays. I stopped 4 years developing for AppleWatch because of the miserable tools situation. Guess what… it's even worse these days.

But what's the secret sauce in uploading? I only get the option to export the IPA to a file.

This no longer seems to work. When I create a new standalone app, I only get a Watch App target and when trying to archive this, I only get options for exporting the archive to file. The bundlid ends with .watchkitapp, the app records are online at AppStoreConnect, there is even a screenshot in the watchOS portion of the app record. Stiil: What am I missing?

Did you manage in the last 4 years? Still seems broken here. Can only select "custom" deployment.

Any updates here? I can't seem to make "App Store Connect" as distribution mechanism available, so I can't upload the standalone app.

Same problem… ridiculous state of the tools.

Even 9 years after this doesn't seem to be available.

The problem was a corrupted empty project created by Xcode. It did NOT include the necessary iOS stub target (which seems to be important for deployment, even for a watch-only watchOS app). With another Xcode version this worked.

9 years later and it's still a problem.

FB15415457