Is there a setting to have the symbols included in the bcsymbolmap for swift package dependencies? Without the symbols included, we are unable to symbolicate crashes that happen in our dependencies. Snippet from the generated bcsymbolmap containing Kingfisher: _$s10Kingfisher17ImageDataProviderMp __hidden#2906_ __hidden#2907_ _$s10Kingfisher26LocalFileImageDataProviderVMn __hidden#2908_ __hidden#2909_ __hidden#2910_ __hidden#2911_ _$s10Kingfisher23Base64ImageDataProviderVMn __hidden#2912_ __hidden#2913_ __hidden#2914_ __hidden#2915_ _$s10Kingfisher20RawImageDataProviderVMn __hidden#2916_ __hidden#2917_ __hidden#2918_ We tried symbolicating a crash that happened in Kingfisher and the lines were not able to symbolicate. Thread 3 name:	Dispatch queue: com.apple.root.default-qos Thread 3 Crashed: 0	 Watch Extension				 	 0x0022a91c _hidden#1323_ + 1435932 (__hidden#1531_:244) 1	 Watch Extension				 	 0x00225cc8 _hidden#1263_ + 1416392 (__hidden#326_:0) 2	 libdispatch.dylib						 0x4866ee1e 0x4866a000 + 19998 3	 libdispatch.dylib						 0x4866fed0 0x4866a000 + 24272 4	 libswiftCore.dylib						 0x6877f97a 0x6850d000 + 2566522 5	 Watch Extension				 	 0x0023f5e0 _hidden#1997_ + 1521120 (__hidden#1140_:148) 6	 libdispatch.dylib						 0x4866ee1e 0x4866a000 + 19998 7	 libdispatch.dylib						 0x4866fed0 0x4866a000 + 24272 8	 libswiftCore.dylib						 0x6877f97a 0x6850d000 + 2566522 9	 Watch Extension				 	 0x0023f4cc KingfisherManager.shared.unsafeMutableAddressor + 1520844 (__hidden#3269_:79) The symbols are also hidden for our other Swift Package Dependencies as well.

When calling HKHealthStore.startWatchApp(with workoutConfiguration: HKWorkoutConfiguration, completion: @escaping (Bool, Error?) -> Void) on the phone with a specified configuration. The watch will be launched and will call the handle method but the configuration seems to always be a default one: <HKWorkoutConfiguration:0x60000390c2c0 activity:HKWorkoutActivityTypeOther location:Unknown location swimming location:unknown lap length:(null)> This wasn't always the case and seems to have started with iOS 14 and watchOS 7. Are there any other things to try in order to get the correct confirmation to the watch.