Configuration Questions / Google API

[mnlmaier]

Question

Hi, thanks for the plugin! We would like to use it in a project, but are currently experiencing some issues which you might be able to help us with. It's most probably not really a issue of the plugin itself, but I'm struggling to understand how we should set up our Google / YouTube account authentication.

We are an agency and authenticating on our client's behalf. We tried authenticating using the account of the client directly, and also tried using our agency account, added as a manager to the client's account (which would be the preferred way).

We end up running into the error above. We're able to see previews of already added YouTube links, but are unable to browse consistently — we're regularly running into errors.

2025-02-25 14:17:25 [ERROR] An error was thrown for an API request for “verbb\auth\providers\Google”: “Client error: `GET https://www.googleapis.com/youtube/v3/playlistItems?maxResults=12&pageToken=CAwQAA&q=Bistum+Passau&part=id%2Csnippet&playlistId=UUbyQY2SbcOKUySPI7mUXbLg` resulted in a `400 Bad Request` response:
{
  "error": {
    "code": 400,
    "message": "The request specifies an invalid page token.",
    "errors": [
      {
  (truncated...)

Have you experienced those errors while building the project by any chance? We've of course followed the instructions shipped with the plugin. Is there any step which is particularly error prone and could be the cause of the error above? Of course I was checking Google for the error, but most results only report the error, but I wasn't able to find something which actually fixed it…

Thanks for your help! As mentioned, it's probably not a bug in the plugin, but maybe you experienced this before.

Additional context

No response

[engram-design]

Interesting, that's not something I've come across (yet) I'm afraid. I've even spun up a new Google app following the docs without any issue. Do note however that you'll very likely need to setup the app on the same account as your YouTube access.

You don't have to, but in that case, you'll need to setup things like the consent screen, in order for your app to have authorised access to other Google account's YouTube accounts.

That 403 access error is something I'll look into. Maybe if you can send through some screenshots of your Google app to support@verbb.io (feel free to redact anything sensitive) I can go through things to checkup.