Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When restoring from Seedvault, some apps may end up with broken FCM registrations #2734

Open
lucasmz-dev opened this issue Jan 6, 2025 · 0 comments
Labels

Comments

@lucasmz-dev
Copy link
Contributor

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:

  1. Example app: https://play.google.com/store/apps/details?id=com.compatec.app
  2. Create a Seedvault backup
  3. Restore backup on another device
  4. Open app
  5. No prompt (if you have confirm new apps enabled) or auto-register, app does not show on registered apps on the Cloud Messaing menu

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.

@lucasmz-dev lucasmz-dev added the bug label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant