auto logged out

[lilarcor]

Q	A
Device?	iPhone
Device Os version	11.3
App Version	2.3
Wallabag server version	2.3.2

I got my id logged out from time to time, and I have to re-key in my password to log in. Don't know how it happened.

[bourvill]

what service do you use?

[lilarcor]

i don't know about the service you mentioned, can it be more specific ?

[bourvill]

Where is your wallabag instance? On your on server? Or service like wallabag.it ?

[lilarcor]

oh, it's on my personal server. I don't have a static ip for my internet connection. So my server's ip could be updated, and I access it through DDNS, I am not sure if that will cause the issue

[lsf3og]

I have the same problem with wallabag.it.

[pheraph]

Same here with a self hosted wallabag (static IP). :-(

[bourvill]

Do you have a message when you are logged out? Or app crash?

[lsf3og]

No message or crash. Just need to enter my password again. Am 11. Mai 2018, 08:14 +0200 schrieb Maxime Marinel <notifications@github.com>:

…

Do you have a message when you are logged out? Or app crash? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[lilarcor]

no app crash. App remembers server URL,client_ID , client_secret and username, I have to keep pressing next then input password to re-log on.

[timscha]

I have the same problem on my iPad with the latest iOS 11.3 and self hosted wallabag.
It looks like the App forget my session. All details like Client id are Safed, but I had to reconfirm everything in the setup at the beginning. There was no crash or something else.

[persona404]

Same issue here. Self hosted, accessible through ddns, iOS 11.4 on both iPhone and iPad. All info saved except password which needs to be re-entered. Seems to happen at least once a day. No error or crash, just asks for login.

UPDATE JUNE 27: Since the last update, I had one instance of being logged out, but nothing for the past couple of days. Issue appears to be resolved. 👍

[bourvill]

I think the problem has been solved with the latest version (2.3.3).

If the problem persists open a new issue. Thank