Issue logging in on any web browser when using the iOS 16.4 public beta
Regardless of the browser selected, I am unable to log in via a browser on devices running the recently released iOS 16.4 beta. that includes browsers where it was fine before (Safari and Chrome) and browsers where I attempted making an initial login (Edge Firefox). I suspect the issue lies at the webkit level, but there is no way to confirm. Symptom is eventually you get a screen that says "A problem repeatedly occurred on "https:///my.1password.com/home. I have both a business account and a 1Password families account and it is not account specific, both are failing. Both accounts have MFA set. It will get as far as requesting the MFA token, so I know it's partially succeeding, but fails after that.
When I deleted the device for the Safari browser on my iPhone, it resulted in not getting past the entries for the first screen, though I know it gets them correctly, as when I enter a bad password, I get a failure notification box. When all information is correct, I just get the screen prompt again with all values empty.
1Password Version: 8.10
Extension Version: Not Provided
OS Version: iOS 16.4 public beta
Browser:_ Safari, chrome
Comments
-
Hi there @NCJayG
From what you describe, it sounds like we should get a look at what's going on behind the scenes. I'd like to ask you to create a diagnostics report from your iOS device:
☞ Sending Diagnostics Reports (iOS)
Attach the diagnostics to an email message addressed to
support+forum@1password.com.⚠️ Don't post your diagnostics report here.
With your email please include:
- A link to this thread:
https://1password.community/discussion/138349/issue-logging-in-on-any-web-browser-when-using-the-ios-16-4-public-beta - Your forum username:
NCJayG
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much! :)
— Grey
0 - A link to this thread:
-
@GreyM1P I'll add that number when I have it but will note that the beta 2 release which was released this afternoon may have resolved the problem, as I was able to get logged in. I will need to do a bit more testing before I am comfortable that it is fully resolved. For now, it looks like both Chrome and Safari are working correctly.
0
