I've been trying to create a new agent in DialogFlow. I have one agent and that has problems. (Using share never adds reviewers or developers after I press save.)
So I decided to create another agent - a new agent. I enter a name, time zone, click the create button.... it turns yellow and says "saving".... and then it turns orange and says "canceled." There is no explanation or any help document I can find that identifies the problem.
So the answer is... I have no idea why it works now but it appears there are account problems.
I went to Fulfillment and noticed the inline editor was off. I tried to turn it on and it would go on and then go back to disabled on its own. Wouldn't work. Went back to look again an hour later, same problem. Went to the Share portion about 10 minutes later to try to add a developer just one more time - and this time it worked. I went to Fulfillment and suddenly inline editor is turned on.
For at least 24 hours it didn't work. My developer claimed not to have access and when I looked, nothing in Share. Now all of a sudden it's working and I was able to readd the developer.
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.
Initially, I built up a test agent on DialogFlow console according to the document, and it works well on the Actions On Google which is a simulator of Google Assistant on mobile devices.
Then, I deployed it through the Release in the left menu as you can see the pic attached.
deployed successfully
After that, I added some Alpha Testers including my colleague and sent my opt-in link to my colleague, besides, I granted them all the viewer permission in IAM.
However, problem appeared. It didn't work well on my testers’ phone(IOS 10+) but only worked well on developer's account(mine). When they opened the link I sent to them, and clicked send to devices, then clicked the notification on top of the screen.
send to device
The result is shown as below.
Google Assistant didn't respond to "Talk to mytest app"
In my case the command was set as "Talk to hello qad", and it did work well on my phone used the developer account.
developer account works well
If my tester input the text "Talk to hello qad", it just replied some direct searching results not hello qad diaglog.
To recap:
My action has already been in "deployed" status for couple of days
I've added the tester accounts in whitelist and give them "Viewer" permission in IAM
Testers could see the action directory page in devices by open opt-in link, but they couldn't see the "I'm In" button and couldn't access the action
Appreciate for any help or advice
During my project development, I also faced a similar issue. This is how managed to do testing:
Made sure all Google Accounts were created with the US as the country.
Through IAM, share AoG project with the tester's Google accounts.
All testers to open the shared simulator link in their browsers. This is important!
Test the app on browser first using the simulator.
Once tested, use any device with the whitelisted Google Accounts.
US country was required for my use case as I was having Transaction API in my Assistant. I had to also mock my location to the US on mobile for testing US specific features.
See if the above steps help you.
I contacted Google and this is what they said:
You have to copy the link to the notes app, and then click it and in the prompt, choose “Open in Assistant”.
Full text:
Please ensure that the opt-in link is opened in Google Assistant app and not in a browser. At this time, Google Assistant app is only available in USA. For opening an opt-in link in iPhone or any iOS device, please follow the steps below:
1. Download the Assistant App in App Store
2. Log in using the included account for Beta testing
3. Copy the opt-in URL to Notes app
4. Hold press the opt-in link then select 'Open in "Assistant"'. Google Assistant and App page in the Assistant Directory will be displayed.
5. Scroll down the page until you see the "Become a Beta tester" section
6. Click the I'M IN button
7. Test the Action
This does not work for me, probably because I am not in the US. However, the app is of course available here.
I ran into a similar issue with Google Actions/Dialog Flow. Here is how I resolved it...
Share the app from within DialogFlow to the test user
Copy the current DialogFlow URL from the address bar
Launch an Incognito Window
Paste the DialogFlow URL from Step 2 in the address bar
Log into DialogFlow using the test account
At the Standard Google Account Access Prompt Allow the access so your Google Action can talk to DialogFlow.
I couldn't find this documented anywhere and wasted about 8 hours figuring it out.
For me it only worked after I shared with the user the link to test on desktop that look likes: https://console.actions.google.com/project/XXX/simulatorcreate?isDeepLink the one you can get the the console menu on the sharing icon.
I asked him to login with same google email he has opted-in in Google Assistant and
to verify if when mouse over on the devices icon on the menu he would see "Testing on Device: Enabled
You currently are able to test your Actions on all
Assistant devices connected to "xxxx#gmail.com". "
Then he could invoque almost right away the alpha version of the BOT.
All that considering that he has already clicked on the opt-in link, I had added his emails as a Alpha tester and I had also added him as a Viewer on Permissions at the console admin https://console.cloud.google.com/iam-admin.
If you are a developer of the project, the test version is enabled by default on your device. If you want to access the alpha and beta versions, make sure to disable the ‘Testing on device’ option on the Actions Console simulator.
Add users before deploying alpha release
I feel obligated to copy dedman's comment on your question here, since his solution worked for me and is the only one directly addressing the problem at hand: an alpha release is not available to testers you have added after deploying the release.
As stated in question, you first deployed the test version and then added alpha testers. You might have to publish new alpha version "after adding the testers" and then wait till you get "deployed" status on the new alpha release too... – dedman
I was encountering this exact problem with the Alpha release of my Action, i.e. assistant not responding on alpha users devices, even though I had deployed the release, shared the opt-in link with users and had them click on it to opt-in. Deploying a new alpha release after users had clicked the opt-in link solved the problem and the action is now responding correctly for all users.
IAM Viewer status is not mandatory
By the way, I can also confirm your suspicion that "Viewer" permission in IAM is not needed for alpha users to have access to your release - they only need to opt-in before you deploy a new release.
I am trying to test my agent on a real device. Following instruction from
Official Google video
However, my panel for integrating Actions on Google doesn't look similar to the one shown in the video.
I see neither AUTHORIZE nor PREVIEW button. I can not set invocation name and TTS voice as well.
I attached my panel that I see. Is there anything missing?
My Action on Google dialog:
That video predates recent changes in the API.AI Actions on Google screen.
The name and voice are now set in the Actions Console, but neither are required to do testing.
If you're willing to accept the default voice for testing, you can
Click on the "Test" button in the screen you're referencing.
You can then go to the Simulator (there will be a link provided) or ask any Assistant device (such as Home) to start your action with "Talk to my test app".
They launched this new platform on the Google I/O.
Now you have the invocation name and everything else in the Actions on Google Console.
It's a pretty intuitive platform, the only annoying thing is that you need to fulfill all of the App information before testing. You can see that the simulator is in this console as well.
Whenever you modify things in API.ai, click the UPDATE button (the one in your print screen), then TEST. Then you can test in the console simulator.
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!