PhilippC / PhilippC/keepass2android
pdf-file not downloadable[BUG]
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Checks
- I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
I have been using your app for a very long time and have not noticed any weaknesses so far. It's actually a very good app.
On vacation, however, I wanted to look at an important pdf file that is stored in the database.
Unfortunately, this was not possible.
All 3 options offered to me in the app do not work.
I receive a file as a download with the Android browser that cannot be read by Word, for example, although I can read all the other pdf files that I have saved elsewhere.
Then I tried to save the file to Dropbox.
Problem: I didn't want to log in with Google, but with my own access data. But this is not possible, because at that moment I can no longer access the database with your app. Writing down the password beforehand is not a solution for me, as I often use 60-digit passwords.
The only solution would be for me to be able to open a second instance of your app.
Describe what you expected to happen:
- Easy download of pdf files stored in Keepass.
- Possibility of using a second instance of your program
What version of Keepass2Android are you using?
1.10-pre
Which version of Android are you on?
Androidversion 14
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
Start by reproducing the three PDF handling options on Android 14 with Keepass2Android 1.10-pre, checking whether the downloaded file can be opened. Also assess the separate request for a second app instance and determine whether these should be split into distinct issues. Done requires clearly verified behavior for each requested outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100