Edit: I made it an activity and now it’s an inaccessible activity in 2025, I guess I’ll just have a bad data point then
This error is also similar to the merging of the new arc recorder app occasionally causing certain events to be super long because of time stamps being merged in the wrong order
I’m pretty sure it happens when the main app loads all the new data from arc recorder into a single event since I can fix it manually
As a general principle, I’m against deleting data. If it’s real data, it should exist in the database. But yeah, there’s a handful of cases where deleting data really is necessary. This looks like one of them!
Not quite sure of the best way to handle it, but I’ll add it to the todos. Hopefully once I get a chance to work on it a sensible solution will present itself.
Unfortunately I still don’t have a good idea for how to work around this one There’s possibly a way to deal with it by editing the JSON in the backups to mark the data as “deleted” then reimporting it. Which… theoretically should work. But it’s something I’ve never tried. But yeah… that does make sense. I don’t immediately see why that shouldn’t work. Hmm…