GAM-team / got-your-back

Got Your Back (GYB) is a command line tool for backing up your Gmail messages to your computer using Gmail's API over HTTPS.
https://github.com/GAM-team/got-your-back/wiki
Apache License 2.0
2.61k stars 207 forks source link

Traceback returns failed to execute script gyb #280

Closed scidmail closed 3 years ago

scidmail commented 4 years ago

I'm reinstalling gyb after reformatting my hard drive. I went through the steps and found the information to use desktop app instead of "other" and did that. I then entered the verification code I was provided when I hit return, this was the respoinse.

Traceback (most recent call last): File "gyb.py", line 2206, in File "gyb.py", line 1546, in main File "gyb.py", line 525, in buildGAPIObject File "site-packages\googleapiclient_helpers.py", line 134, in positional_wrapper File "site-packages\googleapiclient\discovery.py", line 264, in build File "site-packages\googleapiclient\discovery.py", line 245, in build File "site-packages\googleapiclient\discovery.py", line 308, in _retrieve_discovery_doc googleapiclient.errors.HttpError: <HttpError 403 when requesting https://www.googleapis.com/discovery/v1/apis/gmail/v1/rest returned "The caller does not have permission"> [8356] Failed to execute script gyb

I cannot find anything with this exact error. Did I do something to cause this or is this a new issue?

Barb

jay0lee commented 4 years ago

There is currently an issue with Gmail API on Google's end. See:

https://issuetracker.google.com/issues/160441983

the issue breaks GYB but hopefully Google can fix it soon.

Jay Lee

On Mon, Jul 6, 2020 at 4:20 PM scidmail notifications@github.com wrote:

I'm reinstalling gyb after reformatting my hard drive. I went through the steps and found the information to use desktop app instead of "other" and did that. I then entered the verification code I was provided when I hit return, this was the respoinse.

Traceback (most recent call last): File "gyb.py", line 2206, in File "gyb.py", line 1546, in main File "gyb.py", line 525, in buildGAPIObject File "site-packages\googleapiclient_helpers.py", line 134, in positional_wrapper File "site-packages\googleapiclient\discovery.py", line 264, in build File "site-packages\googleapiclient\discovery.py", line 245, in build File "site-packages\googleapiclient\discovery.py", line 308, in _retrieve_discovery_doc googleapiclient.errors.HttpError: <HttpError 403 when requesting https://www.googleapis.com/discovery/v1/apis/gmail/v1/rest returned "The caller does not have permission"> [8356] Failed to execute script gyb

I cannot find anything with this exact error. Did I do something to cause this or is this a new issue?

Barb

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jay0lee/got-your-back/issues/280, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDIZMFHLEKMJSBNFJSDMB3R2IWYFANCNFSM4OR56E2A .

scidmail commented 4 years ago

Thank you for the information. At least it's not just me. :-)

UnknownAlienTechnologies commented 3 years ago

Hi, I still have this issue. Any update?

mehyaa commented 3 years ago

Similar error here:

Traceback (most recent call last):
  File "gyb.py", line 2206, in <module>
  File "gyb.py", line 1511, in main
  File "gyb.py", line 460, in doGYBCheckForUpdates
  File "httplib2\__init__.py", line 1985, in request
  File "httplib2\__init__.py", line 1650, in _request
  File "httplib2\__init__.py", line 1557, in _conn_request
  File "httplib2\__init__.py", line 1391, in connect
  File "httplib2\__init__.py", line 1324, in connect
TimeoutError: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[20996] Failed to execute script gyb

Seems like the issue on Google side has been closed because of inactivity: https://issuetracker.google.com/issues/160441983

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.