I had the same problem with ASC not showing up and this worked for me: Step 1 - create a working dummy app: https://developer.apple.com/documentation/watchos-apps/creating-independent-watchos-apps If you follow the instructions here you can create a project from the Xcode template that will be able to upload an archive to App Store Connect. Step 2 - diff with your actual app: I then pointed my coding-agent at the working dummy app and asked it to compare the differences with my existing project's setup Step 3 - convert watch-only to companion embedded in the iOS app: 3.1. Watch target - make it a companion again: Bundle ID: com.xyz.AppName.watchkitapp (i.e. .watchkitapp) Add Info key WKCompanionAppBundleIdentifier = (the iOS app's ID) Remove WKWatchOnly SKIP_INSTALL = YES (it ships inside the host, not on its own) Add ITSAppUsesNonExemptEncryption = false (standard TLS only; stops TestFlight from stalling on the encryption question) 3.2. iOS host target: Add a target dependency on the watch app. Add a Copy Files build phase named "Embed Watch Content", destination = Wrapper, subpath = Watch, containing the watch .app. This step was easiest when copying the settings from the dummy-app from step-1 3.3. Multiplatform (important if your iOS target is SDKROOT = auto, i.e. builds iOS and macOS from one target): A watchOS app can only embed in an iOS product. Put a platform filter of "ios" on both the embed phase's file AND the target dependency, or your macOS build will try to embed a watchOS binary and break. 3.4. Archive the iOS scheme: Scheme = the iOS host app, destination = Any iOS Device (arm64), then Product > Archive. Archive type is now "iOS App Archive", and Distribute App > App Store Connect appears. The watch app uploads inside it - no separate App Store Connect record needed. TL;DR: Don't archive the watch app directly. Make it a companion (.watchkitapp ID + WKCompanionAppBundleIdentifier, SKIP_INSTALL = YES, drop WKWatchOnly), embed it in the iOS app via an "Embed Watch Content" copy phase