I have a scheduled job that runs every day to fetch the list of following and followers of my profile. I append the following at the end of URL (?__a=1) to fetch data. Since yesterday, I am getting this error in logs:

for (;;);{"__ar":1,"error":1357004,"errorSummary":"Sorry, something went wrong","errorDescription":"Please try closing and re-opening your browser window.","payload":null,"hsrp":{"hblp":{"consistency":{"rev":1005620371}}},"lid":"7104658052927816905"}

Did Instagram change its API configuration since June 1? Why am I getting this response and what should I do to fix this?

CodePudding user response：

It was working fine for me yesterday and I'm seeing the same json response as you. I noticed it still works on public profiles if you're signed out. The json tags are not the same though. Pretty annoying.

CodePudding user response：

I'm having the same problem. It started for me yesterday night. When I try _a=1 in a browser such as Chrome I get the same response intermittently even when I'm logged in. Like Eric said, it must be that some of the urls i've tested are on public accounts , but I haven't verified yet. Hopefully this won't be permanent.

CodePudding user response：

Seems like they've made some major internal changes this week. I had a script grabbing media urls off of the page source of posts but it seems they've completely changed the page source and the urls aren't there anymore. Tried using the __a=1 query and I'm getting the same thing as you guys. Seems like it always works properly when you're not logged in, e.g. if you're in incognito, until they start asking for login...

While I'm here, do you guys know the endpoint that that new chronological feed in the app uses? The one you see when you tap next to the Instagram logo and choose "following". I'm not rooted so I can't intercept traffic to check.

Thanks