-
Notifications
You must be signed in to change notification settings - Fork 58
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
Valid MAC cannot be determined #124
Comments
This is really weird -- pythons |
I have downloaded the executable, and I am running it on Windows 10 Home, version 1703, OS Build 15063.726, |
Also getting this in 0.4.0: Traceback (most recent call last): Windows 10 Home 1709 OS build 16299.125. |
I have the same problem, I'm running 0.4.1 on Windows 10 |
Really weird, this was working for me yesterday no problems at all ( had to use the standard .exe though, and complete via the web browser as copy-all would fail ) Trying it again today, and receiving the same error as the others reporting above. Running Windows 10 Pro 64-bit |
Okay so an update on this. It seems that google.py is causing the issue here. Removing these lines (173-176) made it work perfectly:
Maybe we should find another way to verify it is a valid MAC address. |
same here version 0.4.1 |
I had the same issue on Linux, with pyportify installed from pip. This fix did solve the problem, but we should probably find a more permanent solution to this issue... |
This occurs when I try to sign in with my google account
"Error handling request
Traceback (most recent call last):
File "site-packages\aiohttp\server.py", line 265, in start
File "site-packages\aiohttp\web.py", line 96, in handle_request
File "pyportify\middlewares.py", line 18, in index_handler
File "pyportify\app.py", line 51, in google_login
File "asyncio\coroutines.py", line 206, in coro
File "pyportify\google.py", line 27, in login
File "pyportify\google.py", line 207, in _get_android_id
OSError: a valid MAC could not be determined. Provide an android_id (and be sure to provide the same one on future runs)."
The text was updated successfully, but these errors were encountered: