The template app currently enforces to be logged into a user account. Once you log out from the account, a sheet pops up requiring you to sign back in, before you can continue to use the app.
While this works as expected, the Schedule is not paused. For example, the app continues to deliver notifications to complete the social support questionnaire.
Reproduction
Onboard the app.
Logout from your account.
Wait till 8am to get a schedule notification delivered.
Expected behavior
It would be expected that the app clears all currently queued scheduled notifications and only reschedule them once the user signs back in. This (probably) requires an additional API surface in SpeziScheduler module and some additional account related handling in the ScheduleView.
Additional context
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct and Contributing Guidelines
Description
The template app currently enforces to be logged into a user account. Once you log out from the account, a sheet pops up requiring you to sign back in, before you can continue to use the app. While this works as expected, the Schedule is not paused. For example, the app continues to deliver notifications to complete the social support questionnaire.
Reproduction
Expected behavior
It would be expected that the app clears all currently queued scheduled notifications and only reschedule them once the user signs back in. This (probably) requires an additional API surface in SpeziScheduler module and some additional account related handling in the
ScheduleView.Additional context
No response
Code of Conduct