You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2021. It is now read-only.
Currently the sync request does not work anymore, because the API for it has changed.
Therefore, the configuration used by the Google Assistant cannot be updated anymore.
Before the API change a unique id was added as a query parameter to the sync request uri to identify the action.
We added this id as a secure parameter for our heroku application.
With the new API the owner of the action has to generate a service account key.
I guess this key is then used for oath authentication.
The actions-on-google npm package provides an easy way to make sync request with this key.
So, I think the solution to this problem is as follows:
Generate the service account key for the BCO action
Add the json content of the generated key file as a secure heroku parameter
User the package by google with this parameter to make the sync request
The text was updated successfully, but these errors were encountered:
Currently the sync request does not work anymore, because the API for it has changed.
Therefore, the configuration used by the Google Assistant cannot be updated anymore.
Before the API change a unique id was added as a query parameter to the sync request uri to identify the action.
We added this id as a secure parameter for our heroku application.
With the new API the owner of the action has to generate a service account key.
I guess this key is then used for oath authentication.
The actions-on-google npm package provides an easy way to make sync request with this key.
So, I think the solution to this problem is as follows:
The text was updated successfully, but these errors were encountered: