Thanks for the reply! After careful consideration, I think this modification is in line with the convention of os() conditional compilation, even if it will bring a lot of code changes. Because #if os(iOS)/os(macOS)/os(watchOS)/os(tvOS)/os(visionOS) should be mutually exclusive.

@aviwad Thanks for the update! Confirmed contentMarginsDisabled() is back deployed to iOS 15/macOS 12/watchOS 9.0.

and the warnings appeared in watchOS target.

-ld64 saves me a day. And thanks for reporting a FB! I hope Apple can fix this issue in the next beta...

Cool. The canvas setting is really helpful. Thank you very much!

I sincerely believe that the best way to solve a problem is to provide a step-by-step guide or sample code that can 100% reproduce the issue, rather than diagnostic data. Although I encountered a different issue, I noticed that every time it was related to Preview, the request was always for diagnostic data feedback. I believe this is not very efficient.

@fish aside ;hsdf; las;dlf How do you link your library in your project? I use Swift package and link the library dynamically. And I saw this warning only on beta 3.

Yes... Solve it by Edit Scheme > remove the iOS main app target from the watchOS scheme. I don't know why it's selected by default...

Proposal: Simple Text("...") in corner should be always rendered as a curved text. If you need a regular text style, wrap it with a VStack or something.

Up vote.

@oscb does not work in preview 😫

👍 Very helpful. Thank you!

+100 for this

Hello! I haven't made any substantial fixes. However, I haven't received any similar issue feedback in the past few months. It looks like this issue may have been fixed in a certain watchOS version, or the issue only occurred during the upgrade process from watchOS 8 to watchOS 9.

Thanks for the reply. 🤯 I don't think complicationForeground() should match widgetAccentable(). They should be the opposite. Because for the Apple Watch, the foreground should be the most prominent white and the background should be tinted.