The mobile client fails to log in.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39k
- Forks
- 2.1k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Platform
Mobile - Android
Describe the bug
When attempting to log in to the Folo application installed via Google Play with a valid account and password, the app persistently returns an "authentication failed" error message.
Notably, the identical account credentials work without any issues when used to access Folo via the desktop client or the web-based version.
Entry ID
1926504860@qq.com
Relevant Information
No response
Reproduction Video
No response
Environment
No response
Validations
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- This issue is valid
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
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
No files, tests, or entry points are named. Start by reproducing the login failure in the Android app installed from Google Play with the reported valid account, then compare its authentication behavior with the desktop and web clients; done means Android login succeeds without the authentication-failed message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, typescript
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100