I'm getting so many errors trying to create non-english AoG projects with Dialogflow.
The error is:
Failed to upload action package to AOG (preview)
Request contains an invalid argument.
Locale pt-br was selected but the language pt-BR has not been selected.
I did this steps in Dialogflow:
Clicked at create new agent
Set default language to Portuguese(brazilian) - pt-br
Clicked at create button
After working progress, I did this path Integration -> Google Assistant -> Test
The AoG page did not open and I got the error above.
Does someone know how to fix this issues?
Did you have an existing Actions on Google project with the same language?
I usually create the AoG project first (when creating non-English Actions) and then I create the Dialogflow agent by going under Actions -> Build -> Custom. When you select the same language in Dialogflow, and click create it should work.
Related
I am using Dialogflow Essentials and i already have english language working fine in google action and google assistant. Now i am trying to integrate french-Ca from dialog flow to google action console,
i am not able to see french-Ca in google action console. When i go to the google action console , i can see 12 Actions in english but none in french-Ca. I did these steps: Integrations-Continue with integration, and close.(All the intents are marked). Also tried Add action from google action console but couldn't make it happen. Can someone please assist me with that? Thank you
You can modify the languages supported in your Action from your project's settings in the Actions Console.
Example URL: https://console.actions.google.com/project/YOUR_PROJECT_ID/settings/languages
You can select French and add the Canada locale using the 'Add locale' button.
Whenever I am trying to test my intents in the Dialogflow "Try it now" tab, Dialogflow automatically logs out. Have anyone faced the same issue ? How to resolve it ?
n.b. I am using webhook for some intents
I had the same problem and I managed to solve it by deleting the agent and recreating and import it to the existing google cloud project.
but I still have the same problem whenever I import a prebuilt agent, my current google cloud project won't show in the google cloud project list (i think this is because only one agent allowed per project), and if tried the "try it now" on the prebuilt agent it will redirect me to log in.
I have built an action with Actions-on-Google(2.5.0) and dialogflow-fulfillment(0.6.1) Node.js Library. I cannot test my app on dialogflow test console because I return conv object which is not supported there. Now, I cannot test it in the google action simulator, either. This is the error I get:
Invocation Error
You cannot use standard Google Assistant features in the Simulator. If you want to try them, use Google Assistant on your phone or other compatible devices.
I'd like to use the simulator, so I can debug better.
It is how the error message says: The simulator lacks many features that normal Assistant surfaces (speaker, Assistant app) have and can even sometimes give you completely wrong error messages. There is really no way around testing your app on real devices.
You can however view the same logs that you see in the simulator in Google Stackdriver Logging. To activate this go to the settings of your Dialogflow agent, select the "General" tab and activate the "Log interactions to Google Cloud" option. Then click on the link below the button to get to the logs. The default view will probably show you only the Actions-on-Google logs, i.e. the requests between your users and AoG. To see the requests between Dialogflow and your webhook click on the dropdown arrow in the filter box, select "Convert to advanced filter" and set the filter to resource.type="global".
If you have multiple Actions projects that use the same display name, the simulator chooses one at random. For consistent testing results, use unique names or release channels for each Action.
Reference Link: https://support.google.com/actions-console/answer/9613473?hl=en
Now how to give a display name or change the display name.
Go to develop tab and give display name or change display name as follows
You should definitely be able to test your action in the Actions simulator. Note that the interaction model b/w Dialogflow and Actions simulators are different. In Dialogflow, you can send commands directly to your agent. In the Actions simulator, you first need to invoke your Action.
At the bottom of the screen, you'll see a suggested input like "talk to my test app".
You'll need to send this, or a similar command, first. That will then invoke your action, and you'll be able to send commands to it after. You will see it is invoked by a banner at the top of the simulator.
I've started playing around with Google's Dialogflow and created a simple project. When I go to the Google actions console the Chrome window is grayed out.
Is there perhaps something I have missed or need to enable?
Here are the steps I have taken.
Created a new Test project in Dialogflow
Created two entities under the Entities tab, namely Device and Power and called it Entities (See screenshot)
Under Intents tab
Created some training phrase's
Entered the text "Send" in the action textbox
Created parameters for the two entities, #Device and #Power
(See screenshot)
Under settings of the project
Deployed the project to a DEV environment (See screenshot)
Clicked on the "Manage in assistance console" on the Environments tab. I'm then redirected to the actions console page that is unfortunately disabled. (See screenshot)
Hoping someone will be able to assist.
Okay so I contacted Google support and they were quick to respond and provide me with a resolution.
Turned out that I had a Chrome extension that affected the AoG/Dialog console behaviour. So I disabled the Chrome extension and it worked.
What you can also try for those that encounter a similar issue is to go to the console actions page in incognito window and see if that works for you.
2 days ago the integration between Google home and API.AI agent worked perfectly. Since yesterday, when the API.AI was updated to include Google Assistant integration instead of Google Home, i had to do some extra steps on Action on Google console to make that integration work again.
But when i click on "Fulfillment" on API.AI menu, then "Google Assistant", i get the following screen:
enter image description here
But when i click on "update" or "test" i get the following error message: "Request contains and invalid argument".
How can i solve this?
Unfortunately, I too had to recreate with a brand new agent. Here's the steps I took that may help others who venture down this path...
Create a new Actions on Google project from the console: Actions on Google console
Create a zip file of just your intents and entities folders. They need to be in the top level of the zip file. (agent.json seems to be the one file that kept blowing up my agent after Google updated everything)
Create a new Agent in API.ai as you normally would
Save and finish up the "Actions on Google" console setup for the new project
Go back to API.ai and click on "Integrations" and "Actions on Google". This will allow you to click on "Update" and hopefully test the generic beginning of the agent successfully.
Finally, once you have tested the generic agent, import the zip file you created earlier and all "should" work fine. You'll have to update your fulfillment server if using one, etc.
The above works as of the morning of May 23, 2017. Good luck!