akash-network / akash-network/console
Incognito OAuth signup/login state inconsistency + duplicate trial setup
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 264
- Forks
- 94
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 297
Description
1st time incognito mode
I mistakenly I clicked google ouauth in sign up tab, instead of login tab it took me free trail setup again but it showed all as verified state - create account , verify email, payment setup, when i clicked , its showed me welcome again and deducted 1 dollar
2nd time incognito mode
I again tested with the same flow in incognito mode in new tab again
now done google outh in sign up tab, its took me to console.akash.network this time its correctly landed me correctly but its saying
You need to create a certificate to view deployment details.
instead it just have to show as normal like before
I am attaching the screenshot below
Contributor guide
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
Reproduce both reported Google OAuth flows in separate incognito tabs, including the signup-tab path and the resulting trial setup, verification state, payment step, and console destination. Compare the observed screens with the expected normal login or signup behavior; done means the flow is consistent, does not repeat trial setup or charge unexpectedly, and shows the correct deployment details state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100