Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to recognize page state
See original GitHub issueUsing the docker launcher and getting the following:
Unable to recognize page state! A screenshot has been dumped to aws-azure-login-unrecognized-state.png. If this problem persists, try running with --mode=gui or --mode=debug
Since running in docker there is no png on my Mac.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:16
Top Results From Across the Web
Unable to recognize page state · Issue #61 · aws-azure-login ...
Using the docker launcher and getting the following: Unable to recognize page state! A screenshot has been dumped to ...
Read more >node.js - aws-azure-login "Unable to recognize page state!"
I have deployed an EC2 instance from a AWS RHEL 8 AMI. I have installed all the pre-requisites for aws-azure-login but cannot connect...
Read more >aws-azure-login - Bountysource
Unable to recognize page state ! A screenshot has been dumped to aws-azure-login-unrecognized-state.png. If this problem persists, try running with ...
Read more >AWS-AZURE-LOGIN NOT WORKING WITH MFA - Microsoft Q&A
I have MFA in my account activated and whenever I try to access my AWS profile I have to do so with the...
Read more >aws-azure-login - npm
If you can't get it from them, you can scrape it from a login page from the myapps.microsoft.com page. Load the myapps.microsoft.com page....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was also facing the same issue. this is related to your “Default sign-in method”. you will face this issue If the default sign-in method is the call.
I have changed the default sign-in method to “Microsoft Authenticator - notification” and it worked well for me.
Found mine was related to the wrong MFA choices setup. Double check users have selected their preferred MFA option.