PhilippC / PhilippC/keepass2android
[QUESTION] it needs dropbox app installed?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
What version of Keepass2Android are you using?
Please follow these steps to find your app version:
- Click the ⁝ icon in the top right corner
- Select Settings
- Click About
- Find the "Version" information and provide it here:
version =v1.13-r1 , i tried with "signed-ar64" and "signed" apks
when i first try to open a dropbox hosted file, it opens a webpage (firefox) for authorization, then i tap blue "authorize" button, then opens a page with some text, then returns KP2A app saying "authorization failed" yellow bottom banner .. i tried with dropbox full access and just kp2a folder
i dont have dropbox app installed, and i think i wont either for security and because i dont see the need to install a whole app just to access ONE SINGLE FILE
i tried with google drive before but kp2a forced me to have google drive app installed (#2637), i remove it because of privacy and to debloat my phone ... i suppose with dropbox it works different and it doesnt force me to have the app installed ... anyway surely these platforms have http apis anyway
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
Reproduce the Dropbox authorization flow in Keepass2Android v1.13-r1 with both the signed and signed-ar64 APKs, using Firefox and no Dropbox app installed. Check what happens when the browser returns after authorization, including both Dropbox full-access and KP2A-folder scopes; done means the hosted file can be opened without the authorization-failed banner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100