Re: GDrive: Automatic refresh of oauth2 access token
"Norman J. Goldstein via Duplicity-talk" <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.duplicity.general |
|---|---|
| Message-ID | <[email protected]> |
Duplicity is till running on my GDrive setup, so problem solved. The moral of the story -- keep it simple. Curiously, my response, below, did not seem to make it to the group. ?? On 2024-05-21 12:32, Norman J. Goldstein wrote: > I may have found my mistake. In my OAuth publish screen, I uploaded a > logo/icon (why not? they asked). I just noticed that this is what > was causing my project to need verification! So, I deleted my logo, > and now my verification status, is "Verification not required". It > seems I am published. > > So, I will start up a new project and see if my access keeps chugging > along. Will report back in a couple of weeks. Thank you for your > help, and sorry for any lost time. > > There is an answer to your question, below. > > Norm > > On 2024-05-21 11:28, edgar.soldin--- via Duplicity-talk wrote: >> hey Norman, >> >> On 21.05.2024 19:56, Norman J. Goldstein via Duplicity-talk wrote: >>> I followed those instructions -- very clear, thanks. One addition I >>> suggest is to mention: When setting up, the file at the end of the >>> path, GOOGLE_CREDENTIALS_FILE, must not already exist. >> >> you mean like it throws an error if the file exists beforehand? > Yes > > _______________________________________________ Duplicity-talk mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/duplicity-talk