Web interface not loading / cookie problem
merlinuwe opened this issue · 21 comments
There is a cookie problem with syncthing. The solution is to delete the cookies. How do I do this on android in your app?
There is the same issue.
Maybe removing the cache in the android app setting (not user data!) helps - worth a try.
I think you may need to clear the cache (and possibly data too) of the WebView app, not Syncthing.
Clearing the cache doesn't solve the problem.
Clearing the cache doesn't solve the problem.
Of both the Syncthing app and the WebView app? If yes, then please try to clear data of just the WebView app (but not the Syncthing app, as doing so will reset all your Syncthing settings!).
- I made a backup of the Syncthing settings.
- I deleted the cache and the data.
- I deinstalled syncthing.
- I rebooted the smartphone.
- I installed syncthing.
- I loaded the backup file.
It solved the problem. ;-)
- I'm happy. 😊
Today my Syncthing Web UI suddenly became unusable. (after upgrading to 1.26.0, 2023/11/07 on Google Play)
Don't sure if what I've encountered is same as this (web UI i18n blink repeatedly and totally unusable), also fixed via backup+uninstall+install+import backup. Merely clearing cache doesn't work.
Screen_Recording_20231108_110033_Syncthing.mp4
Anyone reading this, before taking the radical option maybe follow the suggested procedure first - so far no-one confirmed that they tried it and reported whether it helps:
[Did you clear cache] Of both the Syncthing app and the WebView app? If yes, then please try to clear data of just the WebView app (but not the Syncthing app, as doing so will reset all your Syncthing settings!).
I clean WebView app data. Not work.
I cleared the cache of both Syncthing-Android and Android System WebView and it didn't resolve this issue for me.
Then I cleared storage of Android System WebView, but that also didn't help.
Same issue here. After downgrade to 1.23.7 re-setup of all synced folders, Syncthing seems fine again. No clue about the cause though.
This has most likely the same root cause as syncthing/syncthing#9208
- I made a backup of the Syncthing settings.
- I deleted the cache and the data.
- I deinstalled syncthing.
- I rebooted the smartphone.
- I installed syncthing.
- I loaded the backup file.
It solved the problem. ;-)
- I'm happy. 😊
It worked for me too, without steps 3, 4, 5
It worked for me too, without steps 3, 4, 5
Confirmed. It worked for me too.
Don't do this!
It may "work", but it also removes the entire database. At best that's wasteful (everything needs rehashing), at worst it messes with your data (conflicts, resurrected deleted data, ...).
A fix in Syncthing is in the works.
This hopefully is fixed by the latest RC. Reports from anyone that's currently affected and does the upgrade would be appreciated.
- I made a backup of the Syncthing settings.
- I deleted the cache and the data.
- I deinstalled syncthing.
- I rebooted the smartphone.
- I installed syncthing.
- I loaded the backup file.
It solved the problem. ;-)
- I'm happy. 😊
Successful here too! Thanks!
Just got the update, and apparantly I was also effected before by this bug, and it works fine again since the latest RC upgrade.
@opusforlife2 As for F-Droid: There's no beta track there. Afaik you could create one by duplicating the app config at F-Droid, naming it something like "syncthing-android-rc".
I won't release the syncthing RC as a real release, as that would force enable usage reporting.
There's no beta track there.
@imsodin That's not what I'm referring to. When there is an emergency, the F-Droid maintainers can manually add a release instead of relying on the bot. It would be worth contacting them to see if that can be done here.
@imsodin That's not what I'm referring to. When there is an emergency, the F-Droid maintainers can manually add a release instead of relying on the bot. It would be worth contacting them to see if that can be done here.
I don't want that to be done here, as it would release an RC and thus force enable usage reporting for everyone.
Anyway Jakob created a hot-fix tag on syncthing, I should get around to releasing that by end of day.
Don't do this! It may "work", but it also removes the entire database. At best that's wasteful (everything needs rehashing), at worst it messes with your data (conflicts, resurrected deleted data, ...).
A fix in Syncthing is in the works.
@imsodin I'm experiencing the issue and haven't done this workaround. If you let us know when the patch lands on F-Droid, I can report back if that fixes it for me!
EDIT 11/20: F-Droid published the update, fixed it for me without the workaround 🚀
If you let us know when the patch lands on F-Droid, I can report back if that fixes it for me!
The Synching project isn't responsible for F-Droid releases. They build and upload the app on their own, which is usually a few days after the official release here.