Instagram API OGuth and Endpoints update 04-30-2015

After the big Instagram API, many instagram based apps started getting access_token errors for all users trying to login (tried to create a new instagram client - didn't work) I am using Thiago Locatelli and Lorensius W. LT android-instagram-omniauth https: //github.com/thiagolocatelli/android-instagram-oauth

according to their code i am getting this error "Failed to get access token"

Here is the code:

    static int WHAT_FINALIZE = 0;
    static int WHAT_ERROR = 1;
    private static int WHAT_FETCH_INFO = 2;

...    

    private Handler mHandler = new Handler() {
    @Override
    public void handleMessage(Message msg) {
        if (msg.what == WHAT_ERROR) {
            mProgress.dismiss();
            if (msg.arg1 == 1) {
                mListener.onFail("Failed to get access token");
            } else if (msg.arg1 == 2) {
                mListener.onFail("Failed to get user information");
            }
        } else if (msg.what == WHAT_FETCH_INFO) {
            // fetchUserName();
            mProgress.dismiss();
            mListener.onSuccess();
        }
    }
};

      

        
        
        
      

    

I think it might be the same problem as here: Instagram oAuth return "No matching code found" on the same server

UPDATE . This problem can be fixed by changing your server IP, but there is not enough information on how to set up the Instagram app. It has "Enforce signed requests" or "Disable implicit OAuth" etc.)

Does the WEBSITE_URL parameter in the Instagram instagram client app indicate your server IP?

By the way, now when you try to save the settings of the instagram client app, you get the message "Sorry, there was an error processing this request" which should mean some internal changes are being made right now ...

Thank you, comrades!

solved :

The problem was solved by changing my local IP (I contacted my IS provider and changed the IP to a different one). Instagram probably blocked my previous shared IP for a lot of requests, so switching to the new one worked for me. Try to connect from a mobile network (or any other network other than yours), if there is no error - you need to change your local ip. If the error persists, your server IP address may be the cause.