I can confirm this is currently broken (Apr 2025, Xcode 16.3). If you follow the steps outline by Apple in Creating independent watchOS apps when you're ready to submit to the App store, App Store Connect will not work. Distribute App is replaced by Distribute Contents, and there is no option in the Method panel for App Store Connect or TestFlight. The only workaround seems to be to create an iOS app target. Setting the Build Settings for the iOS target to "Skip Install" again leads to breaking the distribution flow, so it seems you must submit an iOS binary if you want to sell a watchOS app. You can at least set your watchOS target to "Supports Running Without iOS Application" for your users, but it looks like you need to pass App Store Review for an iOS app, even if you are only creating a Watch app.

This is not possible, as App Store Connect has not been updated to support this. When following Apple's step by step instructions, Xcode does not display the option to submit a Watch-only app to the App Store.

Just chiming in to say this is still an open issue, and I’m seeing the same behavior. On iOS, ShareLink works as expected and attaches the payload, but on watchOS the share sheet opens (Mail or Messages), and the payload is silently discarded. Happy to test any workarounds—otherwise this looks like a watchOS-only bug.

I'm still seeing this issue (May '25, WatchOS 11.4) — the payload is getting silently discarded. Same code works fine on iOS.

Thanks for the clarification. Just to confirm my understanding: on watchOS, when using Section(_:isExpanded:content:), there’s no built-in tap gesture or disclosure indicator in the header. So while the section responds to changes in isExpanded, it’s up to the developer to provide a custom control (e.g. a Button in the header) to actually toggle that state. Is that correct? If so, I’ll go ahead and file an enhancement request. It would be helpful if watchOS offered consistent behavior with iOS here, especially for common use cases like collapsible settings or lists and the fact that DisclosureGroup is not available on watchOS. Thanks again for the quick reply.