Some accounts have been banned, but dub doesn't seem to be able to detect them

[yuukiki]

Waited: 585/600s

Long wait time -> 600 seconds (10 minutes) has occurred.

[martin@rootjazz]

However, if no POP or IMAP information is entered in the account details, please exit immediately without attempting to unlock the email verification.
A long wait time is occurring.

Then I would like to see a 'mail validation required' statement on the Failed last login.

This would help us detect temporarily restricted accounts.

My apologies, this should be happening already. Let me check and fix it for next update. I think I have an idea why it isn't...

[martin@rootjazz]

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

[yuukiki]

Waiting time no longer occurs.
However, no message appears in Failed Last Login when email verification fails.

logs_94476

[martin@rootjazz]

Waiting time no longer occurs.
However, no message appears in Failed Last Login when email verification fails.

logs_94476

will check / sort tomorrow / Sunday

[yuukiki]

The logs show several types of errors in case of tweet failure.

Example
-
Bridge Error: ExFailed EX_FAILED: ELEMENT_NOT_EXIST Failed find element to click: Failed click username input
-
Bridge Error: Exception net::ERR_TIMED_OUT
-
Bridge Error: Exception Timeout 10000ms exceeded.Call log:- navigating to "https://x.com/home", waiting until "domcontentloaded" job
-
Bridge Error: Exception Timeout 20000ms exceeded.Call log:- waiting for Locator("//*[contains(@data-testid,'tweetTextarea_0_label')]")
-
Bridge Error: ExFailed EX_FAILED: LOG_ID_SCREENSHOT Failed detect all medias uploaded within timeout
-
Bridge Error: ExFailed EX_FAILED: 44842227324111472834576325 Login verification required - no POP
-

Currently Failed Last Login states 'browser timeout' and the type of error is unknown.
How about stating the xxxxx part of 'Bridge Error: xxxxx' instead?

[martin@rootjazz]

Waiting time no longer occurs.
However, no message appears in Failed Last Login when email verification fails.

logs_94476

will check / sort tomorrow / Sunday

Sorry, had a major issue come up that took all day to fix).

Looking at this and your issues above

[martin@rootjazz]

The logs show several types of errors in case of tweet failure.

Example
-
Bridge Error: ExFailed EX_FAILED: ELEMENT_NOT_EXIST Failed find element to click: Failed click username input
-
Bridge Error: Exception net::ERR_TIMED_OUT
-
Bridge Error: Exception Timeout 10000ms exceeded.Call log:- navigating to "https://x.com/home", waiting until "domcontentloaded" job
-
Bridge Error: Exception Timeout 20000ms exceeded.Call log:- waiting for Locator("//*[contains(@data-testid,'tweetTextarea_0_label')]")
-
Bridge Error: ExFailed EX_FAILED: LOG_ID_SCREENSHOT Failed detect all medias uploaded within timeout
-
Bridge Error: ExFailed EX_FAILED: 44842227324111472834576325 Login verification required - no POP
-

Currently Failed Last Login states 'browser timeout' and the type of error is unknown.
How about stating the xxxxx part of 'Bridge Error: xxxxx' instead?

ok before program was just mapping known failed responses and updating the failed column. I'll try it just displaying the failed column if cannot match to known issues from now on. See if that works better...

[martin@rootjazz]

Waiting time no longer occurs.
However, no message appears in Failed Last Login when email verification fails.

logs_94476

should be sorted for next update


The next update will fix this. I shall let you know when it is ready.



Regards,
Martin

[martin@rootjazz]

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