Haha after answering you I actually updated the article but of course not all the images 🙈 „just resizing“ still cause some issues in some situations which is why we went for the image asset magic trick. Maybe it‘s not necessary for anyone but it was so weird that it solved some issue for us that we thought it might be worth sharing (cause who would have thought of this)

Will do!

So I got an answer from a framework engineer on Twitter and it seems that the curved text in the corner won't be supported in watchOS 9. We're supposed to work around by setting a font like .system(size: 28, weight: .semibold, design: .rounded) to get a similar text size but it won't be curved. The other "issue" with the gradient gauge was a misunderstanding of mine: I thought it's only possible to tint it in combination with a gauge style but we can of course just add a .tint(gradient) modifier

I'm sorry, my answer was misleading. The intents can be compiled in the app or an intent target but not in a separate package (which you might use for modularization). And even this is not 100% true, you could basically have all the types in a package and add the AppIntent's protocol conformances in the app/intents targets.

May I ask if your result is %@ and %d more" (localized value) or %@ and %d" (defaultValue)?

This will actually break your widgets when running the app (since the widgetFamily environment value be set to the defaultValue). See https://stackoverflow.com/a/73387184/2048453

This solution only works when updating the activity from the app. I have not found any way to make this work from the token based push notifications since upon reception the Live Activity widget is immediately rendered without ANY hooks to do some side effects. I tried sending the alert along with combinations of content-available/mutable-content to get a notification service extension to launch but nothing worked. I have no clue how one would implement encryption in live activities

I did try exactly what it said there (I have used it before for other projects) but it doesn‘t seem to work when the package contains a macro