3 ms·
I've managed to work around this by changing the API host name from 'api.instagram.com' to 'www.instagram.com' for the Oauth authentication flow. Here's my for
by stefl 10y ago
I've managed to work around this by changing the API host name from 'api.instagram.com' to 'www.instagram.com' for the Oauth authentication flow.
Here's my fork for the omniauth-instagram Ruby gem, which is now allowing me to consistently log in: https://github.com/stefl/omniauth-instagram/blob/master/lib/omniauth/strategies/instagram.rb https://github.com/stefl/omniauth-instagram/blob/master/lib/...
- oblachniy 10y agoFor me it doesn't works. I changed from 'api.instagram.com' to 'www.instagram.com' for the Oauth - have one "302 redirect" back to my site with "error 400". Strange...
- imack 10y agoDitto here, it comes and it goes, but I can see this switch doesn't help our overall fail rate.
- stefl 10y agoOkay, thought I'd mention it because it's had such a significant effect for me. So that possibly means that in my case the Auth0 <-> Instagram connection is something to investigate further.