-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Task sync failed: Error while creating local entries (Android 12, Etesync app 2.4.2) #235
Comments
I was just going to ask this as well...looks like a bug on Android that is preventing syncing and writing of tasks to the local Android device. I've had this problem for about five days now. --- BEGIN DEBUG INFO --- EXCEPTION: SOFTWARE INFORMATION SQLITE DUMP
|
I get the same error. It would be helpful to also log the entity causing the error. --- BEGIN DEBUG INFO --- EXCEPTION: SOFTWARE INFORMATION SQLITE DUMP
|
I get the same |
Same error here, I just turned on verbose logging and this was one of the tasks it failed on
I'm using tasks.org on android for what it's worth. It seems like the task the error occurs on is random each time I remove and re-add the account. |
Hi 0chroma, |
This fixes the NoSuchElementException when creating new tasks https://gitlab.com/tasn/ical4android/-/merge_requests/2 I've also observed that with the above fix I can push new tasks to an existing collection, and I see those tasks being added to a collection in the web client. I can also create a completely new tasks collection and add new tasks both from KDE and android, and both are fetched and pushed correctly. However, I can not fetch new tasks created from KDE on android, with the above fix... |
Does anyone in this issue still have problems with the latest update, v2.4.3? |
I am no longer getting this issue thankfully. |
It's fine on my side too. |
Unfortunately, EteSync app (version 2.4.2) on Android 12 throws errors on attempted task sync (prior to that, a task was added to an existing task list in OpenTasks).
The error log is being uploaded to the developers with reference to this issue number.
Am I doing something wrong or is this a bug?
The text was updated successfully, but these errors were encountered: