I have a voice skill for Google Assistant which requires account linking. Before, I was able to test this in the simulator by going to the Debug tab and there would be a URL that I can use to do the account linking. Now, that URL is no longer there, and I'm not sure how to do account linking using the simulator anymore. Is this a bug or did Google intentionally remove this information from the Debug tab of the simulator?
Nevermind, I realized that you can just reply "Yes" in the simulator and it opens up the account linking window. Although the link in the Debug tab is still gone, I can still perform account linking. That's good enough.
Related
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.
Me and a colleague are using a business instagram account together so we can both have access and upload stuff.. but when we try to invite friends/follow it only comes up with "my personal profile friends" and not any of my colleagues? the insta accounts linked to our company's FB page..? so should have both of our fb account detail, ie friends and stuff??
Sorry I am not a developer :D and dont really have a clue if this is possible or if there is a way of doing it.
Thnks
This isn't really the forum for this, I would advise confirming things with instagram; Email support#instagram.com. Or report it on the app:
You can provide feedback or report a technical issue by clicking on the Options (gear wheel) in your profile and then tapping Report a Problem in the menu.
Anyways, from what I gather, even though the account is a business account, you must've been the one who created it and linked your facebook account. Even though its linked to your page, it's still only linked to your account, not your colleague's. Even if he is an admin on the facebook page.
With a little more research I found this:
https://www.facebook.com/help/218638451837962
There are more links on this that help with every part. I'm not completely clear on all the details. But everything here should work, again if none of this fixes your problem, confirm with instagram whether what you want is possible at all.
Does anyone know why my action can NOT use in web simulator??
I set my invocation name for testing as "test", and in web simulator , I try to use my action by input "Talk to test", but it told me "Sorry, this action is not available in simulation"...
Is there anything wrong with me ??
I got this to work by saying "talk to my test app" or typing it in to the simulator prompt, that triggered my app to start in the simulator. I am using an account that is NOT associated with a home device, I also have NOT entered in artwork etc.
I have found that you have to type in that phrase anytime the simulator gets confused to get back into your intent flow.
In my case it looks like this in the Dialog portion of the simulator:
Turns out for me, even though I had turned on all the activity controls as the tutorial instructed, the organisation my login was associated with had them disabled.
Ask your admin to enable "Web & App Activity" in "My Account" > "Admin" > "Google Services"
I had same issue. This is how I "solved" it
Registered Google Home physical device to my email used for Action and api.ai development
(Redeployed, now Silly project started working)
(Still my project won't work)
Changed the invocation name to something simple ( My first language is not english)
Now Web simulator started working(
One possible Root cause - you are logged in via your second account.
This is the same issue I had. The UI from the earlier google home tutorials have been changed a bit. So after clicking the actions on google in api.ai we are redirected to to actions on google page. (Previously it was sent to the web simulator straight)
I created a project called personal butler in api.ai but what I saw was a project called API project, so when I clicked it and try to simulate it I got the exact error.
I registered to api.ai from my secondary google email. So when I was redirected to the actions on google page, it logged in via the primary account. After I signed out and loged in via the same account I was able to see my project and it was working fine.
PS - When testing with google home also the same account should be used in the andriod app
This bug should be resolved now. If you are still having this problem, you should try pairing your account with an actual device first. The issue was resolved for me by signing in to the Google Home app on my mobile device and pairing it to a home unit. After that, using the simulator then works in the browser.
Link to previous issue: Gmail contextual gadget broken
Yesterday we received a couple of customer complaints regarding our Gmail gadget. They claimed that it had gone missing from their account. This morning, several of our employees have reported the same although, this isn't happening for everyone.
We haven't made any changes to the gadget and since it loads for some, I don't think this was caused by us.
What happens:
The window of the contextual gadget does not appear in the main Gmail interface
The window of the contextual gadget does not appear when opening an email in a new window (shift + click). This differs from when this happened previously.
We've also contacted Google and they have responded that they are looking into the issue. We've also seen that the shift-click to open an email in a new window doesn't work as a work around this time.
The last time this happened our monitoring showed that about 10% of users lost their access to the gadget per-day. We seeing a similar drop off in activity this time around.
Here are the details of the response I received from Google for this issue
Thank you for contacting Google for Work Support. I understand that
that you Gmail Contextual Gadgets have disappeared again from the
Gmail web interface.
I notice there are other user reporting a similar behavior hence he
have requested an update from our Eng team and I am currently waiting
for their response. As soon as I have an official response, I will be
contacting you back directly with the next steps.
Also I notice you mentioned that the previous workaround is no longer
working. Previously the workaround provided was to press "Shift" and
then click on the email. The email will be opened in a new window and
then the gadgets should be displayed. Can you please confirm if the
above workaround is working or not?
I’ll keep this case open while I wait for your reply. If you have any
other questions or additional comments, don’t hesitate to reply and
I'll be happy to continue helping you.
Sincerely,
Wilmer Google for Work Support
Here is the latest update from Google
As before this issue appears to be UI based as opposed to any problem with the Contextual Gadget API itself, we've gathered some troubleshooting information from affected test environments and are working on identifying a clear root cause and then remedying the behaviour at the moment.
There isn't any further you need to do on your end, I'll update you as I learn of any changes in the status of this behaviour.
Regards,
Patrick
I really didn't wanted to ask that kind of question in this resource, but I have no choice.
I have tried ask this question to Azure Support on Twitter, but they told me to open support case in azure portal itself. However, if you want to use their direct support, you must pay money.
MSDN forums does not allow me to post screenshots until it verifies my account, so this makes posting there useless.
When I want to add new Virtual machine I press Add button on Virtual Machines tab. Then it opens new tab with loading message and hangs. It says loading and then nothing happens.
I have cleared cache of my browser, opended incognito mode, still this happens.
I have installed another browser, opened portal and Dashboard still hangs at loading tab.
I have tried to open portal on my friends computers, problem still persists.
This is screenshot of this problem:
This is Javascript console:
According to this screenshot, Azure Portals Dashboard has javascript errors.
Why this is happening? Did I encounter some kind of bug?
As David said, it is not directly related to the forum, but there was partial portal outage, according to the https://azure.microsoft.com/en-us/status/. North America users were impacted.
Looks like that issue was mitigated.
If that is the helpful answer, please mark it as a helpful or as the answer. Thanks!