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.
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 am trying to use the Work Profile version of the Google Assistant app, but I cannot get past the "set default assist app" screen in order to start using Google Assistant. It works on some phones, but not on my Pixel 3 or a Pixel 2 XL that I tested it on.
Steps to reproduce:
Tap on the Work Profile Google Assistant app, and a screen appears to prompt the me to set the default assist app
Tap on "Settings".
When I tap on "Assist App", the "Permission Controller" screen opens briefly and then closes immediately.
Finally any more taps on "Assist App" again has touch feedback show nothing.
Image of screen
Make sure that your work account as permission to access your voice.
Go to the Activity Controls page.
Sign in with your Google account
Enable the following permissions:
Web & App Activity
Under Web & App Activity, check the box next to Include Chrome history and activity from sites, apps, and devices that use Google services.
If that doesn't work, this can be due to limitations or restrictions with work accounts. Contact your admin.
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.
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.
I am developing a smart home app and want to share it to another Google account before it published.
I follow the steps in https://developers.google.com/actions/smarthome/testing-deploying#sharing_your_project
Add a new member xxx#gmail.com and role set to project -> viewer.
But my smart home app does not appear in the home control section of Google Home app when I use the Google account xxx#gmail.com.
When I switch back to my own Google account, my smart home app appears in the Google Home app.
Is anyone encountering this issue?
For sharing your smart home actions with other users, follow theses steps,
Click the "3-dots" icon in the upper right corner of the console (https://console.actions.google.com/)
Click Manage user access (this redirects you to the Google Cloud Platform IAM permissions page)
Click ADD at the top of the page
Enter the email address of the user you want to add
Click Select a role and choose Project > Viewer
Click SAVE
In order to add users to a project, you need to be an owner of the project and after you're done with the above steps then all the added users will be able to see the Actions on their Google console. Additionally the users that have shared access to your Action can test it on Assistant-enabled devices such as their smartphones. But, before they can test the smart home Action, the added users must set up for testing. In order to test that Action device testing must be enabled for that device and after doing that it should be linked to the correct Google account. Performing this setup allows users to test on Google Assistant surfaces and on the Google Home app, using the same account you used to sign in to the Actions console. Find out more about setting up testing at https://developers.google.com/assistant/smarthome/develop/testing?hl=en#setup