I would adjust the Instructions here Google drive
current step 11
Run the web-based authorization flow from within rclone config, by answering "Y" when it asks "Token already configured - replace it?".
in notice Google Drive and Google Photos users - ACTION REQUIRED
In step 11 run rclone config reconnect YourDriveOrPhotosRemoteName: and answer "Y" when it asks "Already have a token - refresh?". This part is important otherwise rclone won't actually use your new client_id/client_secret.
Repeat for all your google drive and google photos remotes. You only need to make one client_id/client_secret - you can add this to all your remotes but you must also run rclone config reconnect on each of them.
so, what is the precise flow in step 11?
Is reconnect going to require going through the interactive oauth flow again, as documented in rclone config reconnect ?
It looks to me that the impact of this transition can become a mayhem, so that perhaps adding some other actions to those stated in Google Drive and Google Photos users - ACTION REQUIRED could help:
- Could it be possible/advisable to create a command "rclone config switchID" so that it could automate the switch from previous clientID or common one to a new clientID?
- Besides detecting common clientID being using, could offer to help on creating a new clientID or offer to execute "rclone config switchID"