CODEWITHSUNDEEP
dialogflow-esactions-on-google
ZhiPeng Zhang
ZhiPeng Zhang

Reputation: 71

Actions on Google - My alpha tester could not access my action

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:

Appreciate for any help or advice

Upvotes: 7

Views: 3434

Answers (6)

Tantris
Tantris

Reputation: 91

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.

Upvotes: 0

user11419010
user11419010

Reputation:

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.

Upvotes: 0

Rosana Reischak
Rosana Reischak

Reputation: 11

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 "[email protected]". "

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.

Upvotes: 1

Bret Houston
Bret Houston

Reputation: 11

I ran into a similar issue with Google Actions/Dialog Flow. Here is how I resolved it...

  1. Share the app from within DialogFlow to the test user
  2. Copy the current DialogFlow URL from the address bar
  3. Launch an Incognito Window
  4. Paste the DialogFlow URL from Step 2 in the address bar
  5. Log into DialogFlow using the test account
  6. 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.

Upvotes: 1

ffritz
ffritz

Reputation: 2261

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.

Upvotes: 1

Abhinav Tyagi
Abhinav Tyagi

Reputation: 5256

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.

Upvotes: 3

Related Questions