valid MAC coiuld not be determined

I got my google play music auth code but then tuijam fails with this error:

Traceback (most recent call last):
  File "/home/mark/.local/bin/tuijam", line 11, in <module>
    load_entry_point('tuijam==0.7.1', 'console_scripts', 'tuijam')()
  File "/home/mark/.local/lib/python3.7/site-packages/tuijam/app.py", line 630, in main
    app.login()
  File "/home/mark/.local/lib/python3.7/site-packages/tuijam/app.py", line 121, in login
    locale=locale.getdefaultlocale()[0])
  File "/home/mark/.local/lib/python3.7/site-packages/gmusicapi/clients/mobileclient.py", line 184, in oauth_login
    return self._login(session_login, device_id, locale)
  File "/home/mark/.local/lib/python3.7/site-packages/gmusicapi/clients/mobileclient.py", line 125, in _login
    raise OSError("a valid MAC could not be determined."
OSError: a valid MAC could not be determined. Provide an android_id (and be sure to provide the same one on future runs).

I’m running python 3.7.5

[silentjay]

If anyone wants a hacky way to get tuijam running around this issue: change line 123 in /home/YOUR_USER/.local/lib/python3.8/site-packages/gmusicapi/clients/mobileclient.py
mac_int = getmac() to mac_int = <YOUR_MAC_AS_INTEGER>

yeah nasty, but I wasn’t prepared to let a google play music browser tab to continue to steal 500mb of ram anymore.

[cfangmeier]

It should be pretty straight forward to support an optional MAC from the config file. In earlier versions, tuijam would query gmusicapi for an android id and use that, but it was simpler to just use the MAC address under the assumption that it would always work. Obviously, this is not the case. A more robust solution may look like:

1. If supplied, try to login using a MAC specified in the config file.
2. If 1 fails, try to determine and use the MAC as is done currently.
3. If 2 fails, query the api for android ids. Iterate through them until finding one that works. (Optionally - store the working id in the config file)
4. If 3 fails, give up!