We're still seeing this error in our project when building with Xcode 11.5 GM. We're not able to provide the source code, but is there any way for us to determine what code is triggering this?!dbg attachment points at wrong subprogram for function !51 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11) void (%3*, %0*, %0*, %0*, i32, %2*)* @"\01__hidden#6361_" br i1 %213, label %446, label %119, !dbg !83, !llvm.loop !276 !277 = !DILocation(line: 249, column: 2, scope: !278) !278 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !279) !278 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !279) ld: warning: Invalid debug info found, debug info will be stripped

I never tried the iOS 14.2 beta, but unfortunately silent pushes are not working for my app on the released version of iOS 14.2. They work fine on my device running iOS 13.7.

This appears to still be broken in Xcode 12.5.1 when using a watchOS 7.4 simulator and in Xcode 13 beta 1 when using a watchOS 8 simulator. Xcode 12.5 and 12.5.1 do work when using a watchOS 7.0 simulator, as @cordechasse suggested. I didn't try a watchOS 7 simulator in Xcode 13.

updateApplicationContext() is still not working for me in the simulator with Xcode 13 RC, which is preventing us from being able to see how our app looks on the Series 7 watch. @sal_from_new_york, did you ever receive any updates from Apple after they said they were able to duplicate the issue?

We're having exactly same issue with the Shortcut for our app on watchOS 8. Activating our shortcut from the Shorcuts app on watchOS 8 works fine and activating it by voice still works on watchOS 7. I originally reported the issue here and filed FB9541952 on August 20 as instructed by @edford. Unfortunately, I haven't received any follow up in that thread or in the bug report and the issue is still occurring in watchOS 8.2. I haven't tested the watchOS 8.3 beta yet myself, but another developer in the other thread says they're seeing the issue with their shortcut on watchOS 8.3 beta.

Just to follow up for others that are experiencing this issue: Activating our shortcut by voice is still not working with watchOS 8.2. Activating our shortcut from the Shortcuts app on watchOS 8 works fine and activating it by voice still works on watchOS 7. Unfortunately, I haven't received any followup from Apple, either here on the forums or in FB9541952.

We haven't seen any instances of this crash in our app on iOS 15.5, so I think it may have been finally been fixed in that release of iOS.

This appears to be a Siri Shortcuts bug with String parameters that accept multiple values, as I was able to reproduce the issue by modifying the toppings parameter in the SoupChef sample app to be a String parameter and unchecking "Options are provided dynamically". I've filed this issue as FB12150054, as it still occurs on iOS 16.5 beta 3.

I'm also seeing the issue where the Watch app on the phone seems to be showing both the ClockKit and WidgetKit complication, at least in my local development builds. I haven't tried with a TestFlight build yet (which for our app uses a different bundle identifier). This is on watchOS 10.0.1. Did Apple ever respond to your feedback or did you ever figure out how to fix that issue?

I was just now able to submit my app for App Store review. I use the same build I uploaded last night (built with Xcode 15.0.1) that was previously saying it couldn't be submitted because it was built with a beta version of Xcode.

Thanks to a tip from the developers of another app, we found that changing the deployment target of the watch app from watchOS 7 to watchOS 8, allowed the app to be installed on devices running watchOS 8. Since all devices that supported watchOS 7 also support watchOS 8, this was an acceptable workaround and we have now released an app update with this change.