Could not launch app on watchOS downloaded from TestFlight

Does anyone have the same issue? Recently the app has been transferred to another developer account, not sure if it is related, this TestFlight version was rebuilt with the new team

This is indeed quite strange. Would you mind to file a feedback report, attach your sysdiagnose to the report, and then share your report ID here? I'd hope that looking into the sysdiagnose may find some hints about why the app became untrusted.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

Thanks, I have filed feedback, Case-ID: 19339644

@ppwqgtl I have replied to you on the case number. Thanks

Albert
  Worldwide Developer Relations.

We are seeing what looks like the same issue with our TestFlight watchOS app.

In our case the watch app is paired with an iOS app and was installed from TestFlight. The watch app launched successfully earlier on the same device and same installed build, including from a complication, and successfully recorded/transferred data. Later, tapping the app icon or complication did nothing.

We reproduced the failure from the Mac with devicectl device process launch and got:

The application failed to launch. (com.apple.dt.CoreDeviceError error 10002) BundleIdentifier = <watch app bundle id> FBSOpenApplicationServiceErrorDomain error 1: RequestDenied FBSOpenApplicationErrorDomain error 3: Security Unable to launch because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user.

A few details that may be useful:

• The same TestFlight build had launched successfully earlier on the same watch.
• The app was still listed as installed by CoreDevice.
• The companion dev/watch build could still launch on the same watch.
• There was no app crash and no app startup log from the failed launch, so it appears to be denied before our process is created.
• The production complication extension still appeared to be present/running in sysdiagnose, but the main watch app launch was denied.
• Deleting and reinstalling from TestFlight fixed a previous occurrence for us.
• We also saw MobileInstallation/AppConduit logs showing the TestFlight watch app install succeeded and launch was explicitly enabled before the later launch denial.

We have captured a sysdiagnose while the watch was still in the bad state, plus the devicectl launch JSON/log output. This looks consistent with the app becoming untrusted locally on watchOS/TestFlight after it had already been installed and launched successfully.

I’m happy to file a Feedback with the sysdiagnose and share the Feedback ID here if that helps correlate this with the case above.