The implication is that the entry "last modified" time stamp is not being updated correctly, so the entry from database B replaces the one in database A.
1. Check the "last modified" time stamp of the entry before and after you set up OTP.
2. Save and sync.
3. Modify the entry by manually adding a field.
4. Save and sync.
Is the change still there?
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the real cause of this issue is not that easy to reproduce as my scenerio,
it happened rarely, but hit me multiple times in this scenerio,
in my daily usage
I mostly modified local db A as it resident on my laptop that much easier to do most of thing,
and read db B on android phone by keepass2android,
I just post the found here,
and hope I will find the way to reproduce this issue so it can be correct fixed.
and there is also other catch with synchronize,
it won't alert about db with different master key, which will make unpredictable result.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know there has been specific said that field data will not implement,
but I don't know there is a risk lost it due to synchronize,
here is my scenerio,
software
keePass 2.30, with plugin KeeOTP, Tray Totp
kind of surprise ...
The implication is that the entry "last modified" time stamp is not being updated correctly, so the entry from database B replaces the one in database A.
1. Check the "last modified" time stamp of the entry before and after you set up OTP.
2. Save and sync.
3. Modify the entry by manually adding a field.
4. Save and sync.
Is the change still there?
cheers, Paul
the real cause of this issue is not that easy to reproduce as my scenerio,
it happened rarely, but hit me multiple times in this scenerio,
in my daily usage
I mostly modified local db A as it resident on my laptop that much easier to do most of thing,
and read db B on android phone by keepass2android,
I just post the found here,
and hope I will find the way to reproduce this issue so it can be correct fixed.
and there is also other catch with synchronize,
it won't alert about db with different master key, which will make unpredictable result.
You need to compare the last modified time of the entry that is a problem, that's what KeePass uses to perform a sync.
Sync replaces the entire entry, not individual fields.
If you have a different master key sync will fail, nothing unpredictable there.
cheers, Paul
Last edit: Paul 2015-11-18
thanks for the clearify on what happended under there