PhilippC / PhilippC/keepass2android
[BUG] sftp: SEND PUBLIC KEY... fails to open share screen
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:
Lenovo Idea Tab (TB336FU), Android 15, ZUI 17
sftp: SEND PUBLIC KEY...
Fails to open the "Share" screen. Thus I cannot copy the public key to put in "authorized keys".
It's a newish model of Android tablet, released October 2025, but not obscure (it's sold at John Lewis in the UK).
Describe what you expected to happen:
No response
What version of Keepass2Android are you using?
v1.14-r4 from the Play Store
Which version of Android are you on?
15
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 “SEND PUBLIC KEY...” action on a Lenovo Idea Tab running Android 15 with Keepass2Android v1.14-r4, then trace the code path that should open Android’s Share screen. Compare the behavior with a device where sharing works; done means the public key can be sent or copied through the Share screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100