[Instagram] AttributeError - 'InstagramGraphqlAPI' object has no attribute 'item'

[glottisfaun0000]

Installation

pip install gallery-dl in venv on macOS, python via homebrew. Same behavior with a brew install gallery-dl installation

Logs

instagram: An unexpected error occurred: AttributeError - 'InstagramGraphqlAPI' object has no attribute 'item'. Please run gallery-dl again with the --verbose flag, copy its output and report this issue on https://github.com/mikf/gallery-dl/issues .
instagram:
Traceback (most recent call last):
  File "/Users/{USER}/.venv/lib/python3.11/site-packages/gallery_dl/job.py", line 150, in run
    for msg in extractor:
  File "/Users/{USER}/.venv/lib/python3.11/site-packages/gallery_dl/extractor/instagram.py", line 65, in items
    for post in self.posts():
  File "/Users/{USER}/.venv/lib/python3.11/site-packages/gallery_dl/extractor/instagram.py", line 978, in _pagination
    s = "" if self.item.endswith("s") else "s"
              ^^^^^^^^^
AttributeError: 'InstagramGraphqlAPI' object has no attribute 'item'

Guessing this is another underlying python issue, but happens in a virtual environment

[mikf]

This is an error while reporting an error

gallery-dl/gallery_dl/extractor/instagram.py

Lines 993 to 996 in 279854c

	elif not data["edges"]:
	s = "" if self.item.endswith("s") else "s"
	raise exception.StopExtraction(
	"%s'%s posts are private", self.item, s)

and it only occurs for "api": "graphql", which doesn't appear to work anymore. All users are considered "private" since the API doesn't return any results anymore.

[glottisfaun0000]

So Instagram extractor 100% requires login now?

[mikf]

It should be possible to query the rest API a couple of times without login / cookies. At least it is for me with a residential IP.

[Hrxn]

So Instagram extractor 100% requires login now?

Yes, basically.

[fireattack]

Instagram Web still uses graphql, but at a glance they look drastically different than what gallery-dl is/was using? Like, I don't see any requests with query_hash param and they all seem to be POST now.

Theoretically we can rewrite the GraphQL API interface; whether it's worth it or not is an entirely different story, of course.

Should we leave this issue open for that, or just consider it not planned?

[fireattack]

Sorry for necroing again.

This seems can be trivially fixed by changing first parameter to 12:

gallery-dl/gallery_dl/extractor/instagram.py

Lines 930 to 933 in 831f922

	def user_feed(self, user_id):
	query_hash = "69cba40317214236af40e7efa697781d"
	variables = {"id": user_id, "first": 50}
	return self._pagination(query_hash, variables)

[mikf]

This seems can be trivially fixed by changing first parameter to 12:

Thanks for the hint. 24 seems to work as well, at least for now. (ff4e53a)

Should we leave this issue open for that, or just consider it not planned?

I think we should open a new issue for figuring out how exactly this new GraphQL interface works.

[xibr]

Maybe use doc_id instead of query_hash see

• Instagram reels fail to download yt-dlp/yt-dlp#11151
• yt-dlp/yt-dlp@95581b5