Hello, you are not alone, I am experiencing the same issue. I have not found a solution yet.Overall the rest of tutorial worked for me, sometimes I needed to run the app in Simulator, like, for navigating between list and detail views on the watch app, the Canvas just gave me a white screen.I found one typo in Step 6 of "Creating a watchOS App".> Select the WatchLandmarkView.swiftShould be WatchLandmarkDetail.swift

Writing this question gave me a realisation how to solve it. Instead of running action block immediately from the confirmation sheet, run it in onAppear block in the main view.UpdateI have tried this approach and it did not work, it seams onApper is called too early and I get the same error. 😕

I don't think there's a way, I have asked the same question here https://stackoverflow.com/questions/62247557/accessing-system-colors-in-watchkit

I have not found a solution yet, so instead I just changed UX of my app to use another tap confirmation mechanism rather than ActionSheet, it works even better now.

Hi @haptic. My data source looks following: @Published var dataSource = [CustomIdentifiableHashableStruct]() struct CustomIdentifiableHashableStruct: Identifiable, Hashable { 	// Contains bunch of string lets } I have tried to add Codable, Equatable conformance but it didn't fixed the compilation error.

Nov 2020 Update Forgot to mention important bits, we set ENABLE_TESTABILITY to YES, and we build DEBUG for testing. The issue remains.

Thank you very much for your post. I have exactly the same issue which haunted me for months. Looks like a bug in watchOS 6 because the issue isn't happening on watchOS 7. Disabling the 2 options you mentioned in step 3 prevents my app to crash on launch.

Hello, I am sole trader in UK, I believe the right option is "Disregarded Entity". A disregarded entity is a business that is not seen as a separate entity from the business owner for tax purposes. Rather than the IRS taxing the business, the income of the business is passed through to the owner’s income tax return. In this way, the business and the owner are considered one entity. https://www.nav.com/blog/what-is-a-disregarded-entity-635010/ If a business entity (other than a per se foreign corporation) has only one owner, it is classified as either a corporation or a disregarded entity. If the single owner does not have limited liability, the non-U.S. entity is disregarded as an entity separate from its owner and the single owner should complete the applicable U.S. tax form in its own name.  https://www.citibank.com/icg/sa/emea/romania/romanian/assets/docs/W-8BEN-E_Completing_Guide_February_20150708.pdf Good luck, I hope this is helpful.

There's an easier way than suggested by sir RLKingSoftware. Call this when your app starts. UserDefaults.standard.register(defaults: ["key" : "value"]) Additional reading http://dscoder.com/defaults.html

With PHPhotoLibraryPreventAutomaticLimitedAccessAlert set to true Should a file a bug if I still see the photos picker when I change preference in the Settings app? There's no reason for my users to change selected photos because I have a custom button in the app to present the Photos picker.

Make sure that you didn't name your extension "Widget".

I can see my widget now. I have not realised that I still have to provide bundle IDs for both targets. This wasn't obvious as during the creation of the project you already provided a bundle identifier. I have kept the default suffixes (1 and 2) and prepended the ID. File `*.xcodeproj/project.pbxproj` Key 1 `PRODUCT_BUNDLE_IDENTIFIER` Key 2 `INFOPLIST_KEY_WKCompanionAppBundleIdentifier`

In case anyone wonders, I wasn't able to solve it. AFAIK there's no way to preserve the navigation stack. I ended up dismissing my first sheet before presenting a second sheet. Weirdly, I still see the warning. Luckily my UX doesn't suffer from this, it's just a warning that I am curious about. In case I would need to build an application with behaviour like Apple Mail, this would be a show stopper.

Quick update, will post full details later. I realised that I was using SwiftUI in the wrong way. My problem is that I had a view with multiple .sheet modifiers. If you present a second view, add the .sheet modifier to the second view. Essentially this should allow an unlimited navigation stack.

The issue is due to this error message The widget background view is missing. Please ensure that you have called the `containerBackground(for: .widget) {…}` modifier in your widget view. Hower I can see the background in SwiftUI preview.