-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Description
Bug Description
When trying to login via a magic-link or OAuth, users are either sent a link via email, or taken to the said service to login through it via the browser. Both scenarios will yield an open with xdg-open when prompted.
Adding the mimetype x-scheme-handler/appflowy-flutter in .config/mimeapps.list does result in a correct link to AppFlowy when prompted.
.config/mimeapps.list
[Default Applications]
.
..
...
x-scheme-handler/appflowy-flutter=appflowy.desktop
Where appflowy.desktop is as follows:
[Desktop Entry]
Name=AppFlowy
GenericName=App Flowy Notes
Comment=Bring projects, wikis, and teams together with AI
Icon=AppFlowy
Type=Application
Categories=office;
DBusActivatable=true
SingleMainWindow=true
X-GNOME-UsesNotifications=true
X-GNOME-SingleWindow=true
Exec=PATH/TO/APPIMAGE %U
StartupNotify=false
Terminal=false
MimeType=x-scheme-handler/appflowy-flutter;
However, this will still lead to an issue where AppFlowy does not respond to the access token. Following #5651 (comment) solution, and manually grabbing the access token and executing AppFlowy will result in a buffer overflow.
The hacky way around this for magic-links is to delete both &expires_at and expires_in from the access token.
How to Reproduce
Attempt to login using the AppImage
Expected Behavior
Normal login process
Operating System
Solus OS
AppFlowy Version(s)
0.7.1
Screenshots
No response
Additional Context
No response