mirror of
https://github.com/rclone/rclone.git
synced 2026-05-19 06:10:00 -04:00
docs: fix googlephotos custom client_id instructions
The Google Photos custom client_id documentation was incomplete - it only mentioned changing the scopes but did not mention that you need to enable the "Photos Library API" instead of the "Google Drive API" in step 3 of the referenced Google Drive instructions. This fixes the documentation to clearly state both differences from the Google Drive setup: - Enable "Photos Library API" instead of "Google Drive API" - Use the Google Photos specific scopes Co-authored-by: hyusap <paulayush@gmail.com>
This commit is contained in:
@@ -659,8 +659,14 @@ second that each client_id can do set by Google.
|
||||
If there is a problem with this client_id (eg quota too low or the
|
||||
client_id stops working) then you can make your own.
|
||||
|
||||
Please follow the steps in [the google drive docs](https://rclone.org/drive/#making-your-own-client-id).
|
||||
You will need these scopes instead of the drive ones detailed:
|
||||
Please follow the steps in [the google drive docs](https://rclone.org/drive/#making-your-own-client-id)
|
||||
with the following differences:
|
||||
|
||||
- At step 3, instead of enabling the "Google Drive API", search for and
|
||||
enable the "Photos Library API".
|
||||
|
||||
- At step 5, you will need to add different scopes. Use these scopes
|
||||
instead of the drive ones:
|
||||
|
||||
```text
|
||||
https://www.googleapis.com/auth/photoslibrary.appendonly
|
||||
|
||||
Reference in New Issue
Block a user