2FA handling failed: TimeoutError: page.waitForSelector: Timeout 2000ms exceeded
[5/14/2025, 10:56:28 PM] [PID: 485885] [LOG] DESKTOP [LOGIN] Password entered successfully [5/14/2025, 10:56:41 PM] [PID: 485885] [LOG] DESKTOP [LOGIN] Successfully logged into the rewards portal [5/14/2025, 10:56:41 PM] [PID: 485885] [LOG] DESKTOP [LOGIN] Logged into Microsoft successfully [5/14/2025, 10:56:41 PM] [PID: 485885] [LOG] DESKTOP [LOGIN-BING] Verifying Bing login [5/14/2025, 10:56:52 PM] [PID: 485885] [LOG] DESKTOP [LOGIN-BING] Bing login verification passed! [5/14/2025, 10:56:52 PM] [PID: 485885] [LOG] DESKTOP [LOGIN] Logged in successfully, saved login session! [5/14/2025, 10:57:08 PM] [PID: 485885] [LOG] DESKTOP [GO-HOME] Visited homepage successfully [5/14/2025, 10:57:12 PM] [PID: 485885] [LOG] DESKTOP [MAIN-POINTS] Current point count: 11527 [5/14/2025, 10:57:16 PM] [PID: 485885] [LOG] DESKTOP [MAIN-POINTS] You can earn 0 points today [5/14/2025, 10:57:16 PM] [PID: 485885] [LOG] DESKTOP [MAIN] No points to earn and "runOnZeroPoints" is set to "false", stopping! [5/14/2025, 10:57:18 PM] [PID: 485885] [LOG] DESKTOP [CLOSE-BROWSER] Browser closed cleanly! [5/14/2025, 10:57:19 PM] [PID: 485885] [LOG] MOBILE [BROWSER] Created browser with User-Agent: "Mozilla/5.0 (Android 12; Linux; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36 EdgA/136.0.3240.50" [5/14/2025, 10:57:19 PM] [PID: 485885] [LOG] MOBILE [MAIN] Starting browser [5/14/2025, 10:57:46 PM] [PID: 485885] [LOG] MOBILE [LOGIN] Email entered successfully [5/14/2025, 10:57:55 PM] [PID: 485885] [WARN] MOBILE [LOGIN] Password field not found, possibly 2FA required [5/14/2025, 10:58:31 PM] [PID: 485885] [LOG] MOBILE [LOGIN] 2FA handling failed: TimeoutError: page.waitForSelector: Timeout 2000ms exceeded. Call log:
- waiting for locator('#displaySign') to be visible
I'm experiencing the same issue.
My workaround is to randomly pick a number in the Microsoft Authenticator app and keep retrying.
If the 2FA check stops and I stop receiving notifications, I just restart the container.
In my case, the 2FA prompt never appears in the logs.
I’ve previously made sure that “Send sign-in notification” is enabled on all my Microsoft accounts.
Since I'm using the SaveFingerprint feature, I don't have to go through this every time I log in.
My present situation finds the system persistently requesting verification through a security code dispatched to my associated email address rather than initiating the customary two-factor authentication (2FA) via application.Just in mobile login.I have already disabled the email alert notification feature. no lucky.
Here are some possible solutions :
-
Check your security settings to ensure the authentication app is set as the primary verification method. (not sure u can)
-
Disable email as a recovery option to prevent it from overriding the app authentication. (not sure u can too lol)
-
Reset your two-factor authentication (2FA) by removing and reconfiguring the authentication app with a new QR code.
After logging in on my mobile device, I exported the cookies and placed them in the corresponding session path, but it still doesn't seem to function.
Here are some possible solutions :
- Check your security settings to ensure the authentication app is set as the primary verification method. (not sure u can)
- Disable email as a recovery option to prevent it from overriding the app authentication. (not sure u can too lol)
- Reset your two-factor authentication (2FA) by removing and reconfiguring the authentication app with a new QR code.
I have configured app authentication and disabled email alerts for notifications. Strangely, I suddenly bypassed verification upon login, which is quite perplexing. Should I disable app authentication?
Should I disable app authentication?
If it works & login well, don't touch anything.
Try running it in "headless mode false" and see if you can spot the problem
https://github.com/TheNetsky/Microsoft-Rewards-Script/issues/296#issuecomment-2905017306
Updated solution: https://github.com/TheNetsky/Microsoft-Rewards-Script/issues/296#issuecomment-3305080702