I am trying to test an alpha version of a dialogflow/google-actions on my Android phone, but Google Assistant don't open the opt-in link as expected (see screenshot below).
What I did :
I have created a project in Dialogflow, and activate the Google Assistant option inside Dialogflow
I have configured the associated project on Actions-on-Google
The "Simulator" works well and the "Testing on Device" option is activated
The Alpha release has the "Deployed" status and my gmail email is in the alpha-testers list
But when I click on the opt-in link from my Android phone, it only opens a blank page which ask me to give a feedback on nothing (as shown in the screenshot).
Two additional things to make sure you've done before Alpha testing:
Make sure you have the Google Home app installed on the phone you're testing with and that app is logged into the account you're inviting into Alpha.
Make sure you've allowed enough time - even in the "Deployed" state, it can still take a few hours to be available to everyone.
Related
How can I test my Actions Builder project on an Android device (for example on my mobile phone)?
Can I publish my project and assign it to a device or a Google account? How I am able to use this Google Assistant project from this Google account?
In the Actions Builder console, once you go to the "Test" tab, you will be able to invoke the Action on any Google Assistant device that is using the same account. If you've given the Action a name already, you can invoke it with "Hey Google, talk to name of action." If you haven't given it a name, you'd use "Hey Google, talk to my test app."
The test page gives you details, just in case.
If you need to use a different account to test with, you can publish to the Alpha channel. With this:
You can control who is permitted to access the Alpha version by adding them to a user list. (Up to 20 accounts.)
You then provide them with a link to opt-in to the Alpha version. (They will need to access this link from chrome on a mobile device.)
Unlike other "releases", this does not need to be approved by Google.
To begin an Alpha release
Select the "Deploy" tab along the top
Select the "Release" left menu item
Select the "Start a New Release" button
You will also need to add Alpha testers via the "Manage Alpha testers" link
I have deployed an Alpha version of my app and supplied the email address of a tester and received the opt-in link the user can use to access the Alpha app. In typical fashion, Google gives no instructions for the user, who clicks on the link and promptly gets an error message that no Google or Stackflow search throws any light on.
A further Stackflow search reveals a complex procedure for an Android phone involving copying the opt-in link to Google Notes, pressing on it, and then taking the option to open the Google Assistant app. It would be difficult to find a better way to discourage testers.
Also, this only opens the app on an Android phone. No mention of how the 20 testers can access the Alpha app on Google Home or Nest Mini. Frustrating when the app is specifically designed for use on Google Home or Nest Mini and not on a phone. Does anyone have a solution?
Users need to opt-in to the alpha program on the phone by following the link. (They shouldn't need to copy it, but they will likely need to open it in an actual browser such as chrome.)
Once they have opted in, however, it will be usable on any device linked to the same account on your approved list and that they used to accept.
I was trying to make an alpha release of my app, the opt-in link that has to be shared with the testers is not opening on the desktop browsers but is working fine when directly opened on the mobile device. I am unable to figure out the problem.
This is working as expected or at least a known issue. The opt-in link is supposed to be opened on mobile devices and not in desktop browsers.
From the Google docs:
The Actions directory for the web is not supported for opt-in to alpha/beta. Make sure your testers follow the link on their mobile devices (Android or iOS).
When users click on this link, they are directed to the corresponding Action's directory page. They should click on the I'm in button at the bottom of the Action's directory page to opt in as a tester for the first time.
We have developed a prototype for Google Home and running user tests but have found that the 'test' Action is only triggered on my voice and NOT available to others trying to invoke (device is registered to my development account).
Is there some some restriction?
Testing an Action makes it available for the account which activated the test. It does not make it available for every account on a device - Actions do not load anything on the device itself, they simply permit the account to the trigger commands on Google's server.
If you want other users on the device to access the Action, you need to explicitly permit them to the action. You can see the details, or they're listed if you click the share icon in the simulator, but in short:
Click the gear in the upper left of the console and then the Permissions menu item.
Add team members to the project using the Add button on the top. I usually give them Editor or Viewer project roles.
They then need to visit the simulator page to activate it. They can use the simulator to test, but it is also available on their devices.
Please make sure the account from which you are testing your actions should be given to other testers to test your actions. The account should be connected to the user's Google home to test your actions.
I developed a game using unity engine for android platform.
I have used GPGS plugin from github
But i was unable to "sign in" into GPGS during testing phase(A popup comes up saying "connecting to GPGS" loads 2 times and vanish).but as soon as i published my game on google play store,GPGS starts working properly(now i am able to sign in to my account).
Where i was wrong during my testing phase?
I already add tester email on google play console
Try to check this documentation.
Maybe you missed some essential steps.
To add testing access to an account:
Open the Testing tab for your game in the Google Play Developer Console.
Click the Add testers button.
In the dialog that appears, enter the email addresses of the Google Accounts that you wish to add as testers (one email address per
line).
Click Add to save your preferences. The tester accounts you added should now be able to access your Google Play games services.
You can also see this forum for reference.