I'm building an Action on Google and struggling to use the Alpha testers functionality. I have two G Suite accounts: one business and one personal (yes, I use G Suite, not Gmail for my family email). My business account is the Project Owner of the AoG project, and it's where I do most of my work. My Google Home is associated with my personal account, as is the Assistant app on my iPhone.
Initially for testing I added my personal account as a Project Owner and used the Simulator to enable Testing on Device. This allowed me to test my Action using my Google Home on my personal account.
Now I'd like to switch my personal account to be an Alpha tester, instead of using Testing on Device. While logged into the console on my personal account, I put the Simulator back into the state "No tests currently active." Somewhere along the way I whitelisted my personal account and opened the Opt-in link in a browser signed-in as my personal account. I clicked Send to Device -> Living Room Speaker (later I tried sending to my iPhone, too), but I still can't get to my Action. When I say "Talk to ", it responds with generic search results or the wrong Action.
How can I get my personal account back into a state where it can become an Alpha tester of my Action, after having used the Simulator's "Testing on Device" functionality in the past?
Related
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.
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'm playing around with api.ai to add some possibilities to google assistant and the google home.
I've created a new project in "Action on google" with some very very simple interactions defined in a new agent in api.ai ( only one intent and a few possible responses)
following those steps: https://developers.google.com/actions/get-started/create-project-agent
I now try to test it on my device. I've first tested it in the simulator following those steps:
https://developers.google.com/actions/get-started/preview-the-app
So I can test it in the simulator by saying "talk to my test app". Unfortunatly I don't kow what to say to my home device to trigger the testing. (Note that my device in setup in FRENCH so it is maybe a language issue)
I've read that :
all you need to do is log into the device using the same account that you used to authorize your action for testing in the simulator. Once you authorize your action for previewing, it will automatically be available on the Google Home device assigned to that same account. Note that you need to be authorized in the API.AI account under the same Google account in order for this to work!
I use only one google account, the same on home device, api.ai and google actions. This account is the owner of the new project when I check its permissions. So this should be fine.
Any idea would be helpful. Thanks
As of today (Oct. 6th 2017), you will be able to set French as a language for your API.ai bot and test it on a device or in the web simulator.
Make sure that you have also configured the related Actions on Google app in English AND French (and eventually for the locales -- french (Europe) and french (Canada)). You must have one configuration per language/locale in your bot.
Unfortunately, while the Google Assistant has launched in French, Actions on Google hasn't yet. Until it does, there is no French support for testing actions except through the simulator (where you'll be testing in a different language).
My question is about Facebook Ads API's March 4 breaking changes regarding the new campaign structure.
I do not have a test account nor a test app yet. I would like to test whether my code supports all the March 4 breaking changes. I have neither a test account nor a test app. I have requested a test account through email (this was suggested in the change FAQ). I will later whitelist the account for accessing the structure changes.
To get the test app, do I have to use only the test account (creating an app requires a developer account) or can I create the test app directly by using my production facebook ads account?
Also, the page to apply for test ads app is the same as getting a normal ads app. FAQ suggests that I add "test" to my name. Is this all I have to do or is there something more? The link for helping set up app in the FAQ doesn't seem to point to the right place and doesn't help.
1-To get a test app all u need is to be a developer. Once the app is created u can use it with a test/production account.
2-test and production apps can be created from the same place. Just put "test" in the app name.
I have created an iTunes test User account from My Developer account.
My client has set up (on a different developer account) an application and in-app-purchase product.
Will I be able to use my test user to purchase the product the client has set up?
The answer is no - you can not.
Test users are restricted to buying content in the sandbox for Products on the Developer account they were created on.
I managed to get a friend to help me test this and got this error when I used his test user.