JeffB

I noticed in the last few weeks that Enpass Android hanging while trying to sync. Using version 6.11.1.1022. If I wait, it will eventually come back, but it can be 15 to 30 seconds. It can by during autofill, or updating entry. It happens some with OneDrive, but particularly bad with Box. Box is so bad, it is unusable as sync target. Workable but a nuisance at times. Phone: OnePlus N10 5G running Android 11. Model BE2028.

The DDG browser has improved and now easily uses Enpass security without needed to switch to the Enpass keyboard.

With the Beta release of the DuckDuckGo browser on MacOS, and now on Windows, it would be fantastic to be able to AutoFill in that environment. The browser will AutoFill with its own password repository, but it appears they may not support extensions (presumably for security reasons) although that is not clear. I have submitted feedback on that for the browser, but also adding a note here to explore how Enpass Password Manager (my one and only), but presumably others, could be used on the Desktop with the DDG browser. The DDG browser is very functional and fast, but still early days. Hopefully there can be some vision for other password solutions. That may be limited by the desktop OS, since it does not have the same AutoFill extensibility as on Android, etc. and I wouldn't expect the OS developers would make a move there. Thanks

I have been using the DuckDuckGo browser on Android since it was available. Support helped me to work through the problems. The best solution is to enable the Enpass keyboard (settings) and then switch to that keyboard when you need to AutoFill. It works very well and with only a slight inconvenience.

A command line version of Enpass would be great. I would like to install on my local headless Raspberry PI and use WiFi Sync for group password management. Thanks

Yes, I agree. There are no suggestions, but if typed and hit enter, the tag will be saved. It would be nice to be a little cleaner. Thanks

Ahh, I see my problem. Unlike the Desktop version, I have to add Tags from the Browse menu. I have to select the TAG and then (+) to open the menu and select the Existing Items option to choose the item to add the TAG. I little clunky, but it is not something I do often on mobile. However, there does seem to be a bug. The count on the TAG is not updated although selecting the TAG shows all of the items. After a refresh, the count is correct.

I have attached a screenshot. The entry has one TAG and I am attempting to add another (that already exists). There is no error, the existing TAG is not displayed and saving the item does not update. The device is a OnePlus Nord 10 5G running Android 11.

Abhishek. I think you are misunderstanding the problem. It is not the size of the backup files that was causing the slowness, it was the size of the SQLCipher database. It appears that there was some sort of internal corruption or duplication that was being reflected in both the sync file and the backups. I am glad there was procedure to restore the integrity of the database. Maybe you would pass this information to the developers for their future reference. Thanks.

After the latest update, I am not able to enter TAGS on my phone. Existing TAGS are displayed, but I cannot enter existing one.

Abhishek, I have been able to update my Android phone and my two windows machines to the latest build. The sync and backup files remained about 10 times usual size. So... I exported the primary vault (where the problem has been) to a JSON file. Then disconnected all of the instances, removed all of the vaults, deleted the app and reinstalled one machine at a time, and rebuild with the JSON export. Then set up each of the machines and vaults again. Now the sync file is 2.9MB instead of 38MB. I will monitor the performance and sizes periodically, but I am confident things will remain stable for a while. And now I have a good procedure to rebuild the if in may be needed again in the future. It is nice that there are ways to resolve the problem with the existing tools and capabilities. Thanks, Jeff

Abhishek, I am not commenting on the number of backup files, I posted the image to show the dramatic size increase of the backup files starting in the middle of April. The size increase was unexpected and by April 28 it was pathological. After a major effort, I am working again, but still the sync and backup files are larger than the historical size by a factor of 10. But at least it is not >100x.

Abhishek, I am attaching a folder listing of my vault backups that shows the progress of the problem with repository size (and presumably the source of the speed problem). The jump from 3.7MB to 4.4MB does not seem significant, but then it jumps to 17MB and then to 39MB and ultimately to 380MB (where the performance issues became significant). My efforts to recover brought the file size back to 39MB but it still seems too large. I am reluctant to try to recover back to the 4MB range as I would lose some significant entries. Do you have any suggestions as to a way to clean up the vaults, or any suggestions about alternative recover mechanisms? Thanks

Abhishek, I am glad to hear the garbled item fix is on the horizon. As to the slowness, I was able to resolve it after noticing the sync database and the backups had grown significantly. Here significantly means the sync database growing from about 38MB with over 500 items to almost 500MB and the backup file growing from 18MB for three different vaults to over 350MB. I was able to shut off sync on the two windows computers, and an Android phone, and then reinstall on one of the Windows machines starting with a backup. Then setting up sync again on the other devices. All seems to be humming along as before now. If I can provide any more information about the root cause of the problem, I will need some direction. However, I am content for now that everything is working well.

It has been over 3 weeks without a resolution. Is there any word on progress or timeframe? I have also noticed a significant slowness in the app on all platforms. Are these related issues and fixed soon? Thanks