From 55d6fa47cdf7c4b06a8345f4567e550a2d08d070 Mon Sep 17 00:00:00 2001
From: Pierre-Alain TORET <22810624+daftaupe@users.noreply.github.com>
Date: Sun, 25 Feb 2024 17:12:55 +0100
Subject: [PATCH] Created Invalid token renewal (markdown)

---
 Invalid-token-renewal.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 Invalid-token-renewal.md

diff --git a/Invalid-token-renewal.md b/Invalid-token-renewal.md
new file mode 100644
index 0000000..d99c73d
--- /dev/null
+++ b/Invalid-token-renewal.md
@@ -0,0 +1,15 @@
+An issue that might arise is the Android app losing the authentication Token for some reason and you not noticing immediately.
+
+Once facing this issue, you will have some items not synced with the server and if you delete the accoun to re-add it, you will lose them.
+
+On a selfhosted EteSync server you will get lines such as the following : 
+INFO:     ::1:28393 - "POST /api/v1/collection/list_multi/?stoken=Y2TMWsPY5RXf4tUBDmAIXQpCgf8h9scN HTTP/1.0" 401 Unauth
+orized
+INFO:     ::1:51824 - "POST /api/v1/collection/list_multi/?stoken=Y2TMWsPY5RXf4tUBDmAIXQpCgf8h9scN HTTP/1.0" 401 Unauth
+orized
+INFO:     ::1:42106 - "POST /api/v1/collection/list_multi/?stoken=Y2TMWsPY5RXf4tUBDmAIXQpCgf8h9scN HTTP/1.0" 401 Unauth
+orized
+
+One way to prevent this is to use the option in the Android app account's settings : Encryption password (change your encryption password), where you can reuse the same one as before). That gets you a new token and the items are not lost but will get synced with the server.
+
+Solution taken from https://github.com/etesync/android/issues/227
\ No newline at end of file