Moving a subtask in edit mode, crashes activity, loses data.

[navid-zamani]

Try this:

1. Create a new task with two subtasks and save it.
2. Now go into that task, and edit the second subtask. (No need to actually change anything for the crash to happen.)
3. While still in edit mode (where the delete button is displayed [and awfully close to the text, threatening to insta-vanish your subtask on a mistap]), move the second subtask to the top.

Result:
The task view crashes/exist. All changes are lost!
(Doesn’t seem to happen all the time, but when one is quick, it happens almost always.)

Expected result:
No crash. The subtask ends up there.

Suspected cause:
Since I had this happen with especially long subtask texts too, and the calculation where the subtask should end up is generally quite wonky and often off by a line or so, I suspect that it’s that bit of code that crashes.

Version: 1.4.2 (The latest one in F-Droid)
OS: Android 10 (EMUI 10.0.0.202)

[navid-zamani]

Oh man, and again I lost all my subtask edits, and can’t remember what I entered. This ia becoming a real problem.

I wish I could help out, but the way Android structures apps seems insanely over-engineered to me. I couldn’t even find where it handles the drag release event for all the busywork code in there, and Android Studio is no help either. Much respect that you can even handle this mess of a platform.

[navid-zamani]

For anyone looking for a solution: I found a workaround:
While still dragging, press the square button on the bottom of the screen (the Android task switcher) twice, to switch to another app. (The second tap feature does not exist on older Android, but it should still save you.) Then switch back. Your dragged subtask will leave edit mode, and be de-focused without being lost. It will not be where your finger was, due to the positioning bug, but it will be close.