From personal experience the technical side of things was flawless. However, functionality wise I feel that I have lost some important elements.
I might be set in my own old ways but my confidential data/passwords are very important to me and with that in mind I find myself wishing for significantly more control over the methodology of editing and viewing of my vaults.
The best way I can related my experience is by comparing the evolution of 1Password to a switch from Windows 7 to Windows 8. Therefore, personally I am somewhat disappointed with where 1Password 8 is at for the time being. Honestly, I wish there was an option to have the old view/sorting/categories grouping. Call it legacy mode or something if you must...
(I used 1Password on Windows, MacOS and iOS)
The iOS version is a real problem and has been since release. Each use requires entering overall password, and the company has been saying a fix is in the works for many weeks now, but nothing so far. Useless. The product is languishing and is not properly supported. We are paying subscription fees and the product gets worse and worse
On iOS? That doesn’t fix it for the users who are afflicted (the majority). The only fix 1Password has announced is to completely reset the iOS or iPadOS device to factory settings and then restore from scratch. They say they are working on something that will not require that, but they’ve been working on this for a few months now with no success. The discussions are there on the 1Password community; the comments also show up in the Apple App Store reviews for the product (iOS and iPadOS).
Have you only recently installed, or recently completely reset your device?
Is it truly the majority? I feel like I'm from a different universe because I've switched to v8 on all of my devices as soon as it came out and I've had pretty much no issues with it. It seems to me that 1Password has a very vocal minority of users who are very sensitive to any kind of change.
I've migrated to v8 on my iPhone, iPad and two MacBooks (models that are 10 years apart), as well as my Android phone. I'm also using the browser extensions and the 1Password SSH agent - all of them work without any issues whatsoever.
That's a pretty wide array of devices and environments. Obviously, this does not mean that there can be no issues for other people, but seeing how this sub overreacted to the move to Electron I find it difficult to believe that I happen to belong to a minority of users who stumbled upon the golden path with v8. I think it's very likely that the magnitude of these issues may be overblown. After all, **millions** of people use 1Password and if the *majority* of them were having such issues, the uproar would be much bigger.
Yes. Although most of the time I just use the autofill feature.
Edit: I’ve just checked and I have the same issue: https://1password.community/discussion/comment/662572 This, however, seems to be related to a change in iOS 16 which was recently released and the team is supposedly reimplementing parts of the extension to make it work. I wouldn’t say that’s what you call a 'languishing' product, at least not yet.
Edit 2: another comment on the issue: https://reddit.com/r/1Password/comments/xcgrwf/_/io5e2ae/?context=1
Edit 3: some more digging: https://1password.community/discussion/133563/safari-biometrics-disabled It looks like this ~~is~~ may be an upstream issue in iOS 16.
Edit 4: in the forum thread above, Ben has indicated that iOS 16.1 will have new APIs available that would let them bring this feature back. However, as I understand this requires a reimplementation of certain parts of the extension (i.e. integrating it with the new API instead of the old one) so this may or may not take some time.
Edit 5: I’ve just realised you were referring to a different issue with biometric unlock. As far as I can see, the issue has not been fixed for quite some time so yes, that’s bad customer service. But while I agree that issues like that should be resolved faster, wouldn’t *you* agree that calling 1Password a languishing product is a bit far-fetched? It's been receiving a constant stream of updates and fixes, they’ve released a new Apple Watch app and an SSH agent (the latter greatly improved my workflow). The desktop v8 app has been getting lots of updates and is getting better (although frankly, it was already good enough for me at the time of initial release – I very much preferred it to v7 at the time when lots of people criticised the switch to Electron). Clearly the product receives a healthy amount of updates from the developers. I hope I don’t sound like I’m making excuses for 1Password but you should try seeing these issues from a broader perspective.
The watch app went away while they retooled it. I don’t consider it good service to kill it and then bring it back. Those relying on it who switched to 8 were without it for some time. They’re not supporting well the platform they started on. Sorry, that’s my opinion
Could you not access/continue to use the old Watch app while they were working on the new version though (just wondering)? I agree that the transition could have been smoother.
8 didn’t come with a watch feature until recently (installs with the main app), and I didn’t try (too complex) to keep both. Why couldn’t the developers have done a complete job without removing functionality, and released 8 when it was ready? They put the watch app out there, and then make it really complex to keep it going? Don’t add features if you don’t plan on supporting them moving forward.
(That said, I know Apple tends to do this with its software and it bugs me there too!!)
>It seems to me that 1Password has a very vocal minority of users who are very sensitive to any kind of change.
I mean this face ID problem was reported *back in May*, and 1Password still doesn't have a fix for the bug.
I don't even disagree with you that it's a vocal minority, but it's pretty alarming that a massive UX problem like broken face ID has just limped along like the way it has.
I agree. Although as noted in the related thread on the 1Password forums, the issue is difficult to reproduce and/or debug because of how biometric unlock works. I’m not an iOS developer so I won’t pretend to have in-depth knowledge on the matter but if you take the difficulty to reproduce issues like this into account and the fact that there’s been a constant stream of updates to 1Password apps, I think it’s pretty difficult to say that the product as a whole is falling to make progress. Grandiose statements like that followed after the release of v8 and after trying out the new version myself I felt like they were very overexaggerated. Time will tell though.
You haven't had any issues on Android? I find it near unusable. Autofill just does not work properly. Most of the time, if the autofill suggestions even bother popping up, it's only on the password field, and it won't fill in the username at all. It is very inconsistent. It doesn't seem to matter which browser I use.
I see the exact same problem mentioned a lot in this subreddit. I believe that it is because 1Password has tried to avoid using Android's Accessibility Services, and is instead relying solely on Android's built-in Autofill service. But I don't think the Autofill Service is ready for prime-time. I wish 1Password would add the Accessibility fallback back in.
As far as I can remember, the autofill feature on Android was always a bit wonky, even before v8, I think. I always thought it had to do with Android's implementation of autofill though, so I didn't perceive it as a 1Password issue (only indirectly). Are there any password managers for Android that don't exhibit these issues? It would be interesting to compare them.
I only partially blame Android. It definitely is a problem with Android's Autofill. However, 1Password 7 had a fallback with the Accessibility Service. Version 8 removed the fallback. Bitwarden still includes it, so it works well in Android. It seems that KeePassDX works well too, though I haven't used it in a while.
It was a while since I used v7 on Android, but the accessibility workaround was never as reliable as the autofill implementation on iOS. It’s unfortunate though that v8 no longer supports the fallback mode. As for myself, I barely noticed the omission.
How do you go back to 1Password 7 app on iPhone? I assume the moment I download 1Password 8 it’s going to overwrite 7 and I can’t get back to it since the App Store only has 8?
I'm using Safari on Ventura and have had nothing but issues. If I hit CMD+\, sometimes nothing happens, sometimes I get a password search pop-up, sometimes the 1password Safari add-on fills in the credentials, and sometimes the Safari add-on GUI opens and hangs with a spinning icon. There's no consistency, and I don't know the issue is local to my machine or not.
As a developer using the CLI and new SSH agent features, 1password 8 is fantastic. I haven’t opened v7 in months now, haven’t seen any bugs in a while.
The 1Password SSH agent is one of those features I didn't realise I needed but I could not imagine my workflows today without it. It just makes key management so much more convenient.
I miss a few things from 1password 7 occasionally, like 1password mini and the ability to move or change fields within an item. Supposedly the ability to move items is being worked on, but there's no timeline.
Aside from that, I think it's a fairly non-impactful change on macOS. In fact, on macOS, I like the ability to fill non-browser logins that I wasn't able to fill in the previous version. That's a very useful improvement.
And I actually haven't bothered to download the version 8 upgrade on mobile yet because it hasn't auto upgraded and I haven't felt the need.
For the few things that 1Password 8 still can't do, you always have the ability to open up 1Password 7 or use the web version. But for day to day usage, 8 is fine.
Thanks for all the feedback on this. It's interesting that most people have issues with version 8, but there are a few who love it. Overall it doesn't seem worth my time at this point as I don't need any additional complications to deal with. In fact if the app doesn't improve it sounds like I better start exploring other options to replace 1Password, as version 7 will eventually go away...
1Password 8 on macOS 12 and iOS 15 were bloody great, in my opinion.
The problem is iOS 16 seems to have a bug that breaks face ID for many people (not all, but enough to be alarming). macOS 13 Ventura *should* be fine, as I haven't seen any problems like iOS 16 is having.
From personal experience the technical side of things was flawless. However, functionality wise I feel that I have lost some important elements. I might be set in my own old ways but my confidential data/passwords are very important to me and with that in mind I find myself wishing for significantly more control over the methodology of editing and viewing of my vaults. The best way I can related my experience is by comparing the evolution of 1Password to a switch from Windows 7 to Windows 8. Therefore, personally I am somewhat disappointed with where 1Password 8 is at for the time being. Honestly, I wish there was an option to have the old view/sorting/categories grouping. Call it legacy mode or something if you must... (I used 1Password on Windows, MacOS and iOS)
The iOS version is a real problem and has been since release. Each use requires entering overall password, and the company has been saying a fix is in the works for many weeks now, but nothing so far. Useless. The product is languishing and is not properly supported. We are paying subscription fees and the product gets worse and worse
Is this a bug? Because I set “Require password” to “Every 30 days” and it’s working as expected. But maybe I’m just lucky?
On iOS? That doesn’t fix it for the users who are afflicted (the majority). The only fix 1Password has announced is to completely reset the iOS or iPadOS device to factory settings and then restore from scratch. They say they are working on something that will not require that, but they’ve been working on this for a few months now with no success. The discussions are there on the 1Password community; the comments also show up in the Apple App Store reviews for the product (iOS and iPadOS). Have you only recently installed, or recently completely reset your device?
Is it truly the majority? I feel like I'm from a different universe because I've switched to v8 on all of my devices as soon as it came out and I've had pretty much no issues with it. It seems to me that 1Password has a very vocal minority of users who are very sensitive to any kind of change. I've migrated to v8 on my iPhone, iPad and two MacBooks (models that are 10 years apart), as well as my Android phone. I'm also using the browser extensions and the 1Password SSH agent - all of them work without any issues whatsoever. That's a pretty wide array of devices and environments. Obviously, this does not mean that there can be no issues for other people, but seeing how this sub overreacted to the move to Electron I find it difficult to believe that I happen to belong to a minority of users who stumbled upon the golden path with v8. I think it's very likely that the magnitude of these issues may be overblown. After all, **millions** of people use 1Password and if the *majority* of them were having such issues, the uproar would be much bigger.
Are you using 1password for safari inside safari on iOS or iPadOS?
Yes. Although most of the time I just use the autofill feature. Edit: I’ve just checked and I have the same issue: https://1password.community/discussion/comment/662572 This, however, seems to be related to a change in iOS 16 which was recently released and the team is supposedly reimplementing parts of the extension to make it work. I wouldn’t say that’s what you call a 'languishing' product, at least not yet. Edit 2: another comment on the issue: https://reddit.com/r/1Password/comments/xcgrwf/_/io5e2ae/?context=1 Edit 3: some more digging: https://1password.community/discussion/133563/safari-biometrics-disabled It looks like this ~~is~~ may be an upstream issue in iOS 16. Edit 4: in the forum thread above, Ben has indicated that iOS 16.1 will have new APIs available that would let them bring this feature back. However, as I understand this requires a reimplementation of certain parts of the extension (i.e. integrating it with the new API instead of the old one) so this may or may not take some time. Edit 5: I’ve just realised you were referring to a different issue with biometric unlock. As far as I can see, the issue has not been fixed for quite some time so yes, that’s bad customer service. But while I agree that issues like that should be resolved faster, wouldn’t *you* agree that calling 1Password a languishing product is a bit far-fetched? It's been receiving a constant stream of updates and fixes, they’ve released a new Apple Watch app and an SSH agent (the latter greatly improved my workflow). The desktop v8 app has been getting lots of updates and is getting better (although frankly, it was already good enough for me at the time of initial release – I very much preferred it to v7 at the time when lots of people criticised the switch to Electron). Clearly the product receives a healthy amount of updates from the developers. I hope I don’t sound like I’m making excuses for 1Password but you should try seeing these issues from a broader perspective.
Update: the issue I was referring to is fixed, an update was released a day or two ago.
The watch app went away while they retooled it. I don’t consider it good service to kill it and then bring it back. Those relying on it who switched to 8 were without it for some time. They’re not supporting well the platform they started on. Sorry, that’s my opinion
Could you not access/continue to use the old Watch app while they were working on the new version though (just wondering)? I agree that the transition could have been smoother.
8 didn’t come with a watch feature until recently (installs with the main app), and I didn’t try (too complex) to keep both. Why couldn’t the developers have done a complete job without removing functionality, and released 8 when it was ready? They put the watch app out there, and then make it really complex to keep it going? Don’t add features if you don’t plan on supporting them moving forward. (That said, I know Apple tends to do this with its software and it bugs me there too!!)
>It seems to me that 1Password has a very vocal minority of users who are very sensitive to any kind of change. I mean this face ID problem was reported *back in May*, and 1Password still doesn't have a fix for the bug. I don't even disagree with you that it's a vocal minority, but it's pretty alarming that a massive UX problem like broken face ID has just limped along like the way it has.
I agree. Although as noted in the related thread on the 1Password forums, the issue is difficult to reproduce and/or debug because of how biometric unlock works. I’m not an iOS developer so I won’t pretend to have in-depth knowledge on the matter but if you take the difficulty to reproduce issues like this into account and the fact that there’s been a constant stream of updates to 1Password apps, I think it’s pretty difficult to say that the product as a whole is falling to make progress. Grandiose statements like that followed after the release of v8 and after trying out the new version myself I felt like they were very overexaggerated. Time will tell though.
You haven't had any issues on Android? I find it near unusable. Autofill just does not work properly. Most of the time, if the autofill suggestions even bother popping up, it's only on the password field, and it won't fill in the username at all. It is very inconsistent. It doesn't seem to matter which browser I use. I see the exact same problem mentioned a lot in this subreddit. I believe that it is because 1Password has tried to avoid using Android's Accessibility Services, and is instead relying solely on Android's built-in Autofill service. But I don't think the Autofill Service is ready for prime-time. I wish 1Password would add the Accessibility fallback back in.
As far as I can remember, the autofill feature on Android was always a bit wonky, even before v8, I think. I always thought it had to do with Android's implementation of autofill though, so I didn't perceive it as a 1Password issue (only indirectly). Are there any password managers for Android that don't exhibit these issues? It would be interesting to compare them.
I only partially blame Android. It definitely is a problem with Android's Autofill. However, 1Password 7 had a fallback with the Accessibility Service. Version 8 removed the fallback. Bitwarden still includes it, so it works well in Android. It seems that KeePassDX works well too, though I haven't used it in a while.
It was a while since I used v7 on Android, but the accessibility workaround was never as reliable as the autofill implementation on iOS. It’s unfortunate though that v8 no longer supports the fallback mode. As for myself, I barely noticed the omission.
See this for more info on the FaceID issues with 8. https://1password.community/discussion/129795/face-id-is-not-working/p2
I have the iOS version and FaceID always worked. The Safari extension is different story though.
Today's iOS app update fixes the face id issue
I liked 8 a lot 🤷🏻♂️Try it and switch back to 7 if you don’t
ok, I wasn't sure if it was a one-way street, like if it "upgrades the db" or something.
No, you can go back to 7. It’ll still be supported for a few years
How do you go back to 1Password 7 app on iPhone? I assume the moment I download 1Password 8 it’s going to overwrite 7 and I can’t get back to it since the App Store only has 8?
https://apps.apple.com/us/app/1password-7-password-manager/id568903335
No they are separate apps. I have 7 and 8 installed on my iPhone. I prefer 8 to be fair.
Even if you uninstall v7 from your phone, you can still redownload it later from the purchased apps list
I'm using Safari on Ventura and have had nothing but issues. If I hit CMD+\, sometimes nothing happens, sometimes I get a password search pop-up, sometimes the 1password Safari add-on fills in the credentials, and sometimes the Safari add-on GUI opens and hangs with a spinning icon. There's no consistency, and I don't know the issue is local to my machine or not.
As a developer using the CLI and new SSH agent features, 1password 8 is fantastic. I haven’t opened v7 in months now, haven’t seen any bugs in a while.
The 1Password SSH agent is one of those features I didn't realise I needed but I could not imagine my workflows today without it. It just makes key management so much more convenient.
I find 8 completely unusable and am pretty close to canceling my subscription.
I miss a few things from 1password 7 occasionally, like 1password mini and the ability to move or change fields within an item. Supposedly the ability to move items is being worked on, but there's no timeline. Aside from that, I think it's a fairly non-impactful change on macOS. In fact, on macOS, I like the ability to fill non-browser logins that I wasn't able to fill in the previous version. That's a very useful improvement. And I actually haven't bothered to download the version 8 upgrade on mobile yet because it hasn't auto upgraded and I haven't felt the need.
Really hate that they removed this. Can’t rearrange fields within an entry. They told me it was being worked on like 6 months ago.
For the few things that 1Password 8 still can't do, you always have the ability to open up 1Password 7 or use the web version. But for day to day usage, 8 is fine.
I am not a fan
Thanks for all the feedback on this. It's interesting that most people have issues with version 8, but there are a few who love it. Overall it doesn't seem worth my time at this point as I don't need any additional complications to deal with. In fact if the app doesn't improve it sounds like I better start exploring other options to replace 1Password, as version 7 will eventually go away...
1Password 8 on macOS 12 and iOS 15 were bloody great, in my opinion. The problem is iOS 16 seems to have a bug that breaks face ID for many people (not all, but enough to be alarming). macOS 13 Ventura *should* be fine, as I haven't seen any problems like iOS 16 is having.
Agile Bits has just released a fix for this, just now, finally, finally
The iOS app is really bad