Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Register and revoke Android push devices for the active account

Open
  • Is something wrong?
#108 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, go
Domain
api, authentication, mobile, security

Research direction

Start with the session integration in #94/#95 and notification contract in #107, then trace the active-account device registration flow across the app and service. Done means authenticated registration, update, rotation, revoke, logout detachment, account-ownership checks, token protection, bounded storage, and tests for the listed unauthorized, duplicate, rotation, logout, and account-change cases.

Written by the indexing model from the issue text.

Description

android difficulty: advanced enhancement help wanted notifications security

Roadmap: #76

Goal

Implement device-registration lifecycle using the contract from #107.

Acceptance criteria

  • Add authenticated registration/update/revoke operations with account ownership checks.
  • Register the active device from the app and handle provider-token rotation.
  • Detach the registration on logout and prevent stale callbacks from rebinding it to the wrong account.
  • Avoid exposing device tokens through list responses or logs; bound stored registrations according to the agreed policy.
  • Test unauthorized mutation, duplicate registration, rotation, logout, and account change.

Start: The session integration from #94/#95 and notification contract from #107.

Prerequisites: #94, #95, #107.

Dominant language
Go
Stars
1
Forks
7
Avg merge
1h 45m
Merged PRs (30d)
16

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wavefnd/wave-platform

All issues in wavefnd/wave-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.