Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    @MrSwitch Hi there, got a quick question, I'm using the //auth server on herokuapp.com, I've set up everything correctly, but about 90% of the time I get "http://localhost/index.html?proxy_url=http://auth-server.herokuapp.com/&state={" instead of the full url in the popup window. sometimes it works, like I had it working this morning, went for a coffee break (didn't change anything), tried it again, didn't work
    twitter is giving me a 401 - Unauthorized resonse
    with the response content: {"errors":[{"code":32,"message":"Could not authenticate you."}]}
    I'd appreciate any help here, thanks!
    Andrew Dodson
    @limelabsdesign please include the full response you got?
    @MrSwitch the response I get for hello('twitter').login(loginHandler); is: "{error: Object{code: "cancelled", message: "Login has been cancelled"}}"
    and the twitter requests has the response body as above: {"errors":[{"code":32,"message":"Could not authenticate you."}]}
    this sadly happens even if I use your code examples
    Has anybody tested this project against the latest version of hellojs and inappbrowser? The redirect page doesn't close for me for some reason... Everything else seems to be working fine. I can see all necessary stuff in the url of the redirect page after the oauth process happens. Using the same redirect page that ships with hellojs npm install...
    Andrew Dodson
    @rockneverdies55 that is a common complaint on iOS.