i haven’t tried to go back. that was probably a year ago that it broke, and the dev response was that they didn’t like samsung’s code and thought it was a bad idea to try to work around it. issue is still open

https://github.com/Kunzisoft/KeePassDX/issues/1269#issuecomment-1075449893

Honestly, not being able to reproduce the problem, I don’t feel like going blind when it’s clearly a problem in the OS. I need an AES symmetric key and if I have to go through certificates and RSA asymmetric keys to workaround this issue, it changes the workflow and requires key invalidations, etc… I really don’t know what to do except ask Samsung to implement a proper Keystore.