instagram_private_api icon indicating copy to clipboard operation
instagram_private_api copied to clipboard

Expecting value: line 1 column 1 (char 0) occurs by web api

Open zahra-ash0uri opened this issue 5 years ago • 6 comments

As I use web client without login authentication, I faced to this exception while using endpoints such as media_comments and user_info:

Expecting value: line 1 column 1 (char 0) 

First I guessed it may caused by python request library, or something about network issues so I tried to be more polite and slow in sending requests, but it did not work. Any idea to get rid of that or where it originates?

zahra-ash0uri avatar Mar 31 '20 21:03 zahra-ash0uri

500/502 error? I get those sometimes when getting checking story reels, but they seem to be temporary. Although I'm use the private api so maybe your issue is unrelated.

wlerin avatar Apr 01 '20 19:04 wlerin

500/502 error? I get those sometimes when getting checking story reels, but they seem to be temporary. Although I'm use the private api so maybe your issue is unrelated.

Yes, it's almost temporary but not about user_info! I get this error for every user_info request.

PS: As i don't use login credential and the proxy is getting user_info responses elsewhere, it may have concurrent requests while using this endpoint.

zahra-ash0uri avatar Apr 02 '20 08:04 zahra-ash0uri

@zahra-ash0uri I have same problems. Do you have a solution?

thanhnguyen1121 avatar Jun 09 '20 11:06 thanhnguyen1121

Similar problem as https://github.com/ping/instagram_private_api/issues/266, frontend is using /<username>/?__a=1 with login required instead of /graphql/query/. Any solution?

hyper750 avatar Jun 12 '20 08:06 hyper750

Similar problem as #266, frontend is using /<username>/?__a=1 with login required instead of /graphql/query/. Any solution?

What I understood up to now is that our problem solves with Graph api, I mean /graphql/query/?{query_hash}blah-blah. I couldn't find the specific query_hash which is used by endpoint user_info. PS: Apparently every endpoint has it's own query_hash.

zahra-ash0uri avatar Jun 21 '20 08:06 zahra-ash0uri

Similar problem as #266, frontend is using /<username>/?__a=1 with login required instead of /graphql/query/. Any solution?

What I understood up to now is that our problem solves with Graph api, I mean /graphql/query/?{query_hash}blah-blah. I couldn't find the specific query_hash which is used by endpoint user_info. PS: Apparently every endpoint has its own query_hash.

This problem still exists Do you have a solution to solve this @zahra-ash0uri?

EsmaeiliSina avatar Dec 12 '20 08:12 EsmaeiliSina