Post

Replies

Boosts

Views

Activity

Reply to App group shared user defaults
What about if I want to share a preference between a Watch App WidgetKit Extension (for Watch Face complications) and a Watch app? I don't see how any of the suggested methods would apply to a WidgetKit extension.... This has worked for me previously when sharing between iPhone App and iPhone Widget Extension.
Aug ’23
Reply to Migrating ClockKit complications to WidgetKit not working
I've found the Apple Watch Face Editor on iPhone is still not reliable when doing the WIdgetKit migration. See separate post here for details on that, any ideas welcome. As for the migration, I'm having success with the getWidgetConfiguration in my ComplicationController which conforms to the CLKComplicationWidgetMigrator I provide it the identifier for the widget configuration and I provide the Widget bundle extension identifier. Although I have widgets on iPhone and Apple Watch, I provide separate Extension targets and identifiers as I was struggling to get the right entitlements with a combined one. If there are any other details I can provide to help please let me know!
Jul ’23
Reply to Swift Charts Slow Navigation
Another +1 on this here. I'm trying to draw Charts with ~1,000 point marks and scroll through them in a page style tab view. Even on the latest devices there's noticeable lag. Was wondering if there's anything that can be done to pre-draw them, optimise the data set or something. Currently I just use: In the View initialiser: let data:[(Date,Double)] And in the view body: ForEach(0..<data.count, id: \.self) { index in PointMark( x: .value("Time", data[index].0), y: .value("Data", data[index].1) ) } Many thanks for any suggestions
Jul ’23
Reply to Complications in WidgetKit - .accessoryCorner with curved text
Right, I've submitted 2 subtly different feedback for this. One for existing SDK and one for WatchOS 10. If this isn't resolved by WatchOS 10 I'm going to be in big trouble with my users because I need to implement WidgetKit to be in the Smart Stack. But If I implement it as is, I'll loose one of my most popular Complications which will really upset users. Stuck between a rock and a hard place.... plus I did confirm in a WWDC23 lab that WidgetKit implementation is all or nothing, you cannot run ClockKit & Widgetkit complications on the same Watch. Here are the feedbacks, FB12331689 & FB12331662 🙏 for a fix
Jun ’23