Tags: not-nullptr/Aerochat
Tags
fix: Proper error handling for invalid stored tokens Previously, Aerochat would just crash whenever a token is invalid. This would cause issues in some cases, such as a user transferring their configuration from another account or system, or a developer forgetting to clean up build artifacts when publishing releases (:P). In these cases, the application would simply refuse to open because of an unhandled exception at startup. Now, the case is handled clearly to the user. They are informed of why they are logged out and then taken to the login screen so they can reauthenticate. For bonus points, I added a warning dialog for rare edge cases where the Data Encryption API isn't supported, including older operating systems and non-Windows operating systems (perhaps old versions of Wine?). Signed-off-by: Isabella <kawapure@gmail.com>