with DAVx, down sync is working, up sync is not - unless Tasks are enabled #105
Replies: 2 comments
-
Hello @SirLaffalot ! Regarding the basic problem: The split to select different apps for journals and tasks might be done in the future, but currently there is no specific plan for that. Maybe @rfc2822 or @devvv4ever can tell if this is on the roadmap. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the response. I thought it was something about the DAVx
choices.
Just to be clear on priority (especially for @rfc2822 or @devvv4ever) :
it's not super important ...
I really like OpenTasks' UI on Android. OT has a way to rapidly build
checklists under a task (but they don't have subtasks). I understand
everyone has different preferences of course. I worked around my
preference by adding a Shopping List
(https://github.com/SecUSo/privacy-friendly-shopping-list) to my phone,
which is what I mostly used sublists for anyway.
As of now, I use jtxBoard for journals and tasks, and the shopping list
app for those other lists. So the other issue I haven't yet solved is
finding a nice desktop app for archlinux that handles sub-tasks.
Thanks for all the great work on this app (and DAVx).
…On Wed, 2022-08-17 at 14:45 -0700, Patrick Lang wrote:
Hello @SirLaffalot !
Thank you for the issue description and logcat! This exception is
definitely an undesired behaviour, I will check that issue in
https://gitlab.com/techbeeat1/jtx/-/issues/309
Regarding the basic problem:
Currently DAVx5 only allows setting one task provider which is either
tasks only or tasks+journals. It is currently not possible to
synchronise for example tasks with Tasks.org and journals/notes with
jtx Board. The error message that you got seems to be independent of
the actual problem (the problematic method here just checks if the
synchronisation is currently running to show an indefinite progress
bar in jtx Board).
The split to select different apps for journals and tasks might be
done in the future, but currently there is no specific plan for that.
Maybe @rfc2822 or @devvv4ever can tell if this is on the roadmap.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
The issue is that I preferred OpenTasks tasks. So while the permission in DAVx Integration is set on (the slider) for both jtx and opentasks, the preferred app (radio button) is OpenTasks, not jtx. The down sync worked perfectly, but the up sync failed.
When I add a new Journal entry in jtxBoard, even forcing a Sync in the menu, and a Sync in DAVx, the new Journal entry does not get uploaded. There is some error - see logs attached here.
On the other hand, if I go back to DAVx and pick the radio button to have jtxBoard as my preferred tasks app, then the up sync works.
Is this really the desired behavior? What if I only wanted to use jtxBoard for a diary (vjournal)?
Android 11, LineageOS 18.1, with microg - no Google services.
jtxBoard 1.02.03-rc03.ose
DAVx 4.2.2-ose
Server is Nextcloud with vjournal enabled.
The thrown error is:
[08-07 14:32:23.313 13336:14792 W/Binder]
Caught a RuntimeException from the binder stub implementation.
java.lang.IllegalArgumentException: context is null
at android.accounts.AccountManager.get(AccountManager.java:458)
at at.techbee.jtx.util.SyncUtil$Companion.isJtxSyncRunning(SyncUtil.kt:41)
at at.techbee.jtx.ui.SyncFragment.onCreateView$lambda-1(SyncFragment.kt:51)
at at.techbee.jtx.ui.SyncFragment.$r8$lambda$FWZhkonV4SiR4HYKt7-XH4tsNxg(Unknown Source:0)
at at.techbee.jtx.ui.SyncFragment$$ExternalSyntheticLambda0.onStatusChanged(Unknown Source:2)
at android.content.ContentResolver$2.onStatusChanged(ContentResolver.java:3594)
at android.content.ISyncStatusObserver$Stub.onTransact(ISyncStatusObserver.java:84)
at android.os.Binder.execTransactInternal(Binder.java:1159)
at android.os.Binder.execTransact(Binder.java:1123)
logcat_08-07-2022_14-33-36.txt
Beta Was this translation helpful? Give feedback.
All reactions