Issue logging in on any web browser when using the iOS 16.4 public beta

Community Member
edited March 2 in iOS

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:/// 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


  • 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 [email protected].

    ⚠️ Don't post your diagnostics report here.

    With your email please include:

    • A link to this thread:
    • 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

  • NCJayG
    Community Member

    @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.

  • Sounds good @NCJayG Thank you for the update!

  • NCJayG
    Community Member

    @GreyM1P or @ag_tommy here's that Support ID for the initial reported situation. [#ZSM-52845-881]

  • @NCJayG

    Thank you for the Support ID, I've located your ticket and one of my colleagues will send you an email as soon as possible. To prevent duplication of effort I'm closing this thread. 🙂


    ref: ZSM-52845-881

This discussion has been closed.