Fix/safestorage linux fallback - #6
Open
hebuildapps wants to merge 2 commits into
Open
Conversation
|
@hebuildapps is attempting to deploy a commit to the jvaught01's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey man, really enjoying Flicky!
While setting up on my arch Linux (Hyprland) where safeStorage.encryptString() crashes the app because no D-Bus secret service daemon is running in the background.
Added a quick check for safeStorage.isEncryptionAvailable(). If it returns false, it falls back to plain Base64 encoding so saving/reading API keys works smoothly. macOS, Windows, and supported Linux DEs will still use native OS encryption as normal.
Let me know if this looks good to merge!