I got complication pushes working in an independent WatchOS 6 app. The extra steps I took, using PushApp as an example application name:Created identifier with explicit bundle id com.example.PushApp.watchkitapp and push notifications enabled (on developer.apple.com using your developer account)Using that identifier, created a related profile PushApp watchkitappThe above steps are necessary to get rid of "device token not for topic" error. I did not use this profile explicitly for signing the project, I left it on automaticAdded Background Modes -> Remote notification capability to the PushApp WatchKit Extension target in the XCode projectAdded Push Notifications capability to the PushApp WatchKit Extension targetAnd finally:In the info.plist for the SmaHomi WatchKit Extension, add "App provides Voice over IP services" to the "Required background modes".Without this I was unable to get a PushKit token. Which is strange in my opinion.Now I am able to send complication pushes with apns-topic com.example.PushApp.watchkitapp.complication and apns-push-type complication. I also set priority to 5 and content available to 1.Update: Note that you can get error 410 unregistered when sending complicaton pushes. This can happen when the complication of your app is not active on the current watch face.

I actually have this issue, but not only in the simulator. I think though that the simulator does not know your location, but you can simulate a location (using the location icon in the debug area). Anyway, it seems that the initial setting of the trackingMode is changed by the Map view. Tracking is not active on the Map even though the @State variable used is set to .follow when initialised. I have created a button displaying if the trackingMode is .follow or not, and action code that toggles the value. When the Map is displayed, the value is not .follow. When toggled, the tracking on the Map view is activated. When NOT displaying the Map view (it's inside another View in my case) the initial value of trackingMode is .follow. Which kind of proves that Map changed the value. I'm running iOS 14.1 and Xcode 12.1 can toggle it with a button, and when I do the tracking on the map is indeed activated.

I have this too. It seems to have breakpoints enabled and hit one right from the start. If you hit "Continue program execution" in de debug area of Xcode the app will indeed continue.

My Intel MBA seems to show the same symptoms. The symptoms may start a couple of minutes after the simulator is started

I have a SwiftUI App that displays an animated gif from a weather api, using UIViewRepresentable and WKWebView. I also get this warning. I'm using the Xcode RC. I've checked the preloading solution, but not sure how I can apply this to an App with SwiftUI lifecycle.