PhilippC / PhilippC/keepass2android

[QUESTION] Es ist ein Fehler aufgetreten

Open
#2,714 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
C#
Stars
6.2k
Forks
478
Avg merge
1h 4m
Merged PRs (30d)
2

Description

Hello,

I have been using Keepass/Keepass2Android 1.11-r0 with synchronization via WEBDAV/WIN11 and Android on many devices for several years.

Since KeepassXC now supports passkeys, I have now installed this on the desktops.

During this process, I changed the backup file to the new *.keyx format. This now works on all devices, except for my Samsung A52s 5G with Android 14 with update from October 1st, 2024.

Here I only get "An error has occurred".

I have already tried the following:

  • Completely reinstalled Keepass2Andoid
  • Restarted the device several times
  • Deleted the app cache
  • Removed caching in the settings
  • Saved the DB locally and called it up - that works. But I cannot synchronize with WEBDAV here

Additional information:

  • My weather app also had script errors with the advertisements - maybe there is a connection?
  • See my debug log attached. Does anyone have a suggestion?

Regards

Gert

keepass-log.txt

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 with the attached keepass-log.txt and compare the working local database path with WebDAV synchronization on the Samsung A52s 5G running Android 14. Done means identifying a reproducible cause for the .keyx synchronization error and documenting a verified fix or the missing diagnostic details.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp
Domain
mobile, networking, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.