Thanks for working on this problem @laurent. But in my opinion this scenario should never happen. Its not a good solution to simply hide the problem. I come back to this Forum, becuase i trapped one more time into this even knowing the issue can happen. but i even dont understand why this happend again. it take me hours of fixing going through the here described solution with exporting/importing and so on, and now on the third device it happend again and again all devices are contaminated since sync before understanding something is going wrong. yeah "so much hate!" - i hate this! i hate this a lot!! i am developer and has my own projects where also nobody help me out to fix my bugs - but i donated to keep joplin up - i would even pay a price if you would fix this issue in a way that more than one master key can never happen.
why dont give the user a OPTION: single key OR multi key. If single key - all devices share one and the same key - i do not need more than one key
OR
stop the user before he is doing somethig stupid by a popup: "Do you really want to push/add a second key - yes/no"
sorry for so much hate again - but this one makes me really angry again
Could you provide a screenshot of your encryption config screen? I think it's incorrectly detecting a key that needs upgrade even though it doesn't, but it would be easier to tell with the screenshot.
There's no hidding the problem. We just don't allow encryption key deletion because it's only a few bytes, and could potentially be used to decrypt data. Disabling the key moves it out the view but without deleting it.