AppFlowy-IO/AppFlowy

Fork 0

mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 12:56:59 +00:00

[GH-ISSUE #8221] [Bug] Automatically logout permently #3662

New issue

Closed

opened 2026-03-23 21:32:13 +00:00 by mirror · 5 comments

mirror commented

2026-03-23 21:32:13 +00:00

Owner

Originally created by @da-wilky on GitHub (Sep 15, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8221

Bug Description

Since upgrading to v0.9.9 my Desktop- and Android-App of AppFlowy doesnt stay logged in anymore. After closing the app and waiting for a few hours I need to Log in again. Before I was kinda permently logged in, what I prefer.

How to Reproduce

Selfhosting AppFlowy v0.9.9
Log in via Desktop/Android App.
Close App.
Wait a few hours.
Start the App again.
You are not logged in anymore and need to reauthenticate.

Expected Behavior

Stay authenticated like in the versions before.

Operating System

Android 16, Windows 11, (Server on NixOS via Docker)

AppFlowy Version(s)

v0.9.9

Screenshots

No response

Additional Context

No response

Originally created by @da-wilky on GitHub (Sep 15, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8221 ### Bug Description Since upgrading to v0.9.9 my Desktop- and Android-App of AppFlowy doesnt stay logged in anymore. After closing the app and waiting for a few hours I need to Log in again. Before I was kinda permently logged in, what I prefer. ### How to Reproduce 1. Selfhosting AppFlowy v0.9.9 2. Log in via Desktop/Android App. 3. Close App. 4. Wait a few hours. 5. Start the App again. 6. You are not logged in anymore and need to reauthenticate. ### Expected Behavior Stay authenticated like in the versions before. ### Operating System Android 16, Windows 11, (Server on NixOS via Docker) ### AppFlowy Version(s) v0.9.9 ### Screenshots _No response_ ### Additional Context _No response_

mirror closed this issue

2026-03-23 21:32:13 +00:00

mirror commented

2026-03-23 21:32:14 +00:00

Author

Owner

@khorshuheng commented on GitHub (Sep 16, 2025):

There is an env variable named GOTRUE_JWT_EXP , which is set to 7200 seconds (2 hours) by default. Can you adjust this variable and redeploy the server?

@khorshuheng commented on GitHub (Sep 16, 2025): There is an env variable named `GOTRUE_JWT_EXP` , which is set to 7200 seconds (2 hours) by default. Can you adjust this variable and redeploy the server?

mirror commented

2026-03-23 21:32:14 +00:00

Author

Owner

@da-wilky commented on GitHub (Sep 16, 2025):

Thanks for the reply! I'll give it a try.
This also means, that my time logged in inside the browser will extend, right?
Is there a way for the Apps to stay "always signed in" while the browser needs to reauthenticate after the JWT_EXP time? That would be my favorite and as far as I can tell this was the behavior before updating.

@da-wilky commented on GitHub (Sep 16, 2025): Thanks for the reply! I'll give it a try. This also means, that my time logged in inside the browser will extend, right? Is there a way for the Apps to stay "always signed in" while the browser needs to reauthenticate after the JWT_EXP time? That would be my favorite and as far as I can tell this was the behavior before updating.

mirror commented

2026-03-23 21:32:14 +00:00

Author

Owner

@da-wilky commented on GitHub (Sep 17, 2025):

So this fix indeed helps solving the problem. Thank You! :)
Still I got the question or feature request, if you can stay signed in inside those apps permently while needing to reauthenticate inside the browser. Maybe with a checkbox "Stay signed in" or something like that?

@da-wilky commented on GitHub (Sep 17, 2025): So this fix indeed helps solving the problem. Thank You! :) Still I got the question or feature request, if you can stay signed in inside those apps permently while needing to reauthenticate inside the browser. Maybe with a checkbox "Stay signed in" or something like that?

mirror commented

2026-03-23 21:32:14 +00:00

Author

Owner

@da-wilky commented on GitHub (Oct 22, 2025):

This got fixed by the v0.10.1 release. Thank you!!

@da-wilky commented on GitHub (Oct 22, 2025): This got fixed by the v0.10.1 release. Thank you!!

mirror commented

2026-03-23 21:32:14 +00:00

Author

Owner

@annieappflowy commented on GitHub (Oct 23, 2025):