PhilippC / PhilippC/keepass2android

[BUG] Attachment size 0 Byte/lost when writing shared database via webdav

Open
#2,855 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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:

first of all happy eastern. :-) I am using Keepass 2.58 with a database stored on a Synology NAS. Access via Webdav using a vpn connection. Keyfile stored locally on each device. This combination is used for many years using Chromebook (Keepass2Android), Android (Keepass2Android), Iphone (Keepassium) an Windows PC (Keepass).
On februrary 8th 2025 (last Backup version with correct attachments), I started using Keepass2Android on a Fairphone 5 device, after that all key attachments are reset to size 0 bytes. Even if I replace the 0 bytes attachent on an other device and resync, I cannot open/display the content on the android device (content empty).

Describe what you expected to happen:

No response

What version of Keepass2Android are you using?

1.11-r0

Which version of Android are you on?

14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in Keepass2Android 1.11-r0 on Android 14 with a KeePass database stored through WebDAV, focusing on attachment synchronization. Compare attachment sizes and readability before and after syncing with another client. Done means attachments retain their contents and can be opened on the Android device after replacement and resynchronization.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.