⪆ `v0.2.26.223616` acts as if I haven't added my Google account, yet prevents me adding it, as if I have added it.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
What The Problem Is
As issues/1403 explains, I am unable to proceed past the add account screen even after properly authenticating. It acts as if I never added an account to MicroG. When I try again, I observe:
This account already exists on your device.
How To Reproduce
I forgot to finish uploading the screencast:
<!-- [Uploading demonstration.zip…]() -->
Expected Behavior
All software should automatically detect the present account, and consequently not necessitate manual authentication.
Screenshots
My Environment
-
The OS
[ro.build.version.release]: [13] [ro.calyx.*]: [4.4.0] [ro.build.display.id]: [TQ1A.221205.011.22404000] -
The Hardware
[ro.product.brand]: [Fairphone] [ro.build.product]: [FP4]
Additional Context
issues/1403#issuecomment-1346588225 is relevant.
Contributor guide
No contributing guide indexed for this repository
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
Review linked issue 1403 and its referenced comment first, then trace the Android add-account and authentication flow using the reported Fairphone 4 and Android 13 conditions. Done means reproducing the state where authentication succeeds but the account is not recognized while retrying reports that it already exists, then correcting and verifying that state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100