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

Open Android notification destinations without crossing account boundaries

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, go
Domain
authentication, mobile, security

Research direction

Start with verified link routing in #86, session isolation in #95, and notification.Item.URL, then trace how notification taps enter cold and warm starts. Use synthetic notifications to cover signed-out, wrong-account, expired-content, malformed, untrusted, and repeated-tap cases. Done means supported destinations preserve the intended screen safely and enforce the matching active account.

Written by the indexing model from the issue text.

Description

android difficulty: intermediate enhancement help wanted notifications

Roadmap: #76

Goal

Route notification taps through the existing app-link and account navigation.

Acceptance criteria

  • Map supported notification destinations to the correct screen on cold and warm starts.
  • Require the matching active account before opening account-bound content.
  • Retain the intended destination across sign-in and reject malformed or untrusted destinations.
  • Deduplicate repeated delivery/taps using the contract's notification identity.
  • Test signed-out, wrong-account, expired-content, and repeated-tap cases with synthetic notifications.

Start: Verified link routing from #86, session isolation from #95, and notification.Item.URL.

Prerequisites: #86, #95, #106, #107.

Dominant language
Go
Stars
1
Forks
7
Avg merge
4h 19m
Merged PRs (30d)
34

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.