Oauth version giving me an issue

[arichards4814]

So I got my Oauth working locally by downgrading it like so (see below)

oauth2 (1.4.4)
faraday (>= 0.8, < 2.0)
jwt (>= 1.0, < 3.0)
multi_json (> 1.3)
multi_xml (> 0.5)
rack (>= 1.2, < 3)
omniauth (1.9.0)
hashie (>= 3.4.6, < 3.7.0)
rack (>= 1.6.2, < 3)
omniauth-oauth2 (1.3.1)
oauth2 (> 1.1)
omniauth (> 1.2)

That's the only way it works. However when I deploy to Heroku it is trying to bundle install on its own and it is getting the latest gem. Can anyone help with this. If I don't do this I get an invalid_redirect URI. Which is not true the paths are the same.

[arichards4814]

To be more specific I am sending my user to be authorized. When they come back it is giving an incorrect URI. If I downgrade my omniauth it lets it through. Great for my local machine. But when I'm trying to push up to heroku it is giving an error because it doesn't take the gemfile lock as is.

[EagleOne33]

I've had exactly the same problem.
What is very strange is that somehow, I managed to make it work at least once. I saved the response in a json and using it since then.
For heroku in the end that's what I do:

• I downgraded like you did, got the response and saved the hash in a json file
• I load the authentification from this json file and that's what I'm using on heroku

I'm not sure it's a good trick but for now it's ok...

I wonder why we have this problem; I guess others don't ... No idea

[EagleOne33]

Solved with this post:
#87 (comment)