Not sure how to share details but here is a link to an image of the task.
https://share.icloud.com/photos/0dygngsO7Lc4EnZon6nPCFU9Q
Does this help?
Yes, thanks for the info, @IanT.
According to your screenshot, your task has invalid start date. Currently start date on recurring tasks doesn't work properly. (This was a bug before iOS 13 but it got worse on iOS 13.) But your task seems to have start date later than due date (according to -7 hour duration shown). I'm not quite sure what may have caused it since you're not using start date in the settings.
Please try changing start date by going into 'Settings - General - Use start date' and edit start date to match due date or make it earlier than due date.
If you know how this task got this way, tell me back. Also if you have other tasks that crash, give me a screenshot like this too. And also please share how above procedure went.
Thanks!
I've seen a number of my tasks with -7h as you mention. Obviously I didn't set them up like that.
Do you live in GMT-7 time zone? This could be the reason. DB1 & DB2 had the issue of making wrong start dates when you add a new task.
I live in Vancouver so I would call it -8 but with summertime I guess it could be -7.
I enabled start date in settings. Went to the Task and changed the start date to now. Then I used the back button to go back to the list and save the task. It immediately crashed. When I relaunched the task still had the erroneous start date so I tried again and it crashed.
Ian
Does other tasks which are not recurring behave the same? You might need to make a new task for the one that's crashing.
So it seems not. Also this recurring one doesn't crash it.
A new repeating task with the same details doesn't crash it.
It seems like repeating tasks that's made in DB1, DB2 (PB1) is causing crash when your time zone is GMT-N.
There seems to be no particular way to resolve it. Current workaround would be adding a new one and delete the current one.
I'll keep an eye on it. Thanks!
So I’ve cleared the issue for now. It seemed to be my overdue items which are the ones I was trying to reorganise therefore giving the appearance that it was app wide. I created a new todo and couldn’t reproduce the issues. I noted that completing an item crashed the app but didn’t mark item complete. However rescheduling crashed the app but DID complete the reschedule.
So I rescheduled everything to today and then tried again.....everything was working.
Perhaps this forced the todos to the new database in the correct format?
Thanks for the info, @Themikeyd. It could be a possibility. It seems like there has been lots of changes in DB3 (PB2) under the hood.
1 Like
In my opinion, for now the best thing to do is if you are using the betas, just use the Reminders app for now. It's not that buggy. We don't know what changes Apple is making to the iCloud and Goodtask could still break again. Apple won't release their new APIs until the GM is released in late August or early September. That's when Devs can start fixing their apps for the new OS's.
From what Ive read on apple Dev site and in other forums, Apple is changing their iCloud, which is why beta.icloud.com exists and why many on Catalina beta and other betas are having iCloud issues. Once the GM or release releases come out and we hit the upgrade button in Reminders, we don't even know if Goodtask will continue to work or not. We have to allow the developer time to make changes and make sure everything will work with the new Reminders app and iCloud changes.
On a personal note, I love the time and energy that the Dev has spent on Goodtask, it's a great app and I think you forced Apple to change their default Reminders app to add sub-tasks and so much more. So thank you on a personal level...
1 Like
Thanks @sparkktv for the opinion.
If you're using iOS 13 beta and Catarina, it would be fine to use Reminders or GoodTask with or without the updating the database. Most of the bugs are gone now and current existing ones are that URL field is not showing and some unknown crashes (many of them are resolved in v4.7.3).
If you'd like to try and use new features on the Reminders app, you can use it.
If you want to use existing features of GoodTask, it'll be fine too.
I'm not confident of Apple opening new APIs but seeing changes of URL field (even if it's a bad bug) might be a sign of some changes that will come to current APIs.
If they're going to open some new APIs, they'll probably open it way before GM since it could have bugs and they'll need to fix them too.
Anyway when new API gets opened, I'll post how GoodTask will adapt them. Even if it doesn't get opened, there are plans for improvements in current status and related updates will come one by one. 
Don't forget that the most important thing is to get things done!
Thanks!
What happens if you set up a subtask in Reminders on IOS 13? How does it show on GoodTask? I tried to check myself, but the only device I've updated (iPad Pro Gen 1 12.9) refuses to let me create subtasks.
@denrael, currently subtasks are just shown as normal tasks in the list. If API gets opened, it can be changed. (Used to be not shown at all on previous beta builds but now it shows)
Normal tasks work, just wanted to make certain they did show. Now if I could just get my beta 13 to work. LOL
1 Like
A full reinstall of Beta 13 finally made Reminders behave as it should with subtasks and all so I can see how the interaction is between GT and R13. Given that you received no new APIs to take advantage of the enhancements (shame on you Apple), it's quite elegant.
1 Like