Username param causes failure #110

I think since google switched to its new login page I've been getting this error. I assume it's caused by that email input not existing anymore or something. Easy to work around though by just not providing the username parameter once you know what's happening.

gsts --idp-id=... --sp-id=... --aws-role-arn=arn:aws:iam::...:role/SSO-Administrators --username pete@blah.com --aws-region us-east-1 --verbose
ℹ Loaded credentials from "/home/pete/.cache/gsts/credentials".
ℹ Session has expired on 2024-04-12T04:48:40.000Z, refreshing credentials...
⚠ User is not authenticated, spawning headful instance
ℹ Role ARN "arn:aws:iam::...:role/SSO-Administrators" has been assumed via SAML
ℹ Loaded credentials from "/home/pete/.cache/gsts/credentials".
ℹ The credentials have been stored in "/home/pete/.cache/gsts/credentials" under AWS profile "default"
✖ An unknown error has ocurred with message "page.fill: Target page, context or browser has been closed
Call log:

• waiting for locator('input[type=email]')
• locator resolved to
• elementHandle.fill("pete@blah.com")
• waiting for element to be visible, enabled and editable

• element is not visible - waiting...
  

• navigated to "https://accounts.google.com/o/saml2/initsso?idpid=...&spid=...&forceauthn=false&from_login=1&as=...&authuser=0"
• navigated to "https://signin.aws.amazon.com/saml"
• element was detached from the DOM, retrying
  ". Please try again with --verbose