Same problem… ridiculous state of the tools.

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

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

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?

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

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.

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

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!

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

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.

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.

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.

For iOS 17, I can't seem to negotiate a connection interval below 30ms. It pretty much ignores the interval parameters of the connection update request.

6 years later, CoreBluetooth still does not provide a proper API for setting the connection parameters and the L2CAP COC parameters when being a central. I'm sorry, but I don't buy that the SDK chooses the "best" parameters for the current situation. When the Apple device is the peripheral, I can get up to 100KB/sec, when the Apple device is the central, I get up to 36KB/sec, which is sub-par.

I'd applaud a proper mapping table in the documentation…