Hi,
Ik happens more and more that Arc Editor starts eating my battery and the phone is warm. App restart solves the issue. This morning I hardly used my phone and suddenly almost 30% of my battery is gone.
I hope you can find this one.
Let me know if I can help in some way.
Sietse
This is my daily usage graph:
I actually took a look at the scheduled task earlier today. Arc Editor says it’s running the activity type model updates, and it took multiple hours to do this task.
Curious! Ok, I’m on it.
My first hunch is that yeah it’s the new system of catching up on overdue scheduled tasks while the app is in the foreground. Which means it’ll only be temporary - those things should be caught up by now.
And also if that’s the case, I can just change the “do it in the foreground because it’s overdue” threshold to be ~2 days instead of 1. Give iOS more of a chance to do the work in the background while plugged in to power.
But I’m also suspicious that it might be entirely unrelated, and some new mystery bug. I’ll… keep an eye on it 
Could you check the log files if you see any indication if the background tasks are running overnight for you?
Also, what does the “Scheduled Tasks” say in the Debug Info section?
Things are back to normal today.
Yesterday the app was next to unusable cleaning up the timeline. It was hanging regularly, and after opening the gui, the battery usage started - even when closing the gui. Restarting the app without opening the gui recorded normally, but opening the gui seemed to trigger power usage.
In the debug screen I saw a lot of activity. There were a lot of pending tasks, i saw that ticking them removed them from the list. After cleaning the list, the app started behaving normally.
Hope this helps.
Sietse
I actually couldn’t even view this particular log file. The spinner has been spinning for a while. Curiously I can easily open all other log files, just not this one.
Yeah that’s my expectation at this point. That the main problem was with those of us who migrated to Arc Editor before the new “do catchup in the foreground on overdue scheduled tasks” feature.
Once that catchup work has been done it doesn’t need to be done again. Or rather, if it falls behind again the catchup will be only a tiny workload, that should finish in seconds.
So the big nasty energy/battery hit should be a once off, and only for those of us who got in on Arc Editor before the new catchup feature.
If we do see high battery drain again though, after this point, that’ll be something new to investigate! It can happen from time to time, when some weird bug slips in and something ends up doing excessive/redundant/wasteful work that it shouldn’t.
Unfortunately, it happened again this morning. When opening the Arc Editor App for cleaning up de day before, the app was not very responsive, and started eating my battery. After a few restarts it finally started behaving again.
I have two screen recordings showing the repeated actions (I cannot upload here), here is a screenshot of one of them:
It keeps on running the tasks until I restart the app.
Hope this helps.
Sietse.
@vogon1 I see from the screenshot you’re on build 36. Build 37 went out four days ago. Make sure you’ve got auto updates turned on in the TestFlight app!
Though for the backlog showing in your screenshot, that’s unfortunately an issue that’s still present in 37. And I’m on it!
That one shouldn’t cause excessive battery drain. Though I’m not confident it definitely won’t. But either way it needs to be fixed, and I’m actively on the hunt.
For reference the issue number on that is BIG-293. So if you keep seeing that problem happening a week or more from now, you can slap me over the head with a sign with BIG-293 written on it, “Matt why’s this one still unresolved?!” 
