Isolate Android account sessions and clear private state on logout
Maintainers usually reply within 1 day
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
- Domain
- authentication, mobile, security
Research direction
Start by reading prerequisites #88 and #79, then inspect the app shell and the selected platform/browser session mechanism. Define the session-storage and invalidation boundaries before implementing; done means all listed acceptance tests pass, including process recreation, expiration, logout during a request, and switching between synthetic accounts.
Written by the indexing model from the issue text.
Description
Roadmap: #76
Goal
Implement the device-side session boundary selected in #88.
Acceptance criteria
- Store session material through the selected platform/browser mechanism and restore only valid sessions.
- Keep credentials out of logs, shared URLs, and application backups.
- Cancel account-bound requests and remove private cached state on logout, expiration, or account change.
- Prevent late responses from a previous session from populating the current account.
- Test process recreation, session expiration, logout during a request, and switching between two synthetic accounts.
Use the app shell from #79. This issue owns session storage and invalidation; sign-in presentation is a separate task.
Prerequisites: #88, #79.
- Dominant language
- Go
- Stars
- 1
- Forks
- 7
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 17
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
- 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.
More from wavefnd/wave-platform
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#139 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 Half a day Newbie friendliness 88/100
wavefnd/wave-platform#137 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
wavefnd/wave-platform#136 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 1/5 Under an hour Newbie friendliness 94/100
wavefnd/wave-platform#135 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
wavefnd/wave-platform#133 ·
Maintainers usually reply within 1 day
All issues in wavefnd/wave-platform
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
open-telemetry/opentelemetry-go-compile-instrumentation#1417 ·
Maintainers usually reply within 2 days
-
agent-research-finding agent-research-recommend chore ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jordansmall/spindrift#4068 · 1 comment ·
Maintainers usually reply within 1 day
-
Type/Task
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenNSW/nsw-srilanka#537 ·
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-2 days Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day