May 5, 20223 yr Having encountered the crash with this version, I took the usual step of clearing data and attempting to set up the app from scratch. While the fresh install does not crash, it does not allow syncing more than vault via folder (I have not tried other sync styles). I have multiple vaults, one for personal, one for work, etc. Each vault has a separate folder sync location on Android. This has worked with previous builds. In this build I can create a new vault "Personal" with the same vault password that I use for the synced vault on other platforms. I do not store the vault password in the primary vault (this was not required previously). If I configure this vault to sync, it works fine and the empty vault is populated with sync information from the folder as expected. Multiple syncs can occur without issue. Then I add a second vault ("Work") with its own (different) password and set it to sync with a different folder. This also works, populates the new vault with the appropriate information, etc. However, as soon as I add the Work vault sync, the Personal vault sync begins to fail and reports the wrong password. Entering the correct password for that vault does not allow it to sync (reports incorrect password). If I disable sync for Personal, and then reenable it with the correct password, it begins to sync again, but immediately breaks the Work sync in the same way. This pattern repearts for vault 3, 4, etc. At any time only the most recently configured vault for syncing works, all the others reports they have the wrong password, even though they were able to sync before. Its almost like Enpass has forgotten that each synced vault can have its own password.
May 5, 20223 yr Hi @Axxel H Apologies for the hassles caused to you in this matter. Kindly share the below details with me and I'll get this investigated for you - The version of the OS you are using on which you are facing this concern. Are you also encountering any error message with this issue? If yes, kindly share a screenshot of it with me.
May 5, 20223 yr Hi @Axxel H We were able to reproduce the bug on our end, due to which this issue is occurring, and our dedicated team is now working on fixing it. Soon, a patch addressing this issue will be released. Your patience in the meantime is appreciated. SI-2786
May 5, 20223 yr Author It sounds like you have a repro case and don't need screenshots, but to answer the other question this is Android 12 (Pixel 5a). Looking forward to a fix.
Create an account or sign in to comment