I am trying to create Smart Home Test Google Action but when try to test it in Google Assistant app it redirects to 500 Error page.
I am following this Smart Washer example :
https://codelabs.developers.google.com/codelabs/smarthome-washer/#2
but not able to proceed to next step because of this 500 Error
Related
I'm using Expo webview for my react project.
But i got an Error when i turn off my phone an hour and my app was still on foreground.
Error message was like
Error loading page
Domain : undefined
Error Code : -2
Description: net::ERR_NAME_NOT_RESOLVED
I guess this error occurs because when user's access token expires, i reload the page to reconnect websocket.
Please help this stupid junior developer 😢
enter image description here
I tried to integrate pos with uber eats. I followed https://developer.uber.com/docs/riders/guides/authentication/user-access-token but getting error response as error.invalid_request . I entered UBER_CLIENTID, UBER_CLIENTSECRET
correctly and for 1 time it worked and show the login page but later on it showing the error error.invalid_request . I tried 3 different browsers and received same error.
this is the response image
I'm hacking away at a Facebook app on Heroku, using Node.js. When I go to the app myself, it works exactly as I expect. When I send another developer/tester to it, the standard Heroku "Application Error" message is displayed. When I check the logs, there isn't even a log that the developer made a GET request for the app page, let alone an error.
He tells me that the last thing he sees in his browser status bar is "waiting for .herokuapp.com", which implies that Facebook got to the app, but the logs don't support this theory.
Is there another method of seeing Heroku errors? Is there something I have to turn on in order to see more? A setting I have to modify to let this other guy use the app?
Update: Some more looking around led me to check the network traffic. He's getting a 503 Service Unavailable, followed by the error page. Still wondering why this happens on his machine, but not mine.
Update: Inserted some error-checking code into the handle_facebook_request method.
req.facebook.app(function(err, app) {
if(err !== null) {
var errorMessage = "Error getting app: " + util.inspect(err['error']);
console.log(errorMessage);
}
// rest of req.facebook.me, and rendering code
}
This gives me an "Unsupported get request", of type "GraphMethodException" and code 100. So now I have something I can look into! I wish that Heroku had at least mentioned that the request had been tried.
I had the same problem with a new facebook app created with the support heroku / node.js.
After several attempts and tests I saw that I get the message "Unsupported get request", type "GraphMethodException" and the code 100, because my facebook app was with sandbox mode.
When I disabled the sandbox my application on heroku it worked fine.
We followed the Facebook example code, shown here -- this works in our app -- if you click the anchor 'a' link, its onclick handler opens a new window and the facebook feed dialog appears:
<a class="fbShareToWall" onClick='window.open("https://www.facebook.com/dialog/feed?app_id=123050457758177
&link=https://developers.facebook.com/docs/reference/dialogs/
&picture=http://fbrell.com/f8.jpg
&name=Facebook%20Dialogs&caption=Reference%20Documentation
&description=Using%20Dialogs%20to%20interact%20with%20users.
&redirect_uri=http://www.example.com/response");'>Share on Facebook</a>
The above code works fine and displays the Facebook sample of the Feed dialog.
Here is our code - we get the error message:
"An error occurred with oursite.com. Please try again later.
API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: redirect_uri is not owned by the application.
NOTE: this is a beta site and we're running it on a staging server whose domain name is NOT the same as the domain name that "OUR_APP_ID" below is associated with:
<a class="fbShareToWall" onClick='window.open("https://www.facebook.com/dialog/feed?app_id="OUR_APP_ID"
&link=https://www.oursite.com&name=Please%20work
&caption=Just%20work
&description=Comeon%20work
&redirect_uri=http://www.oursite.com");'>Share on Facebook</a>
(note: our code has the numerical FB app_id, not "OUR_APP_ID")
"OUR_APP_ID" is 'connected' to our production server's domain name and we're kinda wondering if that's the problem.
EDIT: "we're kinda wondering if that's the problem" because the code above is on our staging website www.foo.com --
and our code above uses an app_Id that we connected to our production domain name 'www.oursite.com'.
We wonder if Facebook -- upon receiving the above request to display the Feed dialog -- is saying to itself
"okay this website www.foo.com is trying to display a Feed dialog -- but the app_id is for www.oursite.com --
so we're going to pop up a 191 error"
We tested that theory. We altered the sample FB feed dialog code at the top -- we changed some numbers in the sample code's app id.
And we get an error message now with the formerly working sample Feed dialog code but it is a completely different error message.
Any advice on this '191' redirect_uri error message?
the url format works fine with my app
https://www.facebook.com/dialog/feed?app_id=135669679827333&link=https://anotherfeed.com&name=testing&caption=Just%20testing&description=the%20test&redirect_uri=http://anotherfeed.com
check to make sure your app id is correct and that your redirecting to the domain that is set up in your app settings.
Has anyone encountered the following error message when sending to Twitter?
"Error: Incorrect signature"
And on the debug console:
<0xf14cf80 SHKTwitter.m:(356)> Twitter Send Status Error: {"request":"\/1\/statuses\/update.json","error":"Incorrect signature"}
So far as I can tell I've followed the install instructions on http://www.getsharekit.com/install/#download and it is working with Facebook, e-mail etc. just not Twitter.
It would be great if someone has seen this error before and goes "aha!".
All I did to enable twitter Sharing is:
Regitered my App as a Twitter APP (Application Type: Browser)
#define SHKTwitterConsumerKey #"My..."
#define SHKTwitterSecret #"My..."
#define SHKTwitterCallbackUrl #"http://www.anything.com/callback" // You need to set this if using OAuth, see note above (xAuth users can skip it)
\#define SHKTwitterUseXAuth 0 // To use xAuth, set to 1
\#define SHKTwitterUsername #"" // Enter your app's twitter account if you'dlike to ask the user to follow it when logging in. (Only for xAuth)
Note that for the callback function you can enter any URL you want. even www.google.com. Just make sure it is the same URL in your code.
The issue is that you're signed into your twitter account, and allowed the app to connect to your profile.
However, days go by, the Key and Secret change, and now you're seeing this error. It's because you have to log out and re-log back into Twitter. I spent waaay too much time finding this out when I created a new Twitter App to hook into (and organize my apps) and found this error.
Basically, ShareKit is saving your login info, auto-logging you in, and getting the error when twitter says the app doesn't have permission to connect to your profile.
Follow these steps to log yourself out and test again :
http://www.getsharekit.com/docs/#logout
Check this previous SO question, it might be able to help you solve the problem:
Twitter API status update always returns "Incorrect signature"