TD not posting tweets

[TwitterM]

Saw the other thread about tweets not being posted, but didn't know if this issue is different.

Getting this in the raw logs:

17:58:24: Scraping Daily stats for: accountinquestion
17:58:24: GET: https://mobile.twitter.com/accountinquestion
17:58:24: 403
https://twitter.com/i/users/prompts
{"message":"Could not authenticate you."}
17:58:24: prompt.prompts is null!

. . .

17:58:26: WARNING: authentication issue - account needs to log in again!
17:58:26: * FAILED: stats failed to scrape: 92340750923875983658 : Get request response authentication errors: 401
https://api.twitter.com/1.1/users/looku ... inquestion
{"errors":[{"code":32,"message":"Could not authenticate you."}]}

Logs: 98360

Logging into the account using the session browser nothing seems to be wrong - although I had to enter phone # (which was already provided in the account info in TD, so it should have been entered automatically I guess).

Please let me know if you need more information.

[martin@rootjazz]

Please try this.

If using AUTO RUN on processing tab, turn it off
Restart app
Pause all existing actions
clear logs: HELP >LOGS > DELETE
goto ACCOUNTS tab
UNCHECK Use Proxy box
check account
right click account > select DELETE COOKIES (maybe reset cookies)
Click VERIFY LOGIN

Run the action, if doesn't work, submit logs
HELP > LOGS > SUBMIT

then send your logs ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)


If you have an account I can test with this issue, please export and email it over:

Code: Select all

support[at]rootjazz[dot]com

Regards,
Martin

[TwitterM]

Sent you an email with some accounts.

Had some trouble following the instructions, as I couldn't find most of the options described.

[martin@rootjazz]

anyone else with this issue.

update:
https://rootjazz.com/twitterdub/updatetesting.html

Clear cookies:
CHECK account, right click account > DELETE COOKIES
goto ACCOUNTS tab, check account, uncheck USE PROXIES, click VERIFY LOGIN

should fix it


Regards,
Martin

[mpak]

Hello

I'm having a similar problem with 3.0.8.164. Tried to update .NET framework but microsoft says i'm up-to-date. zip file in the download page asks for password so I couldn't use it.

The problem only occurs with a newly added account.

So the login is working but not without problems. First I always get this:

Login: get: https://twitter.com/
Login: Success validate:
200
https://twitter.com/
WARNING: login failed / authentication issues, please try a clean login
Login failed: prompts

Then it goes through. However, I can't post tweets and update info (bio) and probably everything else. I get this error:
FAILED POST: (286247) 403
https://api.twitter.com/1.1/account/update_profile.json
* WARNING: Request failed with Twitter response: Your credentials do not allow access to this resource.
ERROR RESP FROM TWITTER: 220 Your credentials do not allow access to this resource.

After searching on forum and trying many things I finally made it work by going into Accounts tab, unchecking Use Cookies and Verifying login. I suppose this makes this particular account to work further without cookies?

The thing is all of my old accounts are working fine with cookies. It's just that one new account that I made and it just didn't work. First I created it in some old version. It didn't work. I updated TD and removed entirely this account and recreated it. Maybe that's causing problems.. but I'm pretty sure accounts in twitterdub are attached to some ID not username. I've tried delete cookies/remove local blocks/reset useragent multiple times - didn't help.

I'll keep adding new accounts and see how it goes.

[martin@rootjazz]

Hello

I'm having a similar problem with 3.0.8.164. Tried to update .NET framework but microsoft says i'm up-to-date. zip file in the download page asks for password so I couldn't use it.

The problem only occurs with a newly added account.

So the login is working but not without problems. First I always get this:

Login: get: https://twitter.com/
Login: Success validate:
200
https://twitter.com/
WARNING: login failed / authentication issues, please try a clean login
Login failed: prompts

Then it goes through. However, I can't post tweets and update info (bio) and probably everything else. I get this error:
FAILED POST: (286247) 403
https://api.twitter.com/1.1/account/update_profile.json
* WARNING: Request failed with Twitter response: Your credentials do not allow access to this resource.
ERROR RESP FROM TWITTER: 220 Your credentials do not allow access to this resource.

After searching on forum and trying many things I finally made it work by going into Accounts tab, unchecking Use Cookies and Verifying login. I suppose this makes this particular account to work further without cookies?

The thing is all of my old accounts are working fine with cookies. It's just that one new account that I made and it just didn't work. First I created it in some old version. It didn't work. I updated TD and removed entirely this account and recreated it. Maybe that's causing problems.. but I'm pretty sure accounts in twitterdub are attached to some ID not username. I've tried delete cookies/remove local blocks/reset useragent multiple times - didn't help.

I'll keep adding new accounts and see how it goes.

Goto the ACCOUNTS tab
Check the account
right click > DELETE COOKIES
Uncheck option to USE EXISTING COOKIES (top left)
click the link VERIFY:LOGIN

This will create an action and send it to the PROCESSING TAB
Goto the processing tab and click RUN. The action will run.
You can double click the action to view the logs and submit logs

IF that was successful, try your action again, should work



Regards,
Martin

[mpak]

I've tried a new account today.

It still didn't work when I added a new account and tried to use twitterdub as usual.

However, it works the way you suggested through this Uncheck Cookies and Verify Login. So it's ok for me for now.

[martin@rootjazz]

I've tried a new account today.

It still didn't work when I added a new account and tried to use twitterdub as usual.

However, it works the way you suggested through this Uncheck Cookies and Verify Login. So it's ok for me for now.

Strange as adding a new account by default is a clean login with no cookies and by going the uncheck cookies route, you are just reissuing a normal first time account add with verification!

But if is working now, that's the main thing. If the problem comes back and you want me to look into it further, then submit logs after the issue and export the account details for me to test here



Regards,
Martin

[bmanfacts]

I was going to submit a thread for this but noticed this conversation already occurred.

So I only wanted to add that this helped me when I faced the same issue.

But yeah like the OP, this happened on accounts I freshly added to the software which should run as a fresh cookie login process as you've noted Martin. But I ran into that issue from freshly added accounts while the "Use Cookies" was CHECKED.

Might be an anomaly of two people but strange indeed.

Just wanted to add that the OP's experience on the test reflected my exact issue including the followup observation. Might be helpful for your notes
Incase you want to see the logs of their addition

LogID: 79632

[martin@rootjazz]

I was going to submit a thread for this but noticed this conversation already occurred.

So I only wanted to add that this helped me when I faced the same issue.

But yeah like the OP, this happened on accounts I freshly added to the software which should run as a fresh cookie login process as you've noted Martin. But I ran into that issue from freshly added accounts while the "Use Cookies" was CHECKED.

Might be an anomaly of two people but strange indeed.

Just wanted to add that the OP's experience on the test reflected my exact issue including the followup observation. Might be helpful for your notes
Incase you want to see the logs of their addition

LogID: 79632

Update to the latest version:
https://rootjazz.com/twitterdub/updatetesting.html

clean login on all accounts with the issue. And from reports, the issue should not occur again



Regards,
Martin