Standalone Watch App Woes

Question

Created 1d

Replies 1

Boosts 0

Participants 1

Hello

I have developed a standalone app for watchOS - trying my best to use best practices and floowing the (limited)documentation. But here I am, unable to distribute - or even Validate - my apps archive in Xcode.

As far as I can tell, bundle_id's are correct. It has an iOS wrapper (set up by New Project), Skip install has been tried in every combination.

I'm at a loss.

I'm sure there is some simple setting or workflow that I am missing, but I've been at it for days. Yes. Days.

Has anyone recently created and successfully distributed a standalone watch app that could help me troubleshoot?

I would be extremely appreciative. My kids would too. They miss their dad (just one 5 more minutes, I think I got it!)(I didn't get it)

Thank you bob

Boost

Answer 1

riftsong OP

1d

More Context:

Xcode 26.1.1

New standalone watchOS project - default settings.

There is a project with two targets - an iOS target and a watchOS target.

The iOS target is at default - no code added or taken away

all certificates and profiles point to my distribution certificate and provisioning.

The bundle_id's seem good. The Project and ios share a bundle id of "com.myteam.myapp"

The watchOS bundle id is "com.myteam.myapp.watchkitapp"

There are identifiers for both in App Store Connect.

The app compiles and runs on the simulator with no errors, all sizes, all languages.

I do not have a watch connected to the account, but the code has been tested and I can't imagine that the lack of a physical device is causing the problem

The scheme has the 3 archs in top to botton project, ios, watchOS - all marked to do everything they can and everything I see is marked to release.

This is my first swift program and xcode experience, so I am confident that the error is my understanding of the workflow.

thank you anyone who has some insight.

0