Oauth flow gets stuck after agreeing terms and conditions when authenticating brand accounts

[musakhawaja1]

I have an app deployed which worked perfectly up until yesterday. Users used google oauth to link their youtube channels to the app. The problem I am facing now is that when a user tries to link a brand account or if a user has multiple youtube channels under the same email, he gets stuck in the oauth flow after agreeing the terms and conditions. The redirect back to my homepage never happens. In the browser console, the following error appears:
Transport Error: "Error code = 103, Path = /_/OAuthUi/data/batchexecute, Message = There was an error during the transport or processing of this request., Incomplete XSS header at end of request (HTTP Status: 401) (XHR Error Code: 6) (XHR Error Message: ' [401]')"

Any help on this will be appreciated 

[-Rhett]

Hi @musakhawaja1,

Welcome to the Google Cloud Community!

Our team is currently aware of similar issues where OAuth flows are failing to complete and redirect. We’re working to address this. In the meantime, you may consider creating a new OAuth 2.0 flow for your app as a possible workaround.

For now, I recommend creating a bug report. Include steps to replicate, configuration settings, screenshots, and other details of the issue to help us investigate. While there isn’t a specific timeframe for resolution, once we've fixed an issue in production we'll indicate this and then update and close the bug.

You can also cross post your thread on the following channels for more visibility:

• YouTube API on Stack Overflow
• YouTube API on GitHub

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[musakhawaja1]

Hello, thank you for the reply. This has been reported numerous times in the issue tracker but we keep being told to contact cloud support as they handle OAuth. Whereas here, we are being told to go back to issue tracker. Can someone inform the relevant team so it gets solved as soon as possible. Thank you