Non-json response to URLs incorrectly handled

[eric-wieser]

Got this traceback just now:

access_token=AAADrWXnFBRwBAOq2HxLgnNlD2ZC... [truncated from 56 chars for security]
^
SyntaxError: Unexpected token a
    at Object.parse (native)
    at EventEmitter.<anonymous> (/home/eric/nodejs/node_modules/faceplate/index.js)

From this line

For whatever reason, a graph URL is returning a non-JSON response fo a request to /me. I'm not sure if this is documented behaviour

[eric-wieser]

This is most likely caused by danwrong/restler#110

[otogen]

Hello, I am a node.js & express.js beginner
I got a similar error below today. The program is going to clash after that. It is very weired because I have never got this error before.
I am using Facebook-Template-Nodejs including Faceplate 0.0.4 , Restler 2.0.0, and b64url 1.0.3
I have tried npm install restler2.0.1, but could not get solution.

Please tell me the solution. Is it cause from graph API and JSON data?

Thank you for your thoughts !

undefined:1
SyntaxError:Failed to parse JSON body:Unexpected token o

SyntaxError: Unexpected token S
at Object.parse(native)
at EventEmitter.FaceplateSession.get(../node_modules/faceplate/index.js:121:25)
at EventEmitter.emit(events.js:99:17)
.
.
.

[eric-wieser]

@otogen: Did you read the comment I made 3 days ago? This is due to an unfixed bug in restler.

[otogen]

Totally yes

[Henddher]

I "was" experiencing this issue with Heroku and facebook.
I updated to faceplate 0.5.0, plus the latest changes from Eric Weiser and yet faceplate's req.facebook.app(...) failed as well as fql and get.
It is caused by JSON.parse "hanging" (never returns but an exception is thrown). I "resolved" the issue by calling JSON.stringify on the payload from restler before calling JSON.parse. It might be redundant but the issue appears to be caused by Facebook sending JSON payload with field names containing underscore characters?

Here is a sample of the change I made: (// <<<<<)
Does that make sense at all?

this.get = function(path, params, cb) {

if (cb === undefined) {

cb = params;

params = {};

}

if (self.token)

params.access_token = self.token;

try {

var request = restler.get('https://graph.facebook.com' + path,

{ query: params });

request.on('fail', function(data) {

var result = JSON.parse(JSON.stringify(data)); // <<<<<<<<<<

cb(result);

});

request.on('success', function(data) {

var result = JSON.parse(JSON.stringify(data)); // <<<<<<<<<<

cb(null, result);

});

} catch (err) {

cb(err);

}

};

[Henddher]

And with these 2 changes, login seems to work also:
(Are these changes correct?)

// not logged in or not authorized
if (!data.user_id) {
  cb(data); // <<<<<<<<
  return;
}

if (data.access_token || data.oauth_token) {
  cb(data); // <<<<<<<<<
  return;
}

It seems to me that the parse_signed_request function is not in synch (API-wise) with FaceplateSession "constructor" and the chain of callbacks from middleware. Maybe?

[otogen]

Thank you Henddher San ! I will check it soon and report you here soon !

[otogen]

Henddher San, I have just check the program and it works !
In my case, if faceplate would be upgraded to 0.5.0, then Facebook-template-nodejs does not work. But without change, your comments did work.

So great, thank you so much Henddher San !!!

• If you have also knowledge about what res.cookie(), req.session.cookies does not work in my case, appreciate it.

[Henddher]

Machunter (in another post danwrong/restler#114) confirmed the issue we are seeing: JSON.parse failing to parse the response. Thus, JSON.stringify followed by JSON.parse "solves" the problem.

Another strange thing is that adding JSON.stringify to the parse_signed_request function does NOT work. JSON.stringify seems to be "needed" for function get and fql only.

Can anyone knowledgable with Restler and Faceplate share some thoughts about the "solution" we are discussing?
("solution" between quotes because I do NOT know if it's correct - honestly, it makes no sense as solution)

I am no expert of neither Restler, Faceplate, nor Node as a matter of fact. The most strange thing, IMO, it's the fact that the issue started happening without changes to the code of the apps. So, either Facebook responses changed or Node & NPM versions used on Heroku changed (to a different version which exposes faceplate and restler issues? - Node 0.10?).

In my package.json, I had declared engines as follows:

"engines": {
"node": "0.8.x",
"npm": "1.1.x"
}

That declaration apparently allows newer versions of Node and NPM to be used if available. Now that I know which exact versions are being used, I modified my package.json as follows:

"engines": {
"node": "0.8.21",
"npm": "1.1.65"
}

However, I don't know if Heroku infrastructure honors specific versions either.

Can anyone share some light about JSON.parse?

I still think there's an issue with faceplate MASTER/HEAD and how "Errors" are created and passed onto FaceplateSession constructor when these errors arise during Restler and/or JSON.parse operations.

[eric-wieser]

I don't know which version of node made it actually break, but danwrong/restler#110 has been wrong forever - Every instance of a restler handler you create shares the same EventEmitter. Why I got my error:

1. create two requests (i.e., an auth request and an API request)
2. Add an event handler to each
3. When either completes both handlers fire - my API request handler recieves a non-json auth-token, and everything fails.

I'm not sure what you're seeing here, but this bug is fixed for me after applying danwrong/restler#113 and using faceplate/master.

[eric-wieser]

@Henddher:

(Are these changes correct?)

// not logged in or not authorized
if (!data.user_id) {
  cb(data); // <<<<<<<<
  return;
}

if (data.access_token || data.oauth_token) {
  cb(data); // <<<<<<<<<
  return;
}

Nope. All you're doing there is reverting the changes made to faceplate/0.5.0. These changes are sound - the problem is the other code, which I fixed in #22, #23, and #25. You'll need to update your API calls - 0.5.0 is an API-incompatible update.

[Henddher]

Thank you Eric.

How can I use Faceplate master and danwrong/restler#113

I am using Heroku but I do NOT know if Heroku honors node module versions specified in package.json

Anyone knows?

How could I specify these 2 different versions of Faceplate and Restler?

"dependencies": {
"express": "3.1.0",
"jade": "0.28.1",
"stylus": "0.32.0",
"faceplate": "0.5.0",
"async": "0.1.18",
"ejs": "0.4.3",
"restler": "2.0.0",
"b64url": "1.0.3",
"pg" : "0.6.15"
},

"engines": {
"node": "0.8.21",
"npm": "1.1.65"
}

[eric-wieser]

@Henddher: I can't comment - I haven't been testing with node 0.8.21.

Most likely, your problem is that 0.5.0 is a non-working release of faceplate, and the commits I made on top haven't been put into a 0.5.1 on npm. Until then, you could revert to 0.4.

[Henddher]

Thanks Eric.
The strange thing is that my code stopped working when I was still using faceplate 0.0.4.
Out of the blue, three apps started failing. Even older apps I had not touched in weeks are also failing now.

My package.json had 0.8.x and 1.1.x initially. I even tried node 0.8.21 and 0.8.19 and the app still fails with the same JSON.parse issue.

Either Heroku does not honor package.json versions of dependencies and/or engines or Facebook JSON responses changed somehow.

I can't think of any other possible explanation for the sudden breakage.

Only calling JSON.stringify before JSON.parse seems to successfully solve the issue.

Keep in mind that I tested creating a brand new Heroku app from Facebook developer site and this sample app ALSO fails exactly the same way as the others.

Are there any combination of versions (node, faceplate and restler) in which the issue does not happen?