Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
krusnof
4 years agoDedicated Contributor
Defaults to main Collection on restart
With each restart of app, or seems even with enough inactivity to log out, the selected Collection reverts back to the main one. Meaning when using Quick Access it shows all Vaults and not the desired ones by custom Collection. So I have to manually go in again and select the desired Collection to get it to work...
1Password Version: 8.4.0
Extension Version: Not Provided
OS Version: 12
49 Replies
- 1P_Ben
1Password Team
It looks like your post came through without the screenshot. Could you please try again?
Ben
P.S. I too would very much like to be able to specify the icon to be used by each collection. I don't know of any definite plans in that regard but hopefully it is something the design team will think on for the future.
- krusnofDedicated Contributor
Okay, found a bug still... It has the correct collection selected, but UI wise it's not correct. See screenshot. Should be daily and the icon matches—but the checkmark is on All Accounts...! Also, pleeeeeeease let us select custom icon for the collections.
https://us.v-cdn.net/5020219/uploads/editor/ih/pdm90t67jhcz.png - Joshua_ag
1Password Team
Hey krusnof and all,
Our developers have released a fix for the main 1Password app allowing it to re-open the last used collection on unlock. I am running the nightly and can confirm: 80500095 has this fix.
Let us know if this update fixes everything for you or if you are still having trouble.
- krusnofDedicated Contributor
I've been saying the same thing since November of 2021...
- krusnofDedicated Contributor
But it's NOT resolved for me in the QA part—not main app. Been running nightly since the beginning...
- 1P_Ben
1Password Team
I think there were two separate issues here: one related to Quick Access, and a separate one related to the main app. It appears the one related to Quick Access was resolved, but may've still been compounded by the other. In reviewing the issues it appears the one relating to the main app had code merged with the hopes of fixing it today. 🤞🏻 If you're not running the nightly build I'd suggest giving it a try over the next few days, and hopefully once that code makes it into the nightly you'll see all of this sorted out. Please let me know.
Ben
ref: dev/core/core#12068
- krusnofDedicated Contributor
So it's actually not fully fixed—misleading then.