ValueError: too many values to unpack (expected 2)

Bugs and issues Mac
#1

I no longer can sync data between mac and Google.
I am getting errors ValueError: too many values to unpack (expected 2) for different upload/sync actions.

  File "idesksync/oauth2client.pyc", line 197, in get_token
  File "idesksync/cloudwork.pyc", line 830, in get_changes_for_tops
**[Truncated 105799 lines]**
  File "idesksync/cloudwork.pyc", line 830, in get_changes_for_tops
  File "ideskgd/gdcloud.pyc", line 552, in get_changes
  File "ideskgd/gdclient.pyc", line 631, in get_changes
  File "ideskgd/gdclient.pyc", line 334, in request_resource
  File "idesksync/cloudclient.pyc", line 99, in _request
  File "idesksync/oauth2client.pyc", line 197, in get_token
  File "idesksync/cloudwork.pyc", line 830, in get_changes_for_tops
  File "ideskgd/gdcloud.pyc", line 552, in get_changes
  File "ideskgd/gdclient.pyc", line 631, in get_changes
  File "ideskgd/gdclient.pyc", line 334, in request_resource
  File "idesksync/cloudclient.pyc", line 99, in _request
  File "idesksync/oauth2client.pyc", line 197, in get_token
  File "idesksync/oauth2client.pyc", line 231, in __refresher
  File "idesksync/oauth2client.pyc", line 292, in __refresh
  File "idesknet/httpclient.pyc", line 169, in request
  File "idesknet/httpclient.pyc", line 221, in raw_request
  File "idesknet/httpclient.pyc", line 384, in __request
  File "ideskcore/mainhttp.pyc", line 31, in get_info
  File "ideskcore/mainhttp.pyc", line 49, in __system_proxy

I have been recently in a different timezone and after return I see only these errors.
Any idea?

#2

Hmm, interesting.
I deleted all Insync connections from my Google account, uninstalled Insync, removed config files, installed Insync and with Alternative login option I am getting same error:

image
image1052×230 13.3 KB

#3

Hi @peke. I’m replying here to acknowledge your Forums post aside from our chat correspondence.

As mentioned in the chat, I have requested your log files so I can forward this issue to our engineers for further investigation.

#4

For anyone who might be experiencing a similar issue, please try disabling your proxy settings if they’re not using it or use manual settings if needed.

Thank you!

#5

The issue is still there eventhough I set NoProxy in Insync and switched off system proxy settings.
It is very frustrating :frowning:

#6

@peke Agh, sorry to hear that it’s persisted! Let me forward this to our engineers for further investigation.

#7

@peke Hello! Please follow the steps below:

  • Restart Insync and set the proxy settings to No Proxy on the app
  • Close Insync after the error appears again
  • Collect the logs.db and out.txt files, and send them to support@insynchq.com

Thank you!

#8

Few days it works, few it doesn’t :man_shrugging:
Now after restart it is working again without problems.

But please I collected logs and sent them to you.

#9

We will continue with our investigation, and update you afterwards.

Thank you!

-Mia