Open crealol opened 3 weeks ago
Okay I'm checking
It's a strange issue indeed. I checked the response and the response says OK. Twitter is even returning an ID allocated to the retweet, but when cross-referenced, no retweet with that ID exists. I'll investigate it further and keep you updated.
@crealol For reasons unknown, it's working again now. I think it was an issue from Twitter's side. Let me know if it works for you too.
I'm suffering same issue for few days back for sending and reply tweet.
@gratatouilley I tried it approximately 6 hrs back from now, and then, it didn't work, although the raw response confirmed that it did retweet and also provided a retweet id, but in reality, no retweet was made.
Now, it's working as expected.
Can you confirm if it's working (or not) for you now?
@Rishikant181 tried manual trigger seems working perfectly. but here is the automatic one that happened just about less than 15 mins ago.
1|notification | [Rettiwt-API] [2024-11-02T19:02:47.519Z] [VALIDATE] {"target":"POST_ARGS"}
1|notification | [Rettiwt-API] [2024-11-02T19:02:47.522Z] [GET] {"target":"HTTPS_PROXY_AGENT"}
1|notification | [Rettiwt-API] [2024-11-02T19:02:47.522Z] [GET] {"target":"USER_CREDENTIAL"}
1|notification | 3 November 2024 Jam 02:02:51 WIB: info: [a37a1cd4-dd33-4ad7-a8c2-700fc683aafb] Rettiwt operation succeeded on attempt 1
1|notification | 3 November 2024 Jam 02:02:51 WIB: info: [a37a1cd4-dd33-4ad7-a8c2-700fc683aafb] TweetID 1852760490038178287 replied with media using Rettiwt 1852788478653985081
1|notification | replyTweetWithMedia-a37a1cd4-dd33-4ad7-a8c2-700fc683aafb: 6.718s
It said succeed but the tweet isn't exist. Then it will reply the sent tweet (log below)
1|notification | [Rettiwt-API] [2024-11-02T19:03:01.488Z] [REQUEST] {"resource":"TWEET_POST","args":{"tweet":{"text":"Censored","replyTo":"1852788478653985081","media":[{"id":"1852788518504062976"},{"id":"1852788518751485952"},{"id":"1852788518663356416"},{"id":"1852788518596268032"}]}}}
1|notification | [Rettiwt-API] [2024-11-02T19:03:01.489Z] [AUTHORIZATION] {"authenticated":true}
1|notification | [Rettiwt-API] [2024-11-02T19:03:01.489Z] [VALIDATE] {"target":"POST_ARGS"}
1|notification | [Rettiwt-API] [2024-11-02T19:03:01.490Z] [GET] {"target":"HTTPS_PROXY_AGENT"}
1|notification | [Rettiwt-API] [2024-11-02T19:03:01.490Z] [GET] {"target":"USER_CREDENTIAL"}
1|notification | 3 November 2024 Jam 02:03:05 WIB: warn: [0f5dc49f-6078-42df-aa89-382013b47022] Rettiwt attempt 1 failed: {}
1|notification | 3 November 2024 Jam 02:03:07 WIB: info: [0f5dc49f-6078-42df-aa89-382013b47022] Attempt 2/30 for Rettiwt operation
1|notification | [Rettiwt-API] [2024-11-02T19:03:07.202Z] [REQUEST] {"resource":"TWEET_POST","args":{"tweet":{"text":"Censored","replyTo":"1852788478653985081","media":[{"id":"1852788518504062976"},{"id":"1852788518751485952"},{"id":"1852788518663356416"},{"id":"1852788518596268032"}]}}}
1|notification | [Rettiwt-API] [2024-11-02T19:03:07.202Z] [AUTHORIZATION] {"authenticated":true}
1|notification | [Rettiwt-API] [2024-11-02T19:03:07.202Z] [VALIDATE] {"target":"POST_ARGS"}
1|notification | [Rettiwt-API] [2024-11-02T19:03:07.203Z] [GET] {"target":"HTTPS_PROXY_AGENT"}
1|notification | [Rettiwt-API] [2024-11-02T19:03:07.203Z] [GET] {"target":"USER_CREDENTIAL"}
1|notification | 3 November 2024 Jam 02:03:11 WIB: warn: [0f5dc49f-6078-42df-aa89-382013b47022] Rettiwt attempt 2 failed: {}
There is no error message too.
@gratatouilley Now I got hit with You have reached you daily limit for posting Tweets.....
on my alt account, even though I can retweet from the web app. Definitely something is awry. I'm investigating it further.
Retweeting for me works with text and video-based content. It seems the only problems seem to be with the images?
Found the issue, but right now, I don't have a solution.
The absence of the header x-client-transaction-id
is causing the issue. Earlier, no such header was required. I don't know how that ID is generated of where it's derived from.
Any input is welcome.
Hello! First of all thank you for all the work you are doing!
I think i stumbled across a bug:
Retweet isn't working, but giving "true" back. Everything else is working perfectly.
I'm using a proxy and also tried with fetcherservice, but with the same result > isnt retweeting but there is no error.