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
Describe the bug
When restoring from Seedvault/a device backup, some apps may end up with a broken state of Cloud Messaging, thinking they're currently registered, but the app is never listed as registered on Cloud Messaging until app data is cleared.
Note: Seedvault now emulates device-to-device transfers.
microG seems to exclude FCM registrations from backup and accounts as well as far as I can tell, this seems like it'd be somewhat intended considering most apps do end up clearing this registration data / get registered again after restoring.
The text was updated successfully, but these errors were encountered:
Describe the bug
When restoring from Seedvault/a device backup, some apps may end up with a broken state of Cloud Messaging, thinking they're currently registered, but the app is never listed as registered on Cloud Messaging until app data is cleared.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
App gets re-prompted for registration or the registration is still considered valid
Screenshots
If applicable, add screenshots to help explain your problem.
System
Android Version: 14
Custom ROM: CalyxOS 5.14.2
Additional context
Seedvault bug: seedvault-app/seedvault#840
Note: Seedvault now emulates device-to-device transfers.
microG seems to exclude FCM registrations from backup and accounts as well as far as I can tell, this seems like it'd be somewhat intended considering most apps do end up clearing this registration data / get registered again after restoring.
The text was updated successfully, but these errors were encountered: