Is v8 a mistake edition?

Thanks ag_mike_d that is appreciated.

Note that re: PIN in iOS there also needs to be an equivalent in MacOS as even 1Password 7 only supported biometric (fingerprint) or Apple Watch - which again is incredibly infuriating if you don't have biometrics enabled and don't use an Apple Watch. A variable 6-8 digit/character PIN is as secure, if not more so, than those options and provides an option for ANY user regardless of what functionality they may or may not have enabled on the device. :-)

Re: Windows and your comment:

Regarding this comment, 1Password 8 uses Windows Hello for the PIN unlock. When you say this only works about half the time, it sounds like perhaps this maybe after a reboot or when the 1Password app is completely terminated. This is expected behaviour as 1Password requires your account password after a reboot. However, if you have a hardware backed Trusted Platform Module (TPM 2.0) in your windows device, you can set the following option through 1Password 8 for Windows so that Windows Hello can persist through system restarts: Use Windows Hello to unlock 1Password on your Windows PC - Manage your settings. Please let us know if this helps!

No, this isn't the scenario - not worried about persistency after a restart - happy to re-enter master password in this scenario. The situation I'm experiencing is when the PC has been running for a while with 1Password open but minimised. So...

Windows 10 PC is set up to lock the screen/screensaver after 30 minutes, and 1Password set to lock after 10 minutes. You start the PC, log in with your Windows user PIN (Windows Hello), you open your browser (with 1Password extension) and you main 1Password app, and for the 1Password app enter your master password, then minimise the app out of the way.
You do a little work immediately and use a password or two out of 1Password via the browser extension (while main 1Password app is unlocked from original master password sign in), then take a break and go away.
An hour later you return to resume using your browser and restore 1Password app - it will after a delay of a few seconds bring up the Windows Hello PIN input for 1Password and allow you to enter your PIN and unlock it - you carry on working as usual for a bit. You go away again...
and return a couple of hours later and 1 of 2 things happen - either (a) the PIN comes up again as described in previous sentence, or (b) it doesn't and you have to re-enter Master Password. You work for a bit and go away again (e.g. PC may have been on and running for perhaps 4-8 hours by this stage).
When you return one of 3 things will typically happen: (c) if (a) happened above and the PIN worked then this time it almost certainly fails like (b) above and you have to re-enter the master password, or if (b) above happened and you re-entered the master password then (d) occasionally the PIN might appear, or (e) more typically the balance of the time (75%+) you need to re-enter the master password yet again, and so on.
And so it repeats infinitum if the PC is on for a reasonable period of time (i.e. several hours or more) and you go away and come back to use it at periodic intervals.

I have been unable to identify an obvious pattern or any other 'events' on the PC that could be contributing other than it starts happening after it's been on and running for say at least 3 or more hours and the Windows screen lock, etc, has triggered a couple of times (where you need to enter your Windows PIN to unlock the PC), and both Windows and 1Password have time delays set to auto-lock after a certain amount of inactivity. So not helpful for diagnosing I'm afraid, but that is the behaviour I've been regularly observing under v8 on my PC (and v7 might have done the same prior to that if it was supporting the Windows Hello PIN unlock, I can't recall for certain).

I suspect it may also be more likely a Windows idiosyncrasy than possibly a 1Password bug, given when the PIN does come up successfully sometimes there can be a long lag and other times its instantaneous - suggesting even when the PC is idle and using minimal processor & memory something takes a bit to 'kick into life' in Windows to activate the PIN GUI input...

Cheers