Crashes when attempting to install from file etc
JetLynx opened this issue · 3 comments
First and foremost, thank you for your interest in making qFlipper better by reporting bugs!
in Windows 10, qFlipper crashes when I try to install firmware from file, Backup, or Restore. Attempting to factory reset using Erase function also stays on "Performing Factory Reset" screen and never fails nor succeeds
What were you trying to do? Install custom firmware, specifically RogueMaster. At this point I can't do any of the above functions.
To Reproduce
Steps to reproduce the behavior:
- Run qFlipper, either normally or as Administrator
- Click on install from file, Backup, or Restore
- See qFlipper crash immediately
Expected behavior
Firmware flashing process to run and complete. Or any of the above functions to run without crashing.
Actual behavior
qFlipper crashes without any error messages or dialog windows.
Additional troubleshooting
- Does the issue persist if you try multiple times? Yes
- Does reconnecting/rebooting Flipper solve it? No
- Does re-installing solve the issue? No
- Does running as Administrator solve it? No
- Does restarting the computer solve it? No
- Does formatting the SD Card and performing the factory update and database install solve it? No
The report must also include at least one of the following:
- A FULL LOG of this application run. (see below).
- A screenshot of the application window (if it is a graphical issue).
Additional context
Running Erase results in the program staying on the progress screen, Reinstall seems to work.
Quickfix until a solution patches the logic, but for anyone else who has this issue it's due to qFlipper opening up the File Browser to a location that doesn't exist if it saved that location as the last location used.
Quickfix until a solution patches the logic, but for anyone else who has this issue it's due to qFlipper opening up the File Browser to a location that doesn't exist if it saved that location as the last location used.
I recreated the directory that's listed at the end of the log and now all issues are resolved.