Google actions account linking different URL's in DEBUG- sharedDebugInfo-debugInfo - dialogflow-es

I am new to actions on google and I am trying to explore account linking feature.
I was able to create a project under google actions and link it to dialog flow. Enabled account linking and everything worked fine.
Now I created a second project and followed the same process. This time account linking card is not showing on my google home app.
When I tried to check the difference between two project what I found that the account linking messages are different.
For working action this is the message:
It looks like your <Project name> account is not linked yet. You can link <Project name> to your Google Account from the Google Home app.
For not working action, this is the message:
It looks like your my test app account is not linked yet.
It does not contain the second half of the message.
And also when I tried these actions on simulator, under DEBUG sharedDebugInfo-debugInfo the URL's are different.
For working action:
https://gala-demo.appspot.com/app?login_hint=google email id&service_id=projectid_dev&scope=openid&return_url=https://www.google.com/
For not working action:
https://assistant.google.com/services/auth/handoffs/auth/start?account_name=google email id&provider=projectid_dev&scopes=openid&return_url=https://www.google.com/
Can anyone help me understand why my second action is not working and why is it behaving different from the first one?

Related

How can I delete all scripts and triggers, and remove unauthorised access from my account?

I opened a virus file and someone got access to my emails. After this, I have changed the password and enabled 2FA, but the hacker is manipulating my Google Script.
I keep receiving emails, for example:
Your script, Untitled project, has recently failed to finish successfully. A summary of the failure(s) is shown below. To configure the triggers for this script, or change your settings for receiving future failure notifications, click here.
I don't understand what is happening; how can I delete all of these scripts and triggers, and ultimately remove this person's access from my account?
To completely remove all Google apps scripts access from your compromised account,
Change your Google account password
Visit apps script dashboard and remove all triggers and all scripts there.
Visit your Google account third party apps page and remove all apps with permissions there.
Make sure you're logged into the correct google account.

Google home integration with dynamo DB

I am creating Google Smart Home action of google home. But I have not idea, how to connect the dynamo DB with smart home action but I can see here using with firebase. When I ran the command with invocation name in google assistant then it is showing "something went wrong".
I have enabled the home graph API and also created the JSON key file. I also can see their upload JS file button but don't know, what files should I upload there?
Thank You
It sounds like you are going through the Washer codelab, which is a great first step.
When you are configuring your project in the Actions console, you would need to enter your fulfillment URL from your application (rather than the Firebase URLs shown in the codelab).
You also need to set up an authentication server to enable account linking. Once you've completed this, you should be able to test your Smart Home Action through the Google Home app. Remember that you need to configure the console with your application's URLs for authorization and tokens in place of the demo URLs in the codelab.
The JS upload you are seeing in the console is for local fulfillment applications, which would be a feature to consider adding after you have successfully uploaded and tested your Smart Home Action.

UNLINK OR RELINK - Google assistant account linking flow

I am developing a custom action for google assistant.
In order to get user data and other user info. I need allow account linking flow.
My Account Linking flow:
Open the Google Assistant app on Android or iPhone.
Say the Action – "Talk to My test app”
Read and agree to the Action Terms and Conditions that appear on the screen.
Sign in with Web app.
Go back to Google assistant and ends linking flow
Everything works properly. But once account linked, I am not able to test the flow again
Could anyone suggest, how to unlink my account and test the above account linking process again? Thanks in advance
During development you can unlink your account via the actions on google console. If you navigate to the test window, you can see a settings button on the top right, click that and a setting pop-up should open. There you should look for an unlink button.
This will unlink your account, so when you restart the conversation for your action with this account, you will be prompted to sign-in again via accountlinking. This also works if you are testing on your phone. You just need to make sure that the account on your phone and the simulator are the same.

how to delete "google sign in account" for development purpose - actions on google

I'm working with actions on google and dialogflow, and recently they proposed google signin to make account linking fast without writing own oauth server.
Today I implemented their google signin in my dialogflow app it is working quite fine but unfortunately I am unable to delete that account to check all development aspects, I tried my other google accounts and my friends account but soon ended up out of accounts
Un other methods when i enable and disable testing it forget about linking but in google signin it is tightly stick with the account, and i have tried almost everything i can try like restarting my phone and clearing cache of chrome browser but it looks like it is saving account somewhere in cloud.
What i need to do is, when i sign in first time it ask for name permission, i need that screen again and again for testing something
Google calls this Removing a Website or App that has access to your account. It is done using the myaccount.google.com console.
If you want to do this using Android, the easiest way is to:
Open your device's Settings app Settings app and then Google and then Google Account.
At the top, tap Security.
Under "Signing in to other sites," tap Signing in with Google.
Tap the name of your project.
Choose Remove access.
Through the web, you can go to Apps With Access to your Accounts:
Scroll down to the "Signing in with Google" section
Locate your project.
Select it, and choose "Remove access"
The name that is shown should be the name you've given to your project as part of the OAuth screen. If you haven't set that up (and if you're just playing around, you probably haven't), it will use the Project ID for your project. You can find this on the Cloud Console home screen attached to the same project name that you used in Dialogflow and the Action Console.
While you're in there, you will probably want to configure the OAuth screen to have a name for the app as it will be visible to users on the OAuth screen. From the menu, select "APIs & Services" and then "Credentials"
Select the "OAuth consent screen" tab, and fill in the "Application name".
This name should then be in the list of applications you have installed, and can remove.

How do you test Account Linking with Actions On Google with a separate test account prior to deployment?

I've built an Action using API.AI, and set it up with integration to Actions On Google. A webhook is used for fulfillment, together with account linking. I've followed the directions here to complete testing using my main google account that gives me access to the unpublished action in the web simulator and on my Google Home device that is set up with the same account.
Now it's time to deploy my Action. These instructions detail the process. One of the steps is to provide testing instructions for the Google reviewers that will approve the deployment. If you use account linking, it is necessary to provide them with test user credentials. Here is specifically what they request:
Provide any additional information needed to test your agent. If your agent requires account linking or login information, you must provide a username and password for a test account. Please make sure that any provided accounts are not real user accounts. This information will only be used by the review team, and will not be visible to users.
I've set up a test account for this purpose. I would obviously like to test my Action using the test account (instead of my main account) prior to submission for deployment. How do I do this?
If I use the web simulator and login with the test account, when I try and invoke the Action with my invocation name I get 'Sorry, this action is not available in simulation'.
When developing an Alexa Skill, Amazon provides for this as described here. While researching, I see references to similar provisions for Android developers with Google Play here. Where is the same thing for Actions On Google?
The test account is for the account linking step only.
To test your action in the simulator, you should be using the developer account you used to submit the action for review. The test account is used once your action is invoked and account linking is required to continue using your action.

Resources