Thank you for submitting your Assistant app for review. Unfortunately, your app has been denied for the following:
1. If your Actions require account linking or login information, the credentials provided in your testing instructions must work as expected. At the moment, we are unable to successfully proceed with testing.
In this case, GSI account linking was not found during simulation.
can anyone can help me please ?
Related
If I enter both an ApplicationID and key into the Advanced Settings of the dnn.azureadb2cprovider I get a generic error with no explanation. I've gone through the setup documentation (which seems to be outdated) numerous times. The error gives no clue as to what the issue is.
If I enter only the app id or only key by itself, there is no error. Obviously this wont allow Graph to work, but I am noting it anyway.
Went thought the setup process located at https://github.com/intelequia/dnn.azureadb2cprovider#requirements. I can get users to sign in successfully through B2C so it's partially working. Just the advanced features are having trouble.
You can check the log4net log files under /Portals/_default/Logs folder for more details on the issue. This is probably caused by the permissions of the App registration on the Graph API. Ensure that you have set permissions on these Application scopes and have given consent to them (the documentation will be updated soon):
Application.Read.All
Group.Read.All
GroupMember.Read.All
User.Read.All
PS: in the future please create this type of issues on the GitHub repository to concentrate all the help and documentation on the same location.
mismatch redirect uri screen This is account linking screen. This is error image with actual error. How to link account through Google Actions?
(token generation process through google actions)
Generated Client Id & Client secret for Project but not able to construct the authoriztion URL in client information section of Account linking tab.
Account link process is not working as expected, showing error while enabling test in simulator (Error: We're sorry, but something went wrong. Please try again.)
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?
I've downloaded the starter pack and performed all steps as mentioned in the tutorial. I can create accounts but if I log out and want to sign in again I always get the error invalid username or password. Can anyone share any pointers as debugging this is nearly impossible.
I've created several accounts already just to be sure the password was ok.
I've created the keycontainers
I've created the two applications that are needed in the custom policies (web app and native)
I've updated the extension file with the correct id's
yeah if you dont get your client IDS correct you cant log in and then it constantly reports as invalid credentials.
Double check that you are writing the object ids correctly.
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.