Twitter oAuth Callback triggers exception

[sreuter]

My first guess was that i forgot about the express session middleware but it's setup and working (req.session exists)...

starting step - getRequestToken
...finished step
starting step - storeRequestToken
...finished step
starting step - redirectToProviderAuth
...finished step
starting step - extractTokenAndVerifier
...finished step
starting step - getSession
...finished step
starting step - rememberTokenSecret

node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Step rememberTokenSecret of twitter is promising: requestTokenSecret ; however, the step returns nothing. Fix the step by returning the expected values OR by returning a Promise that promises said values.

[bnoguchi]

Can you copy/paste a gist, so I can re-create this error?

[pgte]

I also have this problem. Trying to figure it out...

[bnoguchi]

gist please? Also, let me know if this error occurs in example/ which works without errors on my machine.

[pgte]

I think I know what it is in my case, it's my fault, sorry.
I have dev.mydomain.com setup in the twitter app, but I was starting out with localhost and then being redirected back to dev.mydomain.com (which points to localhost). Obviously the session didn't work because of that.
Thanks!

[bnoguchi]

@sreuter's gist is here. In his case, commenting out gzip.gzip() eliminates the exception. For more details, please see the following connect-gzip issue.