Follower/following lists come back empty (query_hash GraphQL returns no edges)
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 72/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- api
调研方向
Start from getFollowersOrFollowingGenerator, which still calls graphql/query/?query_hash=37479f2b8209594dde7facb0d904896a (followers) and 58712303d941c6855d4e888c5f0cd22f (following). Read doesUserFollowMe, which already calls /api/v1/friendships/<userId>/followers/ with the x-ig-app-id header, and reuse that request plus next_max_id→max_id paging. Done when follower/following lists return non-empty edges while unfollowNonMutualFollowers, unfollowAllUnknown, unfollowOldFollowed and listManuallyFollowedUsers still iterate all pages — choose page size and pacing carefully to avoid human checkpoints.
由索引模型根据 Issue 内容生成。
描述
Follower/following lists come back empty (query_hash GraphQL returns no edges)
Version: 1.11.16 (macOS, arm64)
What happens
Since 1.11.16 the profile lookup works again (thanks for the GraphQL fix!), but the bot then finds nobody to follow. The follower list request for a target account returns the follower count, but an empty list and has_next_page: false:
{"data":{"user":{"edge_followed_by":{"count":6269,"page_info":{"has_next_page":false,"end_cursor":null},"edges":[]}}},"extensions":{"is_final":true},"status":"ok"}
So followUserFollowers finishes the target immediately without following anyone. No error is logged, so it looks like the bot is working.
Cause
getFollowersOrFollowingGenerator still uses the old graphql/query/?query_hash=... queries:
- followers:
37479f2b8209594dde7facb0d904896a - following:
58712303d941c6855d4e888c5f0cd22f
Instagram now answers both with "edges": []. The following query is used by unfollowNonMutualFollowers, unfollowAllUnknown, unfollowOldFollowed and listManuallyFollowedUsers, so those likely see an empty list too.
Possible fix
The Followers/Following dialog on instagram.com loads its lists from /api/v1/friendships/<userId>/followers/?count=12&search_surface=follow_list_page (and /following/?count=12), paginated with next_max_id → max_id. doesUserFollowMe already relies on that endpoint. Fetching it from the page with the x-ig-app-id header works in a local patch, but you probably know best what page size and pacing are safe here.
Possibly related
Our account got a "confirm you're human" checkpoint after a run that paged through a large following list via that endpoint (12 per page, a few seconds between pages, during unfollowOldFollowed). It may be unrelated, but it seems worth knowing before choosing page size and pacing.
- 主要语言
- TypeScript
- 星标
- 696
- 派生
- 103
- 平均合并
- 4 分钟
- 30 天内合并 PR
- 3
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
mifi/SimpleInstaBot 的其他 Issue
-
Bot does not run未关闭
难度 4/5 3-5 天 新手友好度 35/100
mifi/SimpleInstaBot#330 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
mifi/SimpleInstaBot#322 · 3 条评论 ·
-
难度 4/5 3-5 天 新手友好度 45/100
mifi/SimpleInstaBot#312 · 3 条评论 · 1 个 reaction ·
-
macOS Sequoia?未关闭
难度 3/5 1-2 天 新手友好度 35/100
mifi/SimpleInstaBot#310 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
mifi/SimpleInstaBot#305 · 7 条评论 ·
查看 mifi/SimpleInstaBot 的全部 Issue
相似的 Issue
-
area:editor bug issue-form:bug P0 platform:windows review: low
难度 2/5 1-3 小时 新手友好度 64/100
1lck/Lithe-IDEA#1388 ·
维护者通常 1 天内回复
-
fix(api): isToolAuditEnabled swallows database read errors on auditToolOperations without logging未关闭area: backend bug priority: low
难度 2/5 1-3 小时 新手友好度 82/100
snapotter-hq/SnapOtter#3238 ·
维护者通常 1 天内回复
-
rig up --plan times out after 5 s and reports an UNKNOWN outcome while the daemon completes the plan未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
modelcontextprotocol/servers#5216 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复