Error generating QR
YatoGaml opened this issue · 4 comments
I'm using last version and i got this error
self.run()
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python310\lib\threading.py", line 953, in run
self._target(*self._args, **self._kwargs)
File "C:\Users\Administrator\Desktop\Discord-QR-Token-Logger-main\Discord-QR-Token-Logger.py", line 113, in main
WebDriverWait(main.driver, 10).until(
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\support\wait.py", line 90, in until
raise TimeoutException(message, screen, stacktrace)
selenium.common.exceptions.TimeoutException: Message:
Stacktrace:
Backtrace:
Ordinal0 [0x011EDF13+2219795]
Ordinal0 [0x01182841+1779777]
Ordinal0 [0x0109423D+803389]
Ordinal0 [0x010C3025+995365]
Ordinal0 [0x010C31EB+995819]
Ordinal0 [0x010F0F52+1183570]
Ordinal0 [0x010DE844+1108036]
Ordinal0 [0x010EF192+1175954]
Ordinal0 [0x010DE616+1107478]
Ordinal0 [0x010B7F89+950153]
Ordinal0 [0x010B8F56+954198]
GetHandleVerifier [0x014E2CB2+3040210]
GetHandleVerifier [0x014D2BB4+2974420]
GetHandleVerifier [0x01286A0A+565546]
GetHandleVerifier [0x01285680+560544]
Ordinal0 [0x01189A5C+1808988]
Ordinal0 [0x0118E3A8+1827752]
Ordinal0 [0x0118E495+1827989]
Ordinal0 [0x011980A4+1867940]
BaseThreadInitThunk [0x77160419+25]
RtlGetAppContainerNamedObjectPath [0x7792662D+237]
RtlGetAppContainerNamedObjectPath [0x779265FD+189]
do you have chrome installed on your computer ? If yes what version of it ?
The following code is raising the timeout exception.
driver.implicitly_wait(5)
driver.get('https://discord.com/login')
WebDriverWait(driver, 10).until( # Exception here!
EC.presence_of_element_located((
By.XPATH, "//input[@type='submit']")))
source = BeautifulSoup(driver.page_source, features='lxml')
Judging from the exception, I presume you are not managing to fully load the Discord login page in Selenium in ten seconds or less. This is likely * due to a poor internet connection and/or speed.
In my next pull request, I will change the wait time to allow a maximum of sixty seconds before raising a timeout error, and I will add a descriptive error message.
Thank you for raising this issue. ❤
*this exception may also be due to the fact that Selenium can not locate submit XPATH. This would be strange, but not impossible. In any case, the issue should be fixed within a few hours if it is not a connection issue via reintroduction of the older logic — whilst your waiting, please try an older version of the program.
Bug ended up being more problematic than I previously thought it was going to be. Revent back to time.sleep(7)
. Lazy and unpythonic, I know, but the issues caused were strange and not worth the hassle.
(this issue can be closed)