Frosty doesn't register that I've signed into my Twitch account.

[Nightbre]

Describe the bug
I don't actually know if this is a bug, or if it's literally just my phone being its usual self, but for some reason, when I go to sign into my Twitch account, the app doesn't seem to register that I've input the details and authorized it to use my account.

To Reproduce
This one... This one I'm not finding any way of replicating, either because the app becomes unresponsive and I have to clear the storage, or because many features simply stop responding. The app doesn't seem to register that anything's even happened, either, which is definitely problematic! I'm new to the app, and there may still be a way to replicate this issue, and I'm simply not seeing it, however.

Expected behavior
This is probably a lil' obvious by this point, but simply signing into my Twitch account.

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

• Device: T-Mobile Revvl 5G
• OS: Android 11
• App Version: Version 2.0.0 (25)

Additional context
So the real interesting thing is that I can go through the login process like normal, but the moment I tap "authorize" and it goes through to the next screen, it simply blips out of that screen and returns to the app's interface, behaving as if I were still anonymous, but with many of the app's features becoming unresponsive to input, such as the search function and options to change chat behavior. Outside of this change in behavior, the appearance of the interface doesn't change at all.

Clearing the app's storage and uninstalling both net the same results, allowing me to get past the loading screen and into the app, but still behaving as described above when I attempt to sign in.

This could very easily be an issue with the phone I'm using, rather than the app itself, as this sort of thing HAS happened before, but I find it a bit peculiar that it's happening with this app in particular.

[Nightbre]

Did I just close this just now-

[Nightbre]

Okay wow, I have a lot to learn about this site, it seems. HAHA!

Anyways, any help would be greatly appreciated! I'll edit the main post if I figure out a way to replicate the bug, but it's just weird.

[tommyxchow]

Thanks for opening this issue. I might have an idea of what's causing the login problem.

Frosty currently has Auto Backup enabled (it's enabled by default for all Android apps). Auto Backup essentially securely backups up all the settings and user authentication details so that they persist when re-installing the app. This is supposed to make it easier to reinstall apps because you won't have to log in again and tweak all your settings.

I completely forgot about it being enabled until today when I looked over some documentation from flutter_secure_storage, the package I use to encrypt and store user login tokens on the device itself.

So, when Frosty is reinstalled, it'll restore old existing data which may cause all sorts of issues and conflicts. My code is written in a way that it expects a clean slate when reinstalling. I definitely could've written some better code to handle this situation, but unfortunately, I overlooked it.

To fix this, I'm going to disable Auto Backup on the app. In the future, I may fix up the initialization code so that Auto Backup can be safely re-enabled.

One more thing: If you're familiar with APKs, could you try installing the Frosty APK here under "assets" and let me know if that works for you? APKs don't have any backups whatsoever so I want to make sure that's the root cause of your case.

[Nightbre]

I installed Frosty via the APK and that doesn't seem to be the issue. Same behavior as before, for the most part. I'm unsure as to what may be causing this strange issue.

The biggest difference between the Google Play and APK download is that the app's features continue to respond, but it otherwise still freezes on the startup screen when trying to load back into it.

Attempting to sign in after the first attempt shows the authorization screen, but doesn't change anything if I repeat the process.

Edit: Okay, so attempting to sign in without leaving the app (I have 2FA active on my account) resulted in the Twitch login screen appearing after authorizing the app to use my account, but the app quickly closed the window and nothing else changed. It seems it might be something to do with the browser the app pulls up to sign in, if that's what it is.