@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.

Thanks for the information! 👏

These users have been unable to solve the problem by re-adding complications, or even reinstalling the watch app.

Unfortunately, I was unable to reproduce this issue in a development environment. However, I continue to receive feedback and screenshots from a few users. The logs collected from my app confirm that WKExtension is running correctly, but the ComplicationController methods does not seem to be called by the system, even though the user has added this app's complication.

👏TIL

🤔 Have you tried clearing the cache?

I didn't find any solution. I used Introspect library to workaround it in the UIKit world. It doesn't look like Apple is recognizing the issue, as I haven't received any response to my FB. Please submit another FB if it is convenient. Thanks.