The 1Password Apple Watch app no longer has its own PIN code. {OPI-3813}

The Apple Watch app now requires an Apple Watch PIN code to be set. {OPI-3760}

If you set a passcode (Apple Watch app > Passcode) on your Apple Watch, that should do the trick. 1Password for iOS just isn't going to send any data to your Apple Watch if it isn't protected. Optionally, you can enable "Unlock with iPhone" (also in Apple Watch app > Passcode), which I find I use the vast majority of the time as opposed to unlocking my Watch manually. Secure and convenient. Let me know if that helps.

Actually, that was one of the first things I tried, and it didn't help. But just a while ago, in the iPhone app, I chose an item, noticed the Apple Watch tag, and deleted it. Immediately after doing that, I noticed that all of my data was appearing on the watch app. The watch passcode was in place at the time, so I'm not sure why it suddenly worked, but it seems to work now.

None of the above tricks helped. My watch has always had a passcode set. Using the unlock with iphone did not help. The app is frozen on my watch with the useless reminder to have a device PIN. 1Password is bricked on my watch (model 2)

@tim_trim: That is correct: 1Password is a security app, and if we cannot secure your data beforehand (which is the function the passcode serves), we're not going to send it there. There are plenty of other apps for that: notes, reminders, etc. I'm sorry that's probably not the answer you were hoping for.

@vickurc: Thanks for letting me know. At this point, the best thing to do will be to restart your devices, reproduce the same issue, and then generate a diagnostic report so we can look at the logs to determine exactly what is happening:

Please send it to [email protected] with a link to this discussion and your username in the email so we can 'connect the dots'. Post the Support ID you receive here and we'll take a look at it as soon as possible. Once we see the report we should be able to better assist you. Thanks in advance!

Second it is my data. It can't get to the watch unless I have validated in the app on the phone. It would be good to have the option to use without having to set codes. I choose what goes on there but you have made the decision that I can't do that. I don't want codes on my watch

@tim_trim: I get it, but presumably you're using 1Password because you want to secure your data. This isn't possible without the device passcode, as that's used to encrypt data in the Keychain for transmission and storage on the watch. Again, we're not willing to offer a security app that offers no real security. If you want to store data insecurely on your Apple Watch, you can use another app to do so.

And apart from 1Password, not having a passcode on your watch at all is disastrous if it is lost or stolen. So, fundamentally, this is also about protecting your investment. Have you tried the "Unlock with iPhone" feature I suggested? Most days I don't even enter my passcode once; I just use Touch ID on my iPhone and the watch is unlocked unless I remove it. Just a thought.

Dear Brenty
I was so satisfied before the update. Changed from mSecure to 1Password ( G-D Thanks), originally, because of the beautiful GUI, on the Apple Watch. Used it daily on my watch.
I'm sure you're update is amazing.
But this diagnosis stuff is over my head.
Isn't it possible to give us an option to downgrade to the previous version, till you have a Chance (Probably after Christmas) , to find the problem with the Apple watch modul 2 (Nike version, maybe that's the problem) and your upgraded version of 1Problem.
Thank you for all your help till now.
Ira Rosenzweig

@333ira: lol fair enough. Hopefully that's the only problem you have today! Unfortunately it isn't possible to get previous versions of apps out of the App Store, but we're on the case. I can't say for certain at this stage, but I suspect we'll be able to find a workaround and not have to push an update for this. We had a long beta period and didn't run into anything like this, and one of the things we were most focused on was making sure that it "just works out of the box" after updating. Based on the relatively few reports of issues we've had here, it's likely a specific configuration we weren't able to test for. We'll do our best to get this resolved for you and everyone else as soon as possible either way. Thanks for your patience and understanding.