I'm currently developing an action for Google Assistant using the Actions on Google simulator.
The action uses Google Sign-in to retrieve the users email. To test my flow for users who don't have have their account linked I would unlink using the unlink button in the profile section in the simulator
Today I tried to do this, but the console is giving me an error that unlinking was unsuccessful.
Sadly, this is the only information that I am getting. Refreshing the page and re-enabling testing on my project did not resolve this issue. Does anyone know what might be causing this or have an alternative way to unlink my account from my project?
I didn't understand your question correctly what you are asking. Correct me if am wrong your are asking about how to unlink the linked account with actions on google and for that you are phasing the problem right ??
for that may be https://myaccount.google.com/permissions this link would help to unlink the account which you have linked . Hope this solves the problem if not then please elaborate again the problem so i can understand properly .
Thank You.
I do not know why there may be an issue with the console, but the Google Account Linking page contains a list of every account you've linked.
So the issue of not being able to unlink my account in the simulator has resolved it self after a few days without any changes on my own side. So it might have been an issue on Google's side. The answer posted by Saif was a good work around while this issue wasn't solved yet.
Related
I created a DialogFlow app that works perfectly in my developer account.
But I need to test it as another user, so in my Google Action simulator, I added another test account as a OWNER to the project.
I verified this user has OWNER status in both the DialogFlow and Google Action UI.
They are able to edit both projects with full access.
However, when the test account tries to use the simulator it says:
Sorry, this action is not available for your app. Sorry, this action
is not available for your app. In the simulator, you are only able to
invoke actions that you have added to your app. For more information
on how to invoke your app, click here
https://developers.google.com/actions/discovery/explicit
This makes no sense to me:
I verified the test user has OWNER/ADMIN status on both DialogFlow and Google Actions for the project.
In DialogFlow, I verified the Google Assist is pointing to Default Welcome Intent as the default intent.
In Google Actions, I verified that the Default Welcome Intent is visible on the BUILD > ACTIONS UI.
As others suggested, I tried renaming the app several times with no luck.
I tried publishing an Alpha version, with still no luck.
My gut tells me it is some sort of permission/visibility problem, but I am completely stuck. Any ideas would be of great help.
EDIT:
THIS ISSUE HAS BEEN SOLVED. SEE COMMENT BELOW.
"I revisited my activity controls and noticed my "Web and App Activity" had a special clause due to organization permissions. I completely missed it due to the confusing UI. Posted a picture in the main thread. Thanks for reminding me to double check that area."
After you asked your company admin to enable this feature, it should be same as the image in below.
This error message is quite misleading. I have encountered this error a couple of times, and generally the problem was with one of the privacy settings in my Google account.
In this case you should go to https://myaccount.google.com/activitycontrols, confirm that you are logged in using your test account, and make sure the following are enabled:
Web & App Activity
Device Information
Voice & Audio Activity
Im trying to configure account kit. but the settings are not displayed, why is that ?, I have tried to log from 2 devices but still same screen.
That was a temporary issue and should be fixed now :)
Same is happening here. I've already tried to access it with different facebook accounts and with different projects, and nothing happened.
I'm also receiving errors in my recent registered apps, when tying to send the SMS. But it still works with the old ones.
This is so strange...
I implemented Google OAuth2 on Site A (I'm using Ruby on Rails), successfully adding localhost:3000/auth/google_oauth2/callback and sitea.herokuapp.com/auth/google_oauth2/callback to the redirect uri field in my Google Cloud Console.
Tried to do the same with Site B and... I can't set those darn redirect uris at all any more!
So I cheated a bit and used the Site A key and secret for Site B... and it all worked in localhost.
But when I finished in dev and tried to test in production by adding siteb.herokuapp.com/auth/google_oauth2/callback to that original Site A app... not only did it not get added, but the localhost and sitea uri's got deleted, and now I can't add those back.
Help, please? What might be happening, how do I test?
Thank you!
I've been having the same problem, I think it's an issue with Google Cloud Console.
I used the old user interface (https://code.google.com/apis/console) and it worked fine. Use this for the time being, it'll save you a lot of headache.
The redirect URI saving issue was a bug, and it should be fixed by now. Please leave a comment if you still encounter it. Thanks for reporting.
I have done much searching but not able to find a solution.
Trying to get my Twitter to Facebook feed setup but getting this error:
"Facebook reported an error. The error has been reported to our engineering team. Please try again as it might be a temporary problem"
From what I can gather it may have something to do with an old account that has been deleted, but I have no idea how to resolve this and nor do a lot of other people.
First up: this is not a programming question since it's not related to the Twitter API but to the Twitter interface. Therefore, it's actually to be regarded as "Off-Topic".
To give you a helping hand nevertheless:
What you are describing is a known bug Twitter bug. Check https://www.facebook.com/help/community/question/?id=110412992466716 and https://dev.twitter.com/issues/998
The problem comes up when your Twitter account was previously connected to another Facebook account that you deleted/deactivated without removing the Twitter app first. Now that you try to connect to a new Facebook account, Twitter still tries to authorize using the old credentials of that other account.
Currently, your only hope is to ask Twitter to manually remove the old account credentials from your Twitter profile's backend. From what I've been reading, Twitter frequently fails being cooperative in that point... you can only ask and hope someone at Twitter is able and willing to manually correct their bug.
I have experienced problem accessing my Application Profile Page.
It was actually happening since today.
When I create a new application, in my Basic setting > View App Profile Page
it's just redirect to my website.
It also happening if I go to http://www.facebook.com/apps/application.php?id=228671190534769
However if I open another app (that is I have created before today). It works well
Anyone experiencing the same? Please help!
Yes... I am getting the same thing!!
Because of this error, I have raised a support ticket on Facebook Developers Support section. You can find this here: http://developers.facebook.com/bugs/208861915856389?browse=search_4ed6ed7d7170d5114488507
If this matches your experience, please ensure you click YES on the "Does this repro describe your issue?" at the bottom!