I keep getting the "Welcome to 1Password" "Let's get the browser extension ready" screen on my iPhon
All of the sudden, after using 1Password for years, I am constantly getting the "Welcome to 1Password" screen, where it takes me to the set up of the extension. I have tried removing and re-adding with no resolute. When I go to the next screen, I see that I have done everything but the tour, which if I click "Skip" it goes away and loads a blank page. If I click the Configure (or whatever it says), it also goes to a blank page. Unfortunately, I can do this on demand in order to give you a screenshot. I'll try to get this the next time it pops up.
Otherwise, the checkboxes for the download and the setup above and below this middle section show checked and I do use 1Password on website.
Anyone know a way to resolve this?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
Comments
-
Same here. This has been getting really annoying and frustrating. Kept figuring it would be resolved, but hasn’t happened. My husband is having the same issue.
0 -
Hello @BeachsideCA2CA and @tcaywilson! 👋
I'm sorry that you're running into issues with 1Password for Safari. There's currently a known issue where users who are on the beta version of macOS or iOS might receive unexpected sign-in emails or have 1Password restart by itself showing a welcome page.
We have a mega-thread open and the latest update from the team that can be found here: New sign-in alerts and welcome page appearing with 1Password for Safari (Safari version 18.3 beta) - Page 5 — 1Password Community
If you're not using a beta version of iOS then can you post a screenshot of the message that you see and tell me which version of iOS you're using?
-Dave
0 -
I suppose I took the wrong approach yesterday. I indeed loaded the beta to see if it would resolve an issue. As a developer, I understand that certain changes in any release, including betas, can reset specific settings. I don’t recall seeing this message since I loaded the beta.
However, I was experiencing this issue over the holidays and was on version 18.2 - GA.
As I mentioned earlier, I can’t access this feature on-demand, so I’ll have to wait and see. However, since I’m now on a beta, that possibility seems less likely.
Another thought occurred to me. I was running the beta to version 18.2 at the beginning of December. I don’t remember encountering this issue then. The reason I bring this up is that I wonder if something in the beta code persists and is causing this problem in the GA version.
0