Posts

Post not yet marked as solved
0 Replies
229 Views
Is there a way to migrate WidgetKit extensions made using dual-target watchOS apps to single-target apps? When you create a widget extension with a dual-target app, the bundle identifier includes the extra extension domain (com.company.app.watchkitapp.watchkitextension.widgets). When Xcode 15 migrates a dual-target to single-target, it removes “.watchkitextension” from both the watchOS app bundle identifier and the widget extension bundle identifier. watchOS seems to handle migrating the main app just fine, but any complications created with the dual-target do not get migrated and are just blank until the user re-configures, which would be a huge bummer to have to ship. If I try to manually set the bundle identifier back to include “.watchkitextension”, the OS rejects the installation because of the extraneous dot after the parent app’s prefix.
Posted
by bbatsell.
Last updated
.
Post not yet marked as solved
1 Replies
489 Views
Hello! I am attempting to run & debug a watchOS app on a device running watchOS 7b2 with Xcode 12b2 on macOS 10.15.5. Running the app (usually) works fine — I'm getting live CPU/Mem/etc. stats, breakpoints work, I can set environment overrides from the debug toolbar and they are reflected in the app, but I simply never get any output in the box on the right. "All Output" is selected, there is no filtering active. This has persisted across multiple restarts of all involved devices. I've even ensured that the watchOS debug logging profile is installed (though that was just a Hail Mary since it has never been required for this before). This exact same app produced logging output just fine in Xcode 11/watchOS 6. Does anyone have any other ideas or things I can try? It's making it very tough to debug things. Thanks!
Posted
by bbatsell.
Last updated
.