Stuck in a loop after sign in

[ferenczy]

I just installed a fresh instance of the portable version of the TweetDuck 1.20, executed it, filled in my Twitter credentials, 2FA code and after submitting them, TweetDuck gets stuck in a neverending loop. It just displays Twitter's main menu (the leftmost column) for a moment, then a blue screen with a spinner, then the menu again for a moment, and so on. Twitter's menu is showing my user account at the bottom so I have been apparently successfully signed in.

Windows 10 Pro 64-bit

[chylex]

It's not happening on my end with a fresh portable version. It's possible Twitter rolled out an update only for some accounts so I don't have it yet, but I don't know.

[paanvaannd]

I can confirm the same issue on 2 of my Windows machines as well.

• Windows installation versions:
  1. Windows 10 20H2 build 19042.1110
  2. Windows 10 21H1 build 19043.1083
• TweetDuck version (all systems): 1.20 (not portable)

I just installed TweetDuck on system 1 but system 2 had TweetDuck on it already. TweetDuck was working just fine on system 2 until July 13^th for me but not since then. I did not update TweetDuck since then (though I'm not sure if there was any auto-update performed). In case it matters, TweetDuck was isntalled via Chocolatey in both instances.

Since the issue started is reproducible for me in the system 2 without (again: to my knowledge) any update performed between the times when it was and is now not working, I think this may be something with a Twitter update itself as @chylex mentioned.

Please let me know if there is anything I can do to help further debug this issue. I actually have a 3^rd Windows installation with TweetDuck on it as well that I can check later so I will include information on that system to this as an edit.

e: specified that my TweetDuck installation is not portable

[chylex]

@paanvaannd Can you please install Dev Tools in the installer if you don't have it already (you can install in the same folder to add dev tools to an existing installation), then while it's looping right-click in the window, click Open Dev Tools, and see if there are any errors in the Console tab? Thanks.

[paanvaannd]

I'm not sure if there's a way to have Dev Tools freeze itself/output to a log file because it's unreadable due to Dev Tools's output itself looping as TweetDuck does.

However, I screencap'ed the looping window output and scrubbed that for the relevant errors/warnings:

That said, I may have missed some. So I'll upload the error/warning screenshots below that I identified from the screencap and am also uploading the screencap in case you want to double-check my work.

https://user-images.githubusercontent.com/16567134/125861090-ccf5872e-cf00-4a48-9c60-c17426020867.mp4

Let me know if there's anything else I can help with!

[chylex]

Click the gear on top right (second row) that says Console Settings, then check Preserve log.

From the current log, it looks like you're being rate-limited (possibly because of the loop itself), so please check Preserve log, close the app, then wait 15 minutes and try again.

[chylex]

Once you try again and it loops a few times, you can go to Sources tab and click the Pause button, that'll stop everything and you should have an opportunity to see the Console without the looping:

Like on the screenshots you sent, there might be expansion arrows on the left side of some lines in the Console. Please expand each line at least once, there might be multiple levels of expansion so if there are multiple levels and the first expansion isn't too long, try expanding a bit more in case some information is hidden deeper.

There could potentially be sensitive information, so censor any usernames and long random looking sequences in case they're secret tokens. If you're not sure, you can DM me on Twitter @chylexmc or the app account.

Thanks!

[paanvaannd]

Quite a lengthy output! I captured it using a scrolling screenshot and the resolution is good enough to read the output on my computer but I'm not sure if compression from either GitHub or Twitter (via DM) would hamper that readability.

To my untrained eye, there is no sensitive information within this output, but I'll share it via DM on Twitter to be sure. If you also don't see any hint of sensitive info on the screenshot, I wouldn't mind uploading it here as well for others to view in case they run into the same issue as well and want to see this output.

[paanvaannd]

Scratch that: it's working now!

I have the output and can still send it if desired but rather than do that (it's 97 images stitched together: quite the lengthy read) and waste your time, here was the fix:

I logged into Twitter on my Web browser and Twitter asked me to verify that I am a human. After doing so and verifying my phone number, I was able to access both the Twitter website and TweetDuck started working in the background once again.

What likely happened was that Twitter locked me out for some reason (I use a commercial VPN with an IP that's been blocked across several sites. perhaps because someone is abusing it... this is why we can't have nice things *sigh*) and that caused TweetDuck to act up.

e: MP4 → GIF

[chylex]

Interesting, maybe the Twitter API doesn't have a way to verify if you're a human so it just rejects your login attempt instead. Nice work, Twitter.

[chylex]

I don't know if others have been able to resolve this issue, but we have one possibility for the reason and I don't know what else might have happened. Feel free to comment if you're still experiencing the issue or have any new insight, but for now I'm closing this.