So I am working on an unofficial standalone watchOS app with complications for the Taycan, and recently noticed that the complications weren't updating when I was asking them to.

After ~4 hours of head-scratching, I finally realized it was because I was using ClockKit to refresh my WidgetKit complications, but you're supposed to use WidgetCenter.shared.reloadAllTimelines() instead.

Enter ChatGPT:

Completely unreal.

Just fixed a doozy of a bug in watchOS' networking stack. Seems redirects don't keep track of cookies, making cookie-based auth flows fail on watchOS that otherwise succeed on iOS.

https://github.com/driven-app/porsche-connect/pull/108 fixes this by intercepting all HTTP redirects, tracking set cookies, and manually injecting them into subsequent requests.

Went down quite a few rabbit holes to figure this one out, but am excited to get authentication working on the watch at last :D

So I've always wondered why more apps don't have Apple Watch complications/apps, with the assumption being it's not a priority.

But I've been digging into this recently and my suspicion is even for apps that want to make it a priority, the barrier to entry is too high.

I've yet to find a runnable example of a fully functional app using the most modern Widget-based APIs. Most either outright don't work, or are using APIs from 2+ years ago.

An end-to-end code lab would go a long way here...