-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login Error: waiting for locator("select#landingPageOptions") #63
Comments
I saw the same time out error around last week. My schwab-api code is old around 2/June/2024, my python version is also older. It's good to know that 3.12 also has this issue. I just try re-login later and it will work sometimes, but definitely annoying (This just happened today), I haven't figure out any root cause yet. It feels like schwab site issue? Or will this be un-stable network connection, does anyone on wired network having this problem or not? It should not be pc performance issue? I have 16GB ram and AMD Ryzen 7 7840HS. I previously saw this timeout on a 4GB ram Linux machine sometimes, so I thought it's RAM limited at that time. In the closed attempt (#41), I simply try increase the timeout but there will be another time out jump out elsewhere. Sorry, I didn't spend enough time to look into this issue on Jan/2024. it's not pain enough for me. Appreciate any feedback or possible solution as well File "C:\git/schwab-api_2June2024\schwab_api\authentication.py", line 82, in _async_login |
This also has been happening to me the last few days. 90% fails. Same error: "waiting for locator("select#landingPageOptions")" I looked here to see if anyone else had the same problem. Schwab must have made a change. |
I did a little debugging myself and here's what I found: The script uses this to login on the home page (schwab.com) Here's some things I noticed while troubleshooting:
Hopefully this is helpful and a fix is found soon :) |
I found a fix that worked for me and created a PR. Would love to know if this also works for you @cnMuggle @davidacrook |
Thanks Nelson! I get farther now, but then get a 30 second timeout error on this line: |
Testing Nelson's change on Windows and WSL, 5 tries each: Windows (Python 3.12) - 0 successes, 5 failures. Linux (Python 3.10) - 2 successes, 3 failures. The successes take 17 seconds and it used to take 10 seconds, so something changed on Schwab's side. @NelsonDane, what is your operating environment that this works successfully in? |
@davidacrook Thanks for the reply and for testing. I've tested on: (both headless and not)
However, when I tested it this morning on a Windows 11 VM (Python 3.12.2) I found that it failed to the same timeout error as previously. The iframe also didn't load and "strobed" like in the image I sent above (when ran non-headless). Also this morning, I found that commenting the |
Doing more digging, the Perhaps this module is doing more harm than good? It's at least something to look into more. |
Don't have a ton of bandwidth to test myself, but can we try freezing to playwright 1.4.4 (before the breaking changes) or even 1.27.1 and see if that resolves the issue for now? |
Checking today, it seems that the iframe is no longer blocked, and it's working without any changes needed for me now. Strange, perhaps Schwab updated/fixed something on their side |
I am able to login with @NelsonDane's change in a Linux machine. Just commenting out "await stealth_async(self.page, config)" doesn't work for me. It's strange that my Windows machine can login sometimes without the change (cannot login last Friday, but works Monday today, while the same code cannot work on a Linux machine until I applied the NelsonDane's change). I do see under Linux that without commenting "await stealth_async(self.page, config)", the login box is greyed out. Windows machine (not WSL) playwright version is 1.40.0 with python 3.9.13, Linux machine has playwright 1.45.0 with python 3.12 |
The past few days this issue has been popping up for me:
This occurs whether saving the session cache or not.
The text was updated successfully, but these errors were encountered: