-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync Failure #189
Comments
Closing as deleting the account and re-adding it fixes the sync issue. Would be nice to figure out why this happens in the first place. |
The issue has happened again. About 2 weeks the token was valid before all syncing failed. Going to keep this open until it's resolved. Having to delete and re-add the account is not a viable solution, especially if there there are local pending changes that will be lost. Let me know what other information I may need to provide to help debug. |
This problem has been occurring for me since 2021-09-15 or 2021-09-16:
|
This error is not occurring for me anymore, but I am not able to synchronise with tasks.org, which may be relevant. |
I just noticed that this has been failing for 3 Months now, so yes, Id appreciate a fix without readding my account as well |
Do you know what error you are getting when it fails? Or it just hasn't synchronized any data in three months |
@lenowac what is failing for 3 months? |
For me, reinstallation and subsequent reconfiguration of EteSync and Tasks.org did cause synchronisation to become operational. |
This is very different to mine: it did not display any notification of errata. |
Well, mine did neither for months. Must have done something to trigger it, maybe open the app, idk. |
I was getting a notification error when it happened to me. I don't recall the exact wording (something along the lines of synchronization failed), but it was through that notification that I was able to provide the debug log for this issue in my initial post. |
"me too" I had this same issue as shown in the screenshots above (F-Droid build 2.2.4): invalid token, sync issues, and this went unnoticed for a while. Once I noticed the problem, as I could find no way to logout, and the "delete account" warned me that it would delete all the local data (which I didn't want), I had no better idea than to re-install. So I uninstalled the app, re-installed it, and could re-login. Perhaps this was a mistake, as I lost data in the process, but I don't see what I could have done differently. However, the last successful sync is from end of July, so I lost 4 months worth of contacts, tasks, and calendar entries doing this. 😢 I'm quite disappointed, really not cool to have data loss with an app whose purpose is to avoid having data loss. There doesn't seem to be any way to take a backup of the local state if syncing fails for any reason; so if not addressed by an uninstall/re-install right immediately after syncing fails; it seems the design of etesync just assumes access tokens for login always work; there is no way to logout/login without deleting all the data on the phone. @tasn perhaps you could
|
I have the last version from Google Play and I'm getting same error last 2 months. So I have new local unsynchronized data. What should I do for successful synchronization? Synchronization with the server and thus avoid data lost is essential functionality of EteSync. So I would expect resolving of this issue within a few weeks. Issue is open 3 months and nothing happend. Why? I'm disappointed. This is not how I imagine a payment service. |
I'm getting the same error as the 2nd post in this thread about a server error. The TLS certs were just updated and I had to approve the new fingerprint. I recall when this issue had last happened I had to do the same as well. I'm wondering if this error has to do with the cert renewal being out of sync with something on the back end (pinning, time discrepancies, etc)? |
Sorry, the server error was unrelated. TLS certs error is more often than not a captive portal or something of that sort on the client network (rather than the server network). |
I don't know if this is related to #186 as that issue did not contain a debug error log to determine that. I just started to get this error today. My version is also from F-Droid.
Not sure if this is the culprit, but also curious as to why these show up as denied:
Let me know if you need anymore information. Thank you.
The text was updated successfully, but these errors were encountered: