Received error message for "Bad Request"

Still having this issue?
Can you provide more info?
I cannot reproduce it.

This is a duplicate of #2380559: Handle request error user-friendly and is fixed in the dev branch.

I'm getting this and it's not related to the way the errors are handled. Instagram seems to not like the method used to make the request.

That other issue helps but these errors still persist.

1.x branch on this project may be a good idea too btw.

Dropping priority though since the other issue fix prevents total page meltdown.

Actually somehow my access token got busted, I had to regenerate a new one... it would be nice if the auth token generation was setup on the site requesting it instead of your personal site for security reasons.

it would be nice if the auth token generation was setup on the site requesting it instead of your personal site for security reasons.

Yes I do agree with that, however that requires every user of the module to do create their own Instagram Application to authenticate their token. (Because the site domain would need to be in the redirect_url). I wanted this module to be easily accessible for site builders who don't need to understand the rather confusing Application Dashboard that Instagram provides.

I will have a look into token expiration. I have a feeling that tokens have a limited lifecycle. Maybe there is something I can write to renew them automatically...

I like the intention behind avoiding the Application Dashboard oauth nonsense, but same goes for twitter. It would be nice to have both so you can cater to people who go through the effort or the ones that want to just get up and running without the hassle.

Token expiry would be a good check to help this bad request issue.