search

koenrh / delete-tweets

Delete tweets from your timeline.
ISC License
792 stars 107 forks source link

Could not authenticate you #102

Open MrMarti27 opened 3 years ago

MrMarti27 commented 3 years ago

Everything is set as described but when deleting tweets I'm getting the message

"code": 32, "message": "Could not authenticate you."

Fe-n commented 3 years ago

Edit 2: Nuked my twitter app and just did all of those elements over. I'm guessing it was some case of user error that I was just overlooking somehow. Did I mess up one of my keys somehow? Did I forget to change/check the app permissions? Who knows. Worked fine upon taking the 2min to simply start from scratch. Almost certainly was just me overlooking something stupidly.

Expanding on this, the first tweet it attempts to delete gives: Exception: {'Unknown error': ''}

All tweets after that give: Exception: [{'code': 32, 'message': 'Could not authenticate you.'}]

Maybe it fails because of whatever exception is happening with the first tweet? No idea. I have not really looked at the code base.

Edit: I've looked through the code to no avail really. However, I did edit my tweet.js to remove the first tweet (the one that was giving the unknown error) and verified that the first tweet in tweet.js will return the unknown error regardless of which tweet it is. What was previously the second tweet (now first) returned error code 32 ("Could not authenticate you.") before but now returns the unknown error.

belen-albeza commented 3 years ago

I'm having the same issue, I tried creating another app from scratch and still get the same errors (first an "unknown error" and later "Could not authenticate you"). The permissions are set to read + write, I (re)generated the tokens after setting them, and the env variables are OK.

Any tips into what's wrong here and how could I fix it? Thanks

bobmagicii commented 1 year ago

greetings from the end of 2022. the reason i post in this specific topic is mentioned midway through this experience.

when i first set up the app it gave me client id and secret, and apparently those were incorrect. after going back to the dashboard and regenerating them in the top most section pictured here

image

it gave me new strings that looked more what i am used to seeing, and then it worked.

another thing they are doing currently is actively sabotaging the api. if you exceed the rate limit, which now appears to be more strict than the documentation, they will begin spitting out 32 cant auth instead of 88 rate limit so that the clients cant do their job easily. sat here with a timer and everything, i am pretty confident in this having watched the same api credentials bounce between working and not.

added import time and time.sleep(5) to the script. my server aint got nothing but time. originally had it throttled to 10% slower than the rate limits and they still got pissy about it. eventually it just flat out quit completely and regenerating the creds worked.

import at the top, sleep at the bottom.

image