Hi there, I’m developing a watchOS app using SwiftUI, and I want to allow users to interact with the map using the panning gesture and also drop waypoints by long pressing anywhere on the map—just like in the built-in Apple Maps app on watchOS, where a long press drops a pin and panning still works seamlessly. However, with SwiftUI’s Map, any attempt to attach a gesture other than .onTapGesture (such as LongPressGesture or DragGesture) seems to block the built-in map interactions, making panning impossible. Is there a supported approach to detect long press gestures anywhere on the map while still allowing all standard map interactions (as seen in Apple Maps on watchOS)? Or is this something only possible with private APIs or internal access? Any guidance or best practices would be greatly appreciated! Thank you!

Id like to provide haptic feedback to users on Apple Watch without playing any sound (for my meditation app). The only way I found to play haptic feedback is WKInterfaceDevice.current()play(.start) but this produce sound as well. Apple's Mindfulness app has haptic feedback without playing any sound. Is there a way how to achieve it? Thanks!

Hi, I have a framework (in form of cocoa pod) which calls in one if its class [NSBundle bundleForClass:self.class]. When I build & run the app locally, everything works as expected, bundle of the framework is being returned. This is not a case when I publish the app to TestFlight where app's bundle is being returned (bundle of the app that uses that framework). This started to happen only after I started using Xcode 13 for archiving, before on Xcode 12 everything worked fine (bundle of the the framework was returned). Wanted to ask if this is an expected behaviour when using Xcode 13? Why the behaviour is different for running app locally and the app archived and published on TestFlight? Thanks for your help! Robert