Google Photos - Sync Issue ("rclone create" OAuth nuance?)

It is specific to the client_id I think. It doesn't specifically say that in the docs

Adds one or more media items in a user's Google Photos library to an album. The media items and albums must have been created by the developer via the API.

But the way Google identifies developers is with the client_id

Sorry about that. We should put a note in the docs about that at minimum.

I'd go for option 2 I think.

If you do rclone lsf gphotos:album -vv --dump bodies

Then you'll see lots of JSON on the screen. It is quite well formatted though and you'll see bits like this

    {
      "id": "ABdUxBXXX",
      "title": "album/potato",
      "productUrl": "https://photos.google.com/lr/album/ABdUxBXXX",
      "isWriteable": true,
      "coverPhotoBaseUrl": "https://lh3.googleusercontent.com/lr/AFBm1_Y7GbXXXX"
    }

This has name of album album/potato and isWriteable which will tell you whether the client_id in use can write to the album.

Rclone checks that flag to make the "google photos API only allows uploading to albums rclone created" message.

You can also do this from the dev page here: https://developers.google.com/photos/library/reference/rest/v1/albums/list