Some items take 15+ seconds to display
Hey team,
Some items (haven't yet figured out a pattern), take a very long time (15+ seconds) to display after they've been selected. I'm not entirely sure why this is, but it only happens on my windows installation (not on Mac or iOS).
Thanks!
1Password Version: 6.0.186d
Extension Version: 4.5.9.2
OS Version: Windows 10 Pro Insider Preview Build 14901
Sync Type: Dropbox
Comments
-
I get this on all items and the app is unusable. Long delays between search, display, edit and save. Running Windows version 6.0.186d on Windows 7.
0 -
Perhaps this is related to the behavior I've reported in the past in which no local vault items can be viewed immediately after launch until about 20 seconds after the vault has been unlocked. I do not see similar behavior with 1Password.com based vaults.
0 -
@zendnez @ofrm_dcb refresh is being delayed by sync with the disk/network, unlike 1Password Account data that has all change notifications in it's heart, folder based vaults needs to talk to Dropbox/OneDrive and then to the disk. All of that is making visible delay when it comes to screen refresh. We are working on fix now, sorry for the trouble.
0 -
Probably then related to my other post about the Dropbox vault seemingly not deleted when told to go. There is not vault for it to sync to. I'll send the log as requested in that thread.
0 -
Dropbox vault finally remove itself. Now working faster.
0 -
Excellent! Thanks for the update. I'm glad to hear it. It sounds like you should be all set, but don't hesitate to reach out if we can be of further assistance. The log is greatly appreciated! :)
0 -
@SergeyTheAgile I think I've mentioned this elsewhere. Now that you've publicly acknowledged that local vaults will be read-only in the initial release, it's clear to me, personally, that using the new Windows release with a local vault doesn't solve a problem that I have.
What I mean here (with respect to local vaults) is that since the new release doesn't support writing of local vaults, it's not better than 1Password 4. It's a big step backwards. It's a big step forwards with respect to cloud vaults.
Nobody would be surprised at this point if you just completely yanked local support out of the first release. If/when you add it back, that's when perf would matter.
So...if you're having internal conversations about what to do with local vaults, here's my 2 cents in case it helps:
Either be insanely great at them or don't support them at all. If your long-term goal is to move folks to cloud vaults, then be brave and convicted about that choice, and don't support local vaults (except possibly import) in the Windows release.
The Windows release fights for oxygen as it is. I would be happy with a cloud-only release which keeps feature pace with the Mac release. I prefer that to a Windows release that is forever in catch up mode.
0 -
Hi @zendnez,
We've been saying this for a few months already, especially in our blog post here that 1Password 6 will be limited to 1Password.com accounts and full support for local vaults (aka 1Password 4 customers) are planned for later this year. Nothing has changed recently and it will remain the same for the next few months.
1Password 6's first stable release is not going to be aimed for replacing 1Password 4 for Windows, it'll be limited to 1Password.com accounts that doesn't have any app to work with. 1Password 4 will continue to co-exist until we have a proper version that can replace it fully.
We can choose to postpone 1Password 6 until next year to have all users covered but we're not going to do that but instead roll it out in stages. We can also choose to ignore local vault completely but then none of our existing customers can migrate to 1Password.com, which isn't acceptable and we've seen more and more users migrating the moment we've added migration and import support.
The work on local vault support is not taking up all of our development resources, in fact, the code is reused between the migration, import and read-only support, it doesn't take much more to maintain this support.
As for the issue described here, it affects 1Password.com vaults as well, not limited to the local vault files. The content of the local vaults are stored in the same local database file that includes your 1Password.com account as well, the issue is in the app itself where it is not refreshing correctly with any type of change, regardless of what vault you're using.
0
