I could be misunderstanding something here but I use assistant relay and as my google cloud project for this is testing and not published I didn’t think this was affected based on the following, so have I misunderstood something here?
Determine if you are affected
This deprecation is only applicable to production apps (i.e apps with publishing status set to In Production. The flow will continue to work for apps with the Testing publishing status.
Authorizations by a test user will expire seven days from the time of consent. If your OAuth client requests an offline access type and receives a refresh token, that token will also expire.
There’s no guarantee Google will extend the deadline if you complete the form, but I figured, what the heck, maybe it’ll buy me some time and worst case scenario, Monday’s still doomsday.
Same. Hopefully someone with the skillset can step up to fix…I only have very very minimal experience with oauth, from a developer perspective, and wouldn’t have any free time to even begin looking into this for at least a couple of months anyway, putting us right back to where we are today, running out of time.
Thanks for the link, posting the contents of that comment here for others. I’ll hopefully try it out next week.
When creating your OAuth Credentials, set your app as a Desktop App, not TV.
When creating your user in Assistant Relay, the Google authorization flow does not have a specific pop-up that says “Allow” anymore. Instead, there’s a button that says Continue.
When you finish the Google authorization flow, it’s going to open a tab with a blank screen. Your Auth key is in the url. Copy everything between “code=” and “&scope”. You can paste that into the auth key screen in Assistant Relay setup.
After you visit the URL from your logs and enable the API, it will likely take up to 10-15 minutes for it to start working. Even then, I was not able to get it to broadcast from the sandbox.
When creating a test animation and you select the REST command you created as the action, it did not show the “Service Data” field. Click the 3 dots on your action and click “Edit in YAML”. Now you’ll see “data: {}”. Type anything between the curly brackets, then switch back to visual editor and your field for Service Data will be visible.
I believe it till use OOB verification, to me looks like the only difference is setting authentication up as desktop app, but I am not sure my knowledge not goes that far. All I know is that until now assistant relay is still working good for me
