How to correctly dispose of a Device Registration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
So I accidentally went thru the process of uninstalling microG assuming apps would re-register with a new Device Registration, I was able to recover by restoring an old backup I had of microG's data.
When upgrading devices how should users correctly disable/dispose of their old Device Registrations without having been signed into a Google Account.
I assume if I were to move phones, wipe the old one, Google would still be delivering Push Notifications to apps on a non-existent device.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Start by tracing microG's Device Registration and push-notification handling, then determine whether registrations can be disabled without a Google Account and what happens after a device is wiped. Done means documenting a verified procedure for disposing of an old registration and clarifying whether notifications can still be delivered to it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, java
- Domain
- mobile
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100