ust to add a bit more context after digging into this again — one thing I realized is that even if everything looks clean on the OneAll side, Google can still retain previously granted scopes if the app was authorized earlier with broader permission…
Just wanted to follow up on this in case anyone missed it — still trying to figure out the smoothest way to handle this setup.
While digging into it more, I started wondering if part of the inconsistency might be related to how tightly YouTube is…
Hey,
I ran into something similar when setting up social login with YouTube/Google through OneAll.
From what I understand, that “Manage your YouTube account” permission isn’t actually coming from OneAll itself — it’s part of the default scopes…