-
Notifications
You must be signed in to change notification settings - Fork 718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeyError: 'timeline'
crash on twitter-profile
scraper
#991
Comments
I have this error too File "/home/.venv/lib/python3.10/site-packages/snscrape/modules/twitter.py", line 1902, in get_items version: v0.7.0.20230622 |
KeyError: 'timeline'
crash on twitter-profile
scraper
I'm seeing the same thing on the web interface: the 'Replies' tab on profile pages is empty. This looks like a bug on Twitter's side. |
looks like the UserTweets api call works and has data returned, but UserTweetsAndReplies is busted on Twitters end.. call returns 200, but has no data in timeline_v2 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
Twitter has blocked every unregistered user from viewing tweets. Is this related? |
not related.. the UserTweets api endpoint is still returning data... UserTweetsAndReplies is still b0rk3d. |
Describe the bug
when I run:
it throws error:
How to reproduce
Expected behaviour
It was working until Thu Jun 29 21:35:07 UTC 2023.
Screenshots and recordings
No response
Operating system
ubuntu 16
Python version: output of
python3 --version
Python 3.10.6
snscrape version: output of
snscrape --version
snscrape 0.6.2.20230321.dev32+gb76f485
Scraper
witter-profile
How are you using snscrape?
CLI (
snscrape ...
as a command, e.g. in a terminal)Backtrace
No response
Log output
No response
Dump of locals
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: