-
Notifications
You must be signed in to change notification settings - Fork 12
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
There is not sufficient space available in your Google Account #10
Comments
@Garildi it may be an issue with the Google Drive API where storage information for Business Standard account may be exposed in a different way. Google account space limit (bytes): |
Thank you for looking into this! Here you go: 2021/09/27 12:28:18.765|DEBUG|Google account space limit (bytes): |
@Garildi: Documentation from the Google Drive API: For safety reasons I had implemented a measure to avoid filling up the storage account completely. This check should be avoided for accounts with unlimited storage. I expect to fix the issue this coming weekend. Would you be open to test the change? (I don't have an unlimited Google Drive account) |
Draft release created. |
Not sure if this is still supposed to work with the current Google Photos APIs. No matter which API I use (the provided one or my own custom one), I'm always getting the following error message when trying to upload something:
`INFO Authentiation complete.
WARN There is not sufficient space available in your Google Account to upload this folder.
WARN 10.152905 Mb required, only -9.536743E-07 available
Upload failed of Album '001'
WARN There is not sufficient space available in your Google Account to upload this folder.
WARN 10.8710375 Mb required, only -9.536743E-07 available
Upload failed of Album 'New folder'
Upload summary:
Album not uploaded. Not sufficient storage space in Google Photos.
Album not uploaded. Not sufficient storage space in Google Photos.`
Listing existing albums works fine. It's a Business Standard account that still has more than 1TB free space.
The text was updated successfully, but these errors were encountered: