You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, notification channel ids contain the Update.number constant in order to be able to change the placeholder text. Whenever the Update.number constant is changed in a release, the old channels are removed then new channels are added (for example channel amicale7 could become amicale8), allowing the text to be changed.
This likely has the consequence of losing the setting. If a user disables certain notifications, they expect them to stay disabled after an update.
Approaches that have come to mind :
remove the dependence on Update.number to provide consistency.
use hard-coded channel versions (we could have amicale2 and washer3 at the same time). We would then update the channel ids whenever we want to make a change to placeholder text
The text was updated successfully, but these errors were encountered:
Currently, notification channel ids contain the
Update.number
constant in order to be able to change the placeholder text. Whenever theUpdate.number
constant is changed in a release, the old channels are removed then new channels are added (for example channelamicale7
could becomeamicale8
), allowing the text to be changed.This likely has the consequence of losing the setting. If a user disables certain notifications, they expect them to stay disabled after an update.
Approaches that have come to mind :
Update.number
to provide consistency.amicale2
andwasher3
at the same time). We would then update the channel ids whenever we want to make a change to placeholder textThe text was updated successfully, but these errors were encountered: