Update notification preferences when fragment is created #7469
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update notification preferences right away instead of waiting for it to happen in
onResume()
.The notification preferences were initially disabled and only enabled after the current state has been read from the
NotificationChannel
.thunderbird-android/app/ui/legacy/src/main/java/com/fsck/k9/ui/settings/account/AccountSettingsFragment.kt
Lines 250 to 273 in cba9ca3
However, calling
updateNotificationPreferences()
is skipped when the user returns from setting the notification sound.thunderbird-android/app/ui/legacy/src/main/java/com/fsck/k9/ui/settings/account/AccountSettingsFragment.kt
Lines 102 to 111 in cba9ca3
This could lead to the notification preferences never being enabled when the activity was recreated while returning from the system screen to set a notification sound (see #7468).
Fixes #7468