2fast-team/2fast

App suddenly useless

Opened this issue · 7 comments

Describe the bug

App doesn't open anymore even if correct password is entered.

Steps to Reproduce

I installed the app around a week ago and have around 10 2FAs set up there. It worked nicely until just now. When I open the app now, and I enter the password, I receive the following error message:

#Value does not fall within the expected range.
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
at Project2FA.Services.DataService.d__70.MoveNext() + 0xb56

Then I have two options: restart app or close app. After restarting, the same happens again. Which means that effectively, I cannot use the app anymore.

App Version:

  • Windows 10 22H2 Update

Additional context

If you start the file with a double click and enter the corresponding password, does this work?

For more detailed information you could post the log file AppLog.log here:
C:\Users\YourUsername\AppData\Local\Packages\38343JanPhilippWeber.2fastTwoFactorAuthenticatorSu_nxr4mypqfqb9c\LocalState

Hey, that's good to hear that the problem no longer exists! I suspect that it's due to a Microsoft library and the corresponding API. Could you post the contents of the log file as a comment, unfortunately the attachment didn't come with it.

Best regards

Happened the same to me,

I think the app problem is it's heavy reliance into UWP or Edge caching. I'm not a developer but this is how to replicate the problem:

  • Run an disk cleaner app like Wise Disk Cleaner or CCleaner
  • Run again 2fast. App won't work and password won't open the data file.
  • Repair or restore won't work.
  • Uninstall, reboot, re-install works to solve the problem.

Hope it helps,

PS: Your app is awesome, just some hiccups you've been fixing each release.

Thanks for the information I will try to replicate this in a virtual machine so that I can maybe catch the error and fix it automatically.