Hi, I've been working on a Widget Extension which works great locally (when installed via Xcode) but it crashes when distributed via TestFlight. Most of the crashes occur at WidgetExtensionContext.getDescriptors(completion:) Here's the crash log: 0	 WidgetKit										 0x00000001e556952c closure #1 in WidgetExtensionContext.getDescriptors(completion:) + 208 (WidgetExtensionContext.swift:85) 1	 WidgetKit										 0x00000001e55694ac closure #1 in WidgetExtensionContext.getDescriptors(completion:) + 80 (WidgetExtensionContext.swift:85) 2	 WidgetKit										 0x00000001e55688dc thunk for @escaping @callee_guaranteed () -> () + 28 (<compiler-generated>:0) 3	 libdispatch.dylib						 0x00000001a4aac410 _dispatch_call_block_and_release + 32 (init.c:1454) 4	 libdispatch.dylib						 0x00000001a4aadf08 _dispatch_client_callout + 20 (object.m:559) 5	 libdispatch.dylib						 0x00000001a4abb480 _dispatch_main_queue_callback_4CF + 836 (inline_internal.h:2548) 6	 CoreFoundation								 0x00000001a4d8e634 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16 (CFRunLoop.c:1790) 7	 CoreFoundation								 0x00000001a4d88c34 __CFRunLoopRun + 1940 (CFRunLoop.c:3118) 8	 CoreFoundation								 0x00000001a4d88090 CFRunLoopRunSpecific + 564 (CFRunLoop.c:3242) 9	 Foundation										 0x00000001a5124310 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 232 (NSRunLoop.m:374) 10	Foundation										 0x00000001a5156d68 -[NSRunLoop(NSRunLoop) run] + 92 (NSRunLoop.m:399) 11	libxpc.dylib									 0x00000001a4a0a6ac _xpc_objc_main + 688 (main.m:265) 12	libxpc.dylib									 0x00000001a4a0c984 xpc_main + 180 (init.c:1198) 13	Foundation										 0x00000001a5159068 -[NSXPCListener resume] + 316 (NSXPCListener.m:448) 14	PlugInKit										 0x00000001b44658a0 -[PKService run] + 424 (PKService.m:186) 15	PlugInKit										 0x00000001b44654e0 +[PKService main] + 576 (PKService.m:115) 16	PlugInKit										 0x00000001b4465cac +[PKService _defaultRun:arguments:] + 24 (PKService.m:233) 17	ExtensionKit									 0x00000001e77f7d8c EXExtensionMain + 84 (EXExtensionMain.m:23) 18	Foundation										 0x00000001a52a02b8 NSExtensionMain + 200 (NSExtensionMain.m:13) 19	libdyld.dylib								 0x00000001a4c13f08 start + 4 I've seen multiple reports about the 3rd party widgets not appearing for TestFlight builds in the PB3, but I am not sure if this is related. What can I do to solve this? Thank you!

Hi, I have a breathing app that includes a sleep breathing exercise, and I want to suggest that as a "Wind Down" shortcut. I have set the shortcut availability to sleepMindfulness but whenever I do INVoiceShortcutCenter.shared.setShortcutSuggestions([shortcut]), I get the following error in Xcode: [default] +[LSApplicationProxy applicationProxyFor*] is not a supported method for getting the LSApplicationProxy for the current process, use +[LSBundleProxy bundleProxyForCurrentProcess] instead. I am currently on Xcode 12b4. Any help would be appreciated, thanks!

Hi, I have an app with a root HostingController having "Full Screen" enabled. It works perfectly find on WatchOS 6 but with WatchOS 7, the content under the nav bar gets hidden behind a black strip as if "Full Screen" isn't working at all. Has anyone else faced this issue?

Hello, I am trying out Xcode Cloud for the first time. I could connect to Github in the initial setup and had a few failed builds (package resolution error), which I resolved fairly quickly. Now whenever I am trying to build, I get the following error: Xcode Cloud is unable to connect to the repository “<respository-name>”. Reconnect the repository to resume builds. I am unable to remove the connection from settings as well because it's stuck in a loading state. Is there a way to fix this?

Hi, When we try to build our app on Xcode Cloud, after the app finishes archiving, we get the following error: ITMS-90486: Invalid WatchKit Support. The expected app is missing from the app’s root location, such as /Payload/[AppName].app/Watch. How can we fix this? We have an iOS target + a dependent watchOS target. Thank you!

I am creating a workouts based watchOS app where it also be launched from the companion iOS app. HealthKitStore's startWatchApp works as it launches the watchOS app, but it starts in the always on state. In the always on state, the main view's body never renders and the screen stays blank (with time in the upper right corner). This seems to be a problem with SwiftUI lifecycle based apps as my earlier Storyboard app seems to be rendering the view just fine in the always on state. I test the same behavior in the watch simulator. If you launch a watch app in the always on state, it appears blank until you either click on the screen or press the crown. Is this a bug?

Hi, I recently updated my watch and phone to watchOS 9.1 and iOS 16.1 beta 3, and now my Xcode 14.0.1 is not able download the debug symbols for watchOS. It just gives me the following error: Apple Watch via iPhone: Failed with HTTP status 403: forbidden I've tried restarting all the devices + restoring both iOS and watchOS but the issue persists. I am unable to continue development on watchOS anymore. Is there a solution to this?