When i change task details or add new task in app, info on desktop widget won't update. In same time task list and tasks details in app is ok. This issues retry not often, but helps either removal and adding widget on desktop or restart phone. I use tasks for caldav and ownclowd server on sony xperia zl with android 4.2.2. Info on server after sync in caldav is ok to. Click on buton update in app don't help.

Hello,

I'm using DAVdroid 1.6.5-play on my Samsung Galaxy A3 (2017) with Android 6.0.1 to synchronize Calendar, Contacts and Tasks with nextcloud 12.0.1.

Every time I close the OpenTask app manually and open it again, all tasks are gone. This also happes again and again by itself after some minutes. Then DAVdroid starts to synchronize them again.

I already reinstalled the OpenTasks app and DAVdroid.

Another phenomenon today: All tasks twice in OpenTasks app. They all disappear again when I close it. Then synchronization as usual...

• [x] CustomizedDefaultFieldAdapter: Introduce customizable default values (new interface Default) in order to provide different defaults for DUE (should be after START: new class DefaultAfter) and START (should be before DUE: new class DefaultBefore).
• [x] New constraint After: requires that a value is after another value (e.g. DUE must be after START); if constraint is violated, set value to the default (DefaultAfter); similar to the old NotBefore.
• [x] New constraint BeforeOrShiftTime: requires that a value is before another value (e.g. START must be before DUE); if constraint is violated, then the reference value (e.g. DUE) is shifted with respect to the duration of the task.

With the two new constraints, we prohibit DUE=START and therefore fix #262. The constraint BeforeOrShiftTime is a tradeoff between shifting always (cp. constraint ShiftTime) and shifting never (cp. constraint NotAfter); maybe this is sufficient in order to close #197.

Todo Agenda is a widget that displays calendar events and tasks, and it can display tasks from OpenTasks. (I wrote the support for tasks, but I'm not the maintainer.)

It would be nice if the widget were updated whenever a task is added/changed/completed/etc. From what I've gathered, a PROVIDER_CHANGED broadcast is sent in these cases, but on Oreo and later it's limited to OpenTasks' package only:

https://github.com/dmfs/opentasks/blob/e711e6ea630162be184f5a0e77ac115145a291a3/opentasks-provider/src/main/java/org/dmfs/provider/tasks/TaskProvider.java#L1322

I'm not sure why that limitation (and the comment about figuring out how to do it in 8+). I've tested with a simple app that sends an equal broadcast (without specifying the package) and the widget was able to receive the broadcast.

Could that setPackage be removed, so that any app interested in knowing about changes in tasks can be notified?

Steps to reproduce:

• Create a new task and set due
• Save task
• Edit task and update due date
• Press SAVE
• App crashes and looses all changes

08-01 16:20:32.583  7833  7833 D Profiled: Time spent in Update: 2 milliseconds
08-01 16:20:32.584  7833  7833 D AndroidRuntime: Shutting down VM
08-01 16:20:32.585  7833  7833 E AndroidRuntime: FATAL EXCEPTION: main
08-01 16:20:32.585  7833  7833 E AndroidRuntime: Process: org.dmfs.tasks, PID: 7833
08-01 16:20:32.585  7833  7833 E AndroidRuntime: java.lang.IllegalArgumentException: _ID can not be set manually
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.processors.tasks.Validating.verifyCommon(Validating.java:57)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.processors.tasks.Validating.update(Validating.java:2)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.processors.tasks.Validating.update(Validating.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.TaskProvider.updateInTransaction(TaskProvider.java:20)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.SQLiteContentProvider.a(SQLiteContentProvider.java:28)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.d.value(Unknown Source:10)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.utils.Profiled.run(Profiled.java:5)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.SQLiteContentProvider.update(SQLiteContentProvider.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.provider.tasks.TaskProvider.update(TaskProvider.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.content.ContentProvider$Transport.update(ContentProvider.java:361)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.content.ContentResolver.update(ContentResolver.java:1731)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.tasks.model.ContentSet.persist(ContentSet.java:5)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.tasks.EditTaskFragment.saveAndExit(EditTaskFragment.java:27)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at org.dmfs.tasks.EditTaskFragment.onOptionsItemSelected(EditTaskFragment.java:2)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.fragment.app.Fragment.performOptionsItemSelected(Fragment.java:3)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.fragment.app.FragmentManagerImpl.dispatchOptionsItemSelected(FragmentManager.java:4)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.fragment.app.FragmentController.dispatchOptionsItemSelected(FragmentController.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.fragment.app.FragmentActivity.onMenuItemSelected(FragmentActivity.java:3)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.app.AppCompatActivity.onMenuItemSelected(AppCompatActivity.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.view.WindowCallbackWrapper.onMenuItemSelected(WindowCallbackWrapper.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.app.AppCompatDelegateImpl.onMenuItemSelected(AppCompatDelegateImpl.java:4)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:2)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:4)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.widget.ActionMenuView.invokeItem(ActionMenuView.java:1)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at androidx.appcompat.view.menu.ActionMenuItemView.onClick(ActionMenuItemView.java:2)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.view.View.performClick(View.java:6617)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.view.View.performClickInternal(View.java:6594)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.view.View.access$3100(View.java:778)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.view.View$PerformClick.run(View.java:25910)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:873)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:99)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:193)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6739)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
08-01 16:20:32.585  7833  7833 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:859)
08-01 16:20:32.587  3405 10602 W ActivityManager:   Force finishing activity org.dmfs.tasks/.EditTaskActivity
08-01 16:20:32.592  3405 10602 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1005 com.android.server.am.AppErrors.crashApplicationInner:469 com.android.server.am.AppErrors.crashApplication:392 com.android.server.am.ActivityManagerService.handleApplicationCrashInner:15762 com.android.server.am.ActivityManagerService.handleApplicationCrash:15728 
08-01 16:20:32.593  7833  7833 I Process : Sending signal. PID: 7833 SIG: 9

… them when new task is selected. #624

@dmfs It took some time to get everything correctly working here but it looks good now for me.

There is a field in TaskListActivity now to save the last used color, so it can be used while the selected task is loaded. It is useful upon starting up the app and after rotation.

EmptyTaskFragment also has a hint color now, so we don't change back the color to primary after a deletion but keep it as it was for that task.

ViewTaskFragment can be further simplified after these changes, I've created a separate ticket for that: https://github.com/dmfs/opentasks/issues/628

This pull request should fix https://github.com/dmfs/opentasks/issues/609 and https://github.com/dmfs/opentasks/issues/525, too.

I've created 3 new classes for reading arguments from Bundle here, in order to read the color argument. They help now, but the plan would be to remove and replace them once the full solution from boxed-bolts is available, since that approach is much better and more general.

The title is not shown when viewing task, see attachment. This was reported for Android 6.0.1 (but was also there on Android 5) with Cyanogen OS 13.0. Please fix this. Contact me if I can help testing.

Running latest beta from playstore. Modifiying the task list for an existing task creates a task in the new task list but also keeps the task in the old task list. Expected behavior is simply to have the task list modified for the task.

I am using DavX to sync my tasks with my Synology NAS. If i do a local change in Opentask DavX beginns to sync about every 5 seconds and the phone beginns to vibrate in the same interval. If I uninstall Opentask the syncloop is stopped, thus I think its a bug in Opentask and not in DavX.

There seem to be many people experiencing the same problem, if you look at the reviews in GooglePlay.

I have recognized that the App OneDrive gets stuck in a syncloop too. At least the notifications implies that, because they appear and disappear approximately every second. Can there be a connection to the bug in Opentask?

The widget does not show synced CalDAV data when app is closed. After opening the app the widget data is not refreshed.

Removing the widget, then opening the app will display the synced CalDAV data. Additionally, I noticed that the app doesn't seem to really "sync" as in hold the CalDAV data between sync events, once you close the app, the data is gone until the app syncs again, which I'd guess is the root cause of the disappearing data in the widget.

Moto 5 Plus Android 7.0 OpenTasks 1.1.9 DAVdroid 1.6.5-play

Somehow the keyboard is preset to use lower case every time for the first word. I've never seen this in Android before, please correct this behaviour! :)

Hi dmfs/opentasks!

This is a one-off automatically generated pull request from LGTM.com :robot:. You might have heard that we’ve integrated LGTM’s underlying CodeQL analysis engine natively into GitHub. The result is GitHub code scanning!

With LGTM fully integrated into code scanning, we are focused on improving CodeQL within the native GitHub code scanning experience. In order to take advantage of current and future improvements to our analysis capabilities, we suggest you enable code scanning on your repository. Please take a look at our blog post for more information.

This pull request enables code scanning by adding an auto-generated codeql.yml workflow file for GitHub Actions to your repository — take a look! We tested it before opening this pull request, so all should be working :heavy_check_mark:. In fact, you might already have seen some alerts appear on this pull request!

Where needed and if possible, we’ve adjusted the configuration to the needs of your particular repository. But of course, you should feel free to tweak it further! Check this page for detailed documentation.

Questions? Check out the FAQ below!

FAQ

This draft adds the ability to display and adjust hierarchical tasks, i.e.

- [ ] test1
  - [ ] test11
    - [ ] test111
  - [ ] test12
- [ ] test2
  - [ ] test21
    - [ ] test211
  - [ ] test22
- [ ] test3
  - [ ] test31
    - [ ] test311
  - [ ] test32

will be displayed as: The left and right buttons are used to indend the item to the left or right. This is done rather hackish, as I am rather unfamiliar with Android Layouting. Maybe a swiping motion of the item would be better for choosing the level.

I downloaded the app through the Google Play Store, but the app doesn't open at all. Is there something I can provide you with for debugging?

System: Chrome OS Version: 97.0.4692.91 (current)

Apps: OpenTasks 11.12.3 > DAVx5 4.0-ose > Nextcloud 21.0.7 > Nextcloud App Tasks 0.14.2

When you make a (sub-)tasks with "-symbols, it shows up in Nextcloud with a escape character in front of it.

Expected: "

Actual: \"