PhilippC / PhilippC/keepass2android

[BUG] synchronisation of databases

Open
#2,955 0 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:

Hi, just changed the master password for the database on my laptop. Then I changed the password on the database on my phone. I can confirm I've been able to log on to both databases on both devices with the same password (both databases are the same). However, I tried to synchronise the databases on my laptop with my phone, and it says the phone's file is corrupt, even though I can log in to it on my phone. I tried logging on to my phone's file using the keepass app on my laptop and it also says it's corrupt. I'm using keepass 2.59 on my laptop and 1.12-r7 on my phone. I just updated the app on my laptop so I'm not sure if it's because of that or changing the password on two different platforms.

Describe what you expected to happen:

I expected the two databases to synchronise seamlessly like usual.

What version of Keepass2Android are you using?

1.12-r7

Which version of Android are you on?

Huawei YAL-L21 | EMUI version: 12.0.0 | couldn't see android version

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 synchronization between KeePass 2.59 on the laptop and KeePass2Android 1.12-r7 on the phone after changing the database password on both devices. Compare the reported corruption with whether each database opens independently; done means the matching databases synchronize successfully without a corruption error.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp
Domain
databases, mobile-dev
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.