fix for user info (user info gql) #1868

SaeidB · 2024-04-09T19:12:39Z

__a=1&__d=dis no longer work , replaced with web_profile_info

claell · 2024-04-10T10:39:12Z

While you probably found the correct workaround, this doesn't seem to be compatible with the already existing methods and setup of instagrapi.

@subzeroid (or @tajbowness), as this is a rather important problem, do you possibly have the time to look into fixing this, based on this PR? The solution itself looks pretty easy and just needs to be fit into the existing code base.

SaeidB · 2024-04-10T10:52:49Z

While you probably found the correct workaround, this doesn't seem to be compatible with the already existing methods and setup of instagrapi.

@subzeroid (or @tajbowness), as this is a rather important problem, do you possibly have the time to look into fixing this, based on this PR? The solution itself looks pretty easy and just needs to be fit into the existing code base.

What do you mean ? Did you try and got any error ? I tried it and worked for me without any problem, the native public request of Instagrapi uses __a=1 and i bring plane requests to this part to fix it, you can use "extract_gql..." or not, i comment that line, if you use commented line, the result is exactly the same as before, you can easily get user info without need of login

claell

I reviewed your code to highlight the current problems.

Of course, I am sure that it works right now. It is just not fitting the project structure and thus creating new issues and maintainability problems if it's merged like this.

Let me know if you need more help with refactoring your code.

instagrapi/mixins/user.py

claell · 2024-04-10T10:56:43Z

instagrapi/mixins/user.py

@@ -141,7 +141,10 @@ def user_info_by_username_gql(self, username: str) -> User:
            An object of User type
        """
        username = str(username).lower()
-        return extract_user_gql(self.public_a1_request(f"/{username!s}/")["user"])
+        headers = {'Host': 'www.instagram.com','X-Requested-With': 'XMLHttpRequest','Sec-Ch-Prefers-Color-Scheme': 'dark','Sec-Ch-Ua-Platform': '"Linux"','X-Ig-App-Id': '936619743392459','Sec-Ch-Ua-Model': '""','Sec-Ch-Ua-Mobile': '?0','User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6261.112 Safari/537.36','Accept': '*/*','X-Asbd-Id': '129477','Sec-Fetch-Site': 'same-origin','Sec-Fetch-Mode': 'cors','Sec-Fetch-Dest': 'empty','Referer': 'https://www.instagram.com/','Accept-Language': 'en-US,en;q=0.9','Priority': 'u=1, i'}


Why do you set up new headers here? Please use the existing methods. Otherwise, the user cannot set its own headers.

the new endpoint for user info need some new headers and user-agent and the old headers wont work , this is the reason i put headers directly , and instagrapi users wont need to change headers in gql requests like this request , so the better idea is to use headers directly in endpoints like this , understood ?

Mh. But just giving new headers hard coded is not a clean way to go in that case, either. This might also result in Instagram banning clients, if they see requests with different user agents from the same IP.

So, how do the new headers differ from the old expected ones? Can they somehow get translated into each other? Or be set explicitly somewhere, like the old headers?

as i said this is a public request (gql , or non auth request) , and the headers are same everytime you send request , even the current model uses same headers everytime (for public request) ( monitor the instagrapi requests so you can see ) , so instagram will not ban you ,

No, if I set a different user agent, this won't get used for this request. Also, and I repeat, hardcoding the header here is the wrong place.

I am happy to assist you with improving the code quality. But I hope, you can understand why this is not good coding style.

check the instagrapi gql requests , the headers are same everytime , it uses its own user agent , not logged-in client user agent (mobile), not base_headers , if you use another user agent for this request , it will return you "mismatch user agent error etc"

instagrapi/mixins/user.py

remove commented line

SaeidB · 2024-04-10T11:12:46Z

the new endpoint for user info need some new headers and user-agent and the old headers wont work , this is the reason i put headers directly , and instagrapi users wont need to change headers in gql requests like this request , so the better idea is to use headers directly in endpoints like this , understood ?

commented line has been removed. thank you !

claell · 2024-04-10T11:32:27Z

I hope, you understand my points. Hardcoding values like this and not relying on existing functions is in general a bad practice (maintainability, generalizability, ...).

I got it that the endpoint probably requires different requests, so in that case, probably the way to go is to generalize the existing functions for the new use cases.

SaeidB · 2024-04-10T11:41:14Z

I hope, you understand my points. Hardcoding values like this and not relying on existing functions is in general a bad practice (maintainability, generalizability, ...).

I got it that the endpoint probably requires different requests, so in that case, probably the way to go is to generalize the existing functions for the new use cases.

as i said this is a public request (gql , or non auth request) , and the headers are same everytime you send request , even the current model uses same headers everytime (for public request) ( monitor the instagrapi requests so you can see ) , so instagram will not ban you , rotating headers is for private request ( authenticated requests , my pr is for non authenticated request for user info ) , now do you understand ?

claell · 2024-04-10T11:49:31Z

Here, you can see the current setup:

instagrapi/instagrapi/mixins/public.py

Line 209 in b83a00b

def public_a1_request(self, endpoint, data=None, params=None, headers=None):

. You can possibly also create a new function there (if needed) and then rely on that one. Please note that there is also already a function for public requests:

instagrapi/instagrapi/mixins/public.py

Line 77 in b83a00b

def public_request(

.

SaeidB · 2024-04-10T11:51:59Z

Here, you can see the current setup:

instagrapi/instagrapi/mixins/public.py

Line 209 in b83a00b

def public_a1_request(self, endpoint, data=None, params=None, headers=None):

. You can possibly also create a new function there (if needed) and then rely on that one. Please note that there is also already a function for public requests:

instagrapi/instagrapi/mixins/public.py

Line 77 in b83a00b

def public_request(

.

this is for __a=1 , they removed that

SaeidB · 2024-04-10T11:53:16Z

check the instagrapi gql requests , the headers are same everytime , it uses its own user agent , not logged-in client user agent (mobile), not base_headers , if you use another user agent for this request , it will return you "mismatch user agent error etc"

claell · 2024-04-10T11:57:10Z

My main argument stands. Hard coding this like you did is not good practice. Also, there is no error handling for the request.

The already existing functions provide that already. So, I hope, you can find a way how to rely on them (or refactoring them appropriately). I will be of help, if needed.

claell · 2024-04-10T12:03:28Z

I meant hard coding like you did. You hard coded this in the wrong place, where it can't be reused. There is no error handling, no reliance on good, already existing functions.

SaeidB · 2024-04-10T12:04:20Z

My main argument stands. Hard coding this like you did is not good practice. Also, there is no error handling for the request.

The already existing functions provide that already. So, I hope, you can find a way how to rely on them (or refactoring them appropriately). I will be of help, if needed.

you can see hard-coded by the author in the link below, no problem in public request to hard-code headers

instagrapi/instagrapi/mixins/public.py

Line 69 in b83a00b

"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 "

thats why i told you to check instagrapi public requests in mitm

thank you for your contribution

claell · 2024-04-10T12:05:46Z

(You can also edit GitHub comments, no need to delete and send a new one)

instagrapi/mixins/user.py

SaeidB

thats not personalized , its app id

SaeidB · 2024-04-10T11:48:34Z

instagrapi/mixins/user.py

@@ -141,7 +141,10 @@ def user_info_by_username_gql(self, username: str) -> User:
            An object of User type
        """
        username = str(username).lower()
-        return extract_user_gql(self.public_a1_request(f"/{username!s}/")["user"])
+        headers = {'Host': 'www.instagram.com','X-Requested-With': 'XMLHttpRequest','Sec-Ch-Prefers-Color-Scheme': 'dark','Sec-Ch-Ua-Platform': '"Linux"','X-Ig-App-Id': '936619743392459','Sec-Ch-Ua-Model': '""','Sec-Ch-Ua-Mobile': '?0','User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6261.112 Safari/537.36','Accept': '*/*','X-Asbd-Id': '129477','Sec-Fetch-Site': 'same-origin','Sec-Fetch-Mode': 'cors','Sec-Fetch-Dest': 'empty','Referer': 'https://www.instagram.com/','Accept-Language': 'en-US,en;q=0.9','Priority': 'u=1, i'}


check the instagrapi gql requests , the headers are same everytime , it uses its own user agent , not logged-in client user agent (mobile), not base_headers , if you use another user agent for this request , it will return you "mismatch user agent error etc"

instagrapi/mixins/user.py

claell · 2024-04-11T08:28:14Z

Here, you can see some part of the already existing request error handling code:

https://github.com/subzeroid/instagrapi/blob/b83a00b6d5c23029d9ab22b573ef26ebc79ef262/instagrapi/mixins/public.py#L190C1-L202C54

So I hope this helps you understand, why it is important to rely on existing functions and why just using requests like you did is not error prone.

SaeidB · 2024-04-11T09:39:00Z

the current code which i wrote in my pr will work , however if you mean adding error handling , you can do it by this :

return extract_user_gql(json.loads(cl.public_request(f'https://www.instagram.com/api/v1/users/web_profile_info/?username={username}', headers=headers))['data']['user'])

but the custom headers still needed

added self.public_request for better error handling.

claell · 2024-04-11T16:01:09Z

Already better. But still needs some more refactoring, from my perspective.

One possible problem now is this line:

https://github.com/subzeroid/instagrapi/blob/b83a00b6d5c23029d9ab22b573ef26ebc79ef262/instagrapi/mixins/public.py#L130C13-L130C48

Not sure, but probably we don't want to update the internal headers with the ones that are only used for that request?

Additionally, probably some more refactoring is sensible (like moving the custom headers to a different place. Defining them here like you do is not really sensible, as it won't allow any other functions to make use of them.).

SaeidB · 2024-04-11T16:08:12Z

Not sure, but probably we don't want to update the internal headers with the ones that are only used for that request?\n\nAdditionally, probably some more refactoring is sensible (like moving the custom headers to a different place. Defining them here like you do is not really sensible, as it won't allow any other functions to make use of them.).

Correct we don't need to use these headers on the other methods so make sense to pass them directly to the self.public_request instead of update the headers

claell · 2024-04-12T09:16:24Z

Try to have a look at my referenced line again. It shows that if headers are passed to public_request, the headers will then get updated (which is not wanted). So that needs to be slightly refactored, probably.

SaeidB · 2024-04-12T10:25:12Z

Try to have a look at my referenced line again. It shows that if headers are passed to public_request, the headers will then get updated (which is not wanted). So that needs to be slightly refactored, probably.

yeah i got you ,

default_public_headers = self.public.headers
temporary_public_headers = {'Host': 'www.instagram.com','X-Requested-With': 'XMLHttpRequest','Sec-Ch-Prefers-Color-Scheme': 'dark','Sec-Ch-Ua-Platform': '"Linux"','X-Ig-App-Id': '936619743392459','Sec-Ch-Ua-Model': '""','Sec-Ch-Ua-Mobile': '?0','User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6261.112 Safari/537.36','Accept': '*/*','X-Asbd-Id': '129477','Sec-Fetch-Site': 'same-origin','Sec-Fetch-Mode': 'cors','Sec-Fetch-Dest': 'empty','Referer': 'https://www.instagram.com/','Accept-Language': 'en-US,en;q=0.9','Priority': 'u=1, i'}
data = extract_user_gql(json.loads(self.public_request(f'https://www.instagram.com/api/v1/users/web_profile_info/?username={username}', headers=temporary_public_headers))['data']['user'])
self.public.headers.update(default_public_headers)
return data

claell · 2024-04-12T10:54:16Z

Your solution fixes the problem, but I think, there is a better way:

Refactoring some functions in public.py.

Why? Because I am rather confident that the headers will be needed for other calls as well in the future. So one possible suggestion would be adding another function similar to public_a1_request in public.py.

That function will have the headers (there, they can probably be hardcoded, then), and it will call public_request in a similar manner, as you showed in your code.

I suggest though, to also refactor public_request and _send_public_request with an additional parameter update_headers=True. Then, you can set this parameter to False in your calls and that will prevent updating the headers in the first place (which seems to be cleaner, compared to setting them first and then reversing that afterwards).

This was kind of what I had in mind all along, and I thought, it was rather obvious, but apparently, my suggestions weren't clear to you, before.

What do you think?

user info gql fix + implemented in public_request + avoid headers to be updated

SaeidB · 2024-04-12T12:47:58Z

check the changes i made now , i added update_headers=False and i think everything is good now and enough for this step

user info gql fix + implemented in public_request + avoid headers to be updated

claell · 2024-04-16T13:02:05Z

Thanks, some more nitpicks, though.

instagrapi/mixins/public.py

instagrapi/mixins/user.py

claell · 2024-04-23T17:18:09Z

@subzeroid, can you give a review and possibly make some calls on discussed topics?

marek-knappe · 2024-05-01T23:11:17Z

Just add one thing, hardcoding user-agent can lead to auto-detection of the bot on the Instagram-side so I would recommend actually making it exactly the same globally for every request or at least being able to set it as a config variable.
Also having that variable (temporary_public_headers) globally available (instead of having it in the user scope) would help if we will have any other request that will need to use it - but that can be tomorrow's problem :)

SaeidB · 2024-05-02T05:26:24Z

Just add one thing, hardcoding user-agent can lead to auto-detection of the bot on the Instagram-side so I would recommend actually making it exactly the same globally for every request or at least being able to set it as a config variable.
Also having that variable (temporary_public_headers) globally available (instead of having it in the user scope) would help if we will have any other request that will need to use it - but that can be tomorrow's problem :)

Hi, thx for your attention
Actually user agent will not be detected .

marek-knappe · 2024-05-07T01:15:15Z

@SaeidB

Traceback (most recent call last):
  File "/Users/mknappe/Projects/inst/instagrapi/test.py", line 2, in <module>
    from instagrapi import Client
  File "/Users/mknappe/Projects/inst/instagrapi/instagrapi/__init__.py", line 31, in <module>
    from instagrapi.mixins.public import (
  File "/Users/mknappe/Projects/inst/instagrapi/instagrapi/mixins/public.py", line 83
    update_headers=None
                   ^^^^
SyntaxError: invalid syntax. Perhaps you forgot a comma?

Forgotten comma on that line.

also:

name 'json' is not defined
Traceback (most recent call last):
  File "/Users/mknappe/Projects/inst/instagrapi/instagrapi/mixins/user.py", line 194, in user_info_by_username
    user = self.user_info_by_username_gql(username)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/mknappe/Projects/inst/instagrapi/instagrapi/mixins/user.py", line 146, in user_info_by_username_gql
    data = extract_user_gql(json.loads(self.public_request(f'https://www.instagram.com/api/v1/users/web_profile_info/?username={username}', headers=temporary_public_headers))['data']['user'], update_headers=update_headers)
                            ^^^^
NameError: name 'json' is not defined

No Json imported for json.loads

Also:

TypeError: extract_user_gql() got an unexpected keyword argument 'update_headers'

Looks like user.py:147 has a update_headers after () from public request

fix missing comma

import json

SaeidB · 2024-05-07T06:41:56Z

@SaeidB

Traceback (most recent call last):
  File "/Users/mknappe/Projects/inst/instagrapi/test.py", line 2, in <module>
    from instagrapi import Client
  File "/Users/mknappe/Projects/inst/instagrapi/instagrapi/__init__.py", line 31, in <module>
    from instagrapi.mixins.public import (
  File "/Users/mknappe/Projects/inst/instagrapi/instagrapi/mixins/public.py", line 83
    update_headers=None
                   ^^^^
SyntaxError: invalid syntax. Perhaps you forgot a comma?

Forgotten comma on that line.

also:

name 'json' is not defined
Traceback (most recent call last):
  File "/Users/mknappe/Projects/inst/instagrapi/instagrapi/mixins/user.py", line 194, in user_info_by_username
    user = self.user_info_by_username_gql(username)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/mknappe/Projects/inst/instagrapi/instagrapi/mixins/user.py", line 146, in user_info_by_username_gql
    data = extract_user_gql(json.loads(self.public_request(f'https://www.instagram.com/api/v1/users/web_profile_info/?username={username}', headers=temporary_public_headers))['data']['user'], update_headers=update_headers)
                            ^^^^
NameError: name 'json' is not defined

No Json imported for json.loads

Also:

TypeError: extract_user_gql() got an unexpected keyword argument 'update_headers'

Looks like user.py:147 has a update_headers after () from public request

hi, thanks for the mentioning
the missing comma and missing json import has been fixed , for the last issue (unexpected keyword) i think you forgot to update public.py , can you update user.py and public.py and try again ?

marek-knappe · 2024-05-07T07:29:34Z

@SaeidB Works now, thanks, also I see that there are some conflicts so you need to resolve it before anyone will merge it

ChristianJohnston97 · 2024-07-18T12:27:23Z

Will this fix be merged soon?

SaeidB · 2024-08-01T11:28:52Z

Will this fix be merged soon?

hello, i dunno really, but it works and you can add this to your lib even if it didn't merge

chrisbuetti · 2024-08-15T14:02:57Z

The prior pull request still has an issue but this will work: #2003

Brandon-Huu · 2024-09-08T00:14:19Z

Will this fix be merged soon?

hello, i dunno really, but it works and you can add this to your lib even if it didn't merge

how would I add this to my lib?

SwallowData · 2024-11-11T07:01:13Z

Can it still be used now?

SaeidB · 2024-11-11T17:20:33Z

Can it still be used now?

hi, yes

WarlaxZ · 2024-12-10T15:08:59Z

The only actual additional header you need is X-Ig-App-Id: 936619743392459

edit:
sorry due to how the public is set up originally, actually also needs: "Accept": "application/json"

WarlaxZ · 2024-12-10T15:48:40Z

This will get it working, however I've glossed over 2 fields that may be needed by other things

public_response = self.cl.public_request(f'https://www.instagram.com/api/v1/users/web_profile_info/?username={username}', headers={
    'X-Ig-App-Id': '936619743392459',
    "Accept": "application/json",
})
data_json = json.loads(public_response)['data']['user']
data_json["pinned_channels_info"] = {"pinned_channels_list": []}
for link in data_json["bio_links"]
    link["link_id"] = "set_me"
data = extract_user_gql(data_json)
return data

Update user.py

c9c0d11

__a=1&__d=dis no longer work , replaced with web_profile_info

SaeidB mentioned this pull request Apr 9, 2024

[BUG] Status 201: JSONDecodeError in public_request (url=https://www.instagram.com/nike/?__a=1&__d=dis) >>> #1802

Closed

claell suggested changes Apr 10, 2024

View reviewed changes

Update user.py

fe59f3e

remove commented line

Update user.py

e139fbf

claell reviewed Apr 10, 2024

View reviewed changes

instagrapi/mixins/user.py Outdated Show resolved Hide resolved

SaeidB commented Apr 10, 2024

View reviewed changes

Update user.py

738f059

added self.public_request for better error handling.

SaeidB added 2 commits April 12, 2024 16:10

Update user.py

dd085e7

user info gql fix + implemented in public_request + avoid headers to be updated

Update public.py

a0f93ec

user info gql fix + implemented in public_request + avoid headers to be updated

SaeidB added 2 commits April 12, 2024 16:19

Update user.py

d2d9aa1

user info gql fix + implemented in public_request + avoid headers to be updated

Update user.py

7c329b5

SaeidB requested a review from claell April 15, 2024 12:19

claell suggested changes Apr 16, 2024

View reviewed changes

instagrapi/mixins/public.py Show resolved Hide resolved

instagrapi/mixins/public.py Show resolved Hide resolved

instagrapi/mixins/user.py Show resolved Hide resolved

instagrapi/mixins/user.py Show resolved Hide resolved

SaeidB added 2 commits May 7, 2024 09:58

Update public.py

faf875d

fix missing comma

Update user.py

c424cf1

import json

Merge branch 'master' into master

b2e4dd3

SaeidB mentioned this pull request May 7, 2024

Public method for user_info_by_username_gql throws a simplejson.errors.JSONDecodeError[BUG] #1889

Open

sg-siddhant approved these changes Sep 14, 2024

View reviewed changes

fix for user info (user info gql) #1868

Are you sure you want to change the base?

fix for user info (user info gql) #1868

Conversation

SaeidB commented Apr 9, 2024

claell commented Apr 10, 2024

SaeidB commented Apr 10, 2024

claell left a comment

Choose a reason for hiding this comment

claell Apr 10, 2024

Choose a reason for hiding this comment

SaeidB Apr 10, 2024

Choose a reason for hiding this comment

claell Apr 10, 2024 • edited Loading

Choose a reason for hiding this comment

SaeidB Apr 10, 2024

Choose a reason for hiding this comment

claell Apr 10, 2024

Choose a reason for hiding this comment

SaeidB Apr 10, 2024

Choose a reason for hiding this comment

SaeidB commented Apr 10, 2024 • edited Loading

claell commented Apr 10, 2024

SaeidB commented Apr 10, 2024

claell commented Apr 10, 2024

SaeidB commented Apr 10, 2024

SaeidB commented Apr 10, 2024

claell commented Apr 10, 2024

claell commented Apr 10, 2024

SaeidB commented Apr 10, 2024

claell commented Apr 10, 2024

SaeidB left a comment

Choose a reason for hiding this comment

SaeidB Apr 10, 2024

Choose a reason for hiding this comment

claell commented Apr 11, 2024

SaeidB commented Apr 11, 2024

claell commented Apr 11, 2024

SaeidB commented Apr 11, 2024

claell commented Apr 12, 2024

SaeidB commented Apr 12, 2024

claell commented Apr 12, 2024

SaeidB commented Apr 12, 2024

claell commented Apr 16, 2024

claell commented Apr 23, 2024

marek-knappe commented May 1, 2024

SaeidB commented May 2, 2024

marek-knappe commented May 7, 2024 • edited Loading

SaeidB commented May 7, 2024

marek-knappe commented May 7, 2024

ChristianJohnston97 commented Jul 18, 2024

SaeidB commented Aug 1, 2024

chrisbuetti commented Aug 15, 2024

Brandon-Huu commented Sep 8, 2024

SwallowData commented Nov 11, 2024

SaeidB commented Nov 11, 2024

WarlaxZ commented Dec 10, 2024 • edited Loading

WarlaxZ commented Dec 10, 2024

claell Apr 10, 2024 •

edited

Loading

SaeidB commented Apr 10, 2024 •

edited

Loading

marek-knappe commented May 7, 2024 •

edited

Loading

WarlaxZ commented Dec 10, 2024 •

edited

Loading