-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
content-sync fails if cannot find profile #239
Labels
bug
Something isn't working
Comments
c240amg
changed the title
content-sync fails if user who (re)tweeted no longer exists
content-sync fails if cannot find profile
Nov 24, 2024
Adding debug mode shows this:
|
Hello, are you still having these issues? |
Hi, yes I am, I can send debug information if you need? let me know how to do that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Logging into twitter and bluesky works ok.
Once content-sync begins, content-sync hangs when profile is not found. Happening on multiple twitter accounts - syncs are hung and frozen with no progress.
This seems to be a bug as the tweets do have users that still exist on X.
Maybe it's trying to check with users that exist on bluesky?
I am not a dev so got no clue on how to fix this, or if it's an issue on my side
XRPCError: Profile not found
error: 'InvalidRequest',
Tweets seems to be this post: https://x.com/Feargal_Sharkey/status/1860606739474706632
I am syncing about 16 accounts, and about one third of them have this issue of 'profile not found'
To Reproduce
Steps to reproduce the behavior:
git pulled latest version
nvm --version 0.40.0
nvm version v22.11.0
node ./dist/index.js /data/env.usertosync
Expected behavior
content sync to complete
Screenshots
Additional supporting information
Also happening on another profile:
Tweet seems to be this post: https://x.com/BagnolRebecca/status/1855600240495038491
Another tweet: https://x.com/FlyANA_official/status/1853538045934366900
The text was updated successfully, but these errors were encountered: