After reading your post on iOS Background Execution Limits it sounds like I can't rely on BGAppRefreshTaskRequest to ensure a scheduled dose window of 2 weeks for my users. That is because "... there are common scenarios where it won’t grant you any background execution time at all!". How does Apple's Medications app ensure this 2 week window along with Local Notifications? Do they have access to an api that I don't to make it possible?

After reading your post on iOS Background Execution Limits it sounds like I can't rely on BGAppRefreshTaskRequest to ensure a scheduled dose window of 2 weeks for my users. That is because "... there are common scenarios where it won’t grant you any background execution time at all!". How does Apple's Medications app ensure this 2 week window along with Local Notifications? Do they have access to an api that I don't to make it possible?

After reading your post on iOS Background Execution Limits it sounds like I can't rely on BGAppRefreshTaskRequest to ensure a scheduled dose window of 2 weeks for my users. That is because "... there are common scenarios where it won’t grant you any background execution time at all!". How does Apple's Medications app ensure this 2 week window along with Local Notifications? Do they have access to an api that I don't to make it possible?

After reading reading your post on iOS Background Execution Limits it sounds like I can't rely on BGAppRefreshTaskRequest to update the user's dosing schedule window of 2 weeks. This is because there are "common scenarios where it won’t grant you any background execution time at all!". My question is: How does Apple Health's Medications app keep a rolling 2 week schedule window? Maybe they have access to a private api for performing more reliable background execution?

Sounds like we should be targeting iOS 18 for anything using SwiftData