Post

Replies

Boosts

Views

Activity

Reply to Open Health App Sources using URL Schemes
With iOS 14 I notice that when you delete an app instead of offering to delete your health data it shows an option to go into the health app where you can delete your data. That screen also shows permissions. It would be very helpful to be able to deep link to that screen for users who change their mind about what permissions they want to grant. "How do I change my health permissions?" Is a common support request for us. Anyway, the above change implies that such a link/url does exist. I wonder if anyone knows what it is?
Sep ’20
Reply to WidgetKit + CoreData with CloudKit
I haven't tried this with the new widgets, but with the old widgets I found that the widget core data instance was very slow to receive updated, as in days later. This issue was true in watchOS for a while and then it was resolved, so it may be resolved in iOS 14 too, but just something to test for. (The workaround in my case is to store the database in a shared container)
Aug ’20
Reply to onDisappear not getting called for widget
I don't work at Apple so my word isn't canonical, but my instinct is that the fact that onAppear is working is a bug. The widgets are totally static, you should imagine that they are generating a still image which is shown the user at the system's discretion. Much like the app switcher screens, or launch screens. They can't take any action on being shown or hidden, or under any other circumstance.
Jul ’20
Reply to Widget Timelines With Clock-Based App
In beta 1 it seemed like widgets refreshed from the timeline every few seconds. Since beta 2 it seems to be much less frequent, like maybe once an hour. I am fine with not updating every second, but once a minute seems quite reasonable given the low cost of the widget views. I think this will be a problem for apps which want to show timely glanceable information (for example the system clocks widget does not update every minute). I will raise a feedback.
Jul ’20
Reply to Core Data Background Context vs Main Context
I would recommend using the viewContext for everything by default. If you hit a real life scenario where this is causing an issue I would investigate how to solve that issue at that point, but it’s better to avoid complexity until you need it. (To be clear I think this is a good question and this is not an intuitive answer. I think the contexts could be better labelled as “default” and “expert” or something like that)
Jul ’20