1.0 (build 47), 2026-03-30 11:13 (Bali)
Bug Fixes
- Fixed activity type model updates not running after the Build 46 database migration, caused by a database index being renamed during the table rebuild (BIG-379)
Iām asked to subscribe although I am subscribing to Timeline. Should I do something special? (I see no ārestore purchase ā¦ā)
Any timeline on moving recorder over to the new app. Iām going to delete and reimport my database I think after that
Currently the data is more complete in old arc because it just has more points
also any timeline on officially replacing the old app?
1 Like
@diligiant The restore button is the āreloadā button at bottom left. Though because these are TestFlight betas the purchases arenāt real - no money involved.
Once Arc Editor is on the App Store proper your existing subscription will carry over automatically. But for now you can do a fake lifetime purchase to get through. Itāll say āTestFlightā or āSandboxā at the top, to let you know itās not real.
1 Like
Are you meaning data gaps? Has Arc Editor been getting terminated?
Arc Editor / LocoKit2 record higher quality and higher frequency data than the old app. So in almost all cases the Arc Editor data will be preferable. Iād only consider doing a fresh migration from the old app myself if I had data gaps in Arc Editor that arenāt there in Arc Timeline.
For when things will shipā¦ Iām lining up to ship Arc Editor to the App Store as the final v1.0 maybe this weekend. All the work on Arc Editor is done for the release, and the only blocker is an Arc Timeline update, to point people towards the new app, and also to ensure existing subscriptions carry over correctly.
For Arc Recorder, Iāve got that planned for soon after the v1.0 release. Unlikely to be more than a week after v1.0 goes live.
Yeah it gets terminated more frequently I had a large data gap last week that the old app dealt with fine
Itās happened frequently enough that Iād want to do a fresh database migration on the update
The new app has issues underground which annoys me a lot since I use subways a lot but thatās ok, the data gap yesterday was a 25 minute road trip over ground
I too have noticed data gaps in the last 2 versions. Even in the function of importing from Apple Health workouts, while before he was able to import the entire workout (done with Apple Watch and then saved on Apple Health) of running now he sees me and I only care about some segments (5 minutes each when the training lasted some cases 40 minutes) then marking me data gaps. This problem did not occur before. In general I noticed a big worsening in the last two versions, Iāve been using arc editor in beta for many months and it had never happened to me.
I put screenshots in which you can see: 1) the data gap, the workout that is seen as 31 minutes and the two importable segments of only 5 minutes each. The result is that I can only import the two segments for 5 minutes and they remain without data for the rest.
Iām also noticing data gaps with the last versions. Arc Editor seem to snap on visits at known places and dismisses the leaving. Arriving at the next place seems to wake it up. Result are two visits, no track between.
For what itās worth, just another random anecdote, I also feel like the last couple of versions have been missing more things.
It doesnāt show as a āData gapā for me ā and the app doesnāt appear to have been terminated ā it just doesnāt wake up from sleep.
For example, it missed an entire 20-minute errand yesterday, showing me at home the whole time. 
Also I donāt know if you can adjust the weighting but whenever thereās bad data it really wants to make it stationary even when thereās a known type assigned
See below a bunch of points got assigned to a station even though itās flagged by the system as metro already
as someone who uses transit a lot the old one is just a lot better in these low accuracy GPS scenarios than the current model which is why when you move over Iād be reimporting regardless when you make the change
Hm. Definitely terminated? Youāre getting uptime reset to zero in Debug View, and fresh debug log files?
The reason I ask is because Iām tracking a couple of issues that are causing the app to not get new timeline data / new timeline items when it should. Both happening while the app is still alive, not terminated.
If though the app is definitely being terminated, then thatās something separate that Iām not aware of, and should also be tracking separately!
For me Arc Editor is never terminated by iOS. It stays alive for as many days as I let it. With it only being restarted when Iām doing development testing. So if itās getting terminated regularly on other peopleās phones Iāll ideally want to figure out why thatās happening.
I shouldāve done some testing for this when I was still in Bangkok last month. My bad.
I tend to always have my bicycle with me, so I donāt take trains all that often these days. But I really need to get that testing done when Iām in a city with underground rail! Actually Iāll be back in Bangkok late next month. Can set aside some time then.
@Helge @kronk Sounds like youāre both experiencing problems Iām tracking at the moment. I described them in part in my reply above to @Hutima.
Thereās two separate problems. First is that sleep mode is too āstickyā sometimes, with recording not restarting early enough due to the algorithm being too strongly biased towards staying asleep.
The second is a more difficult one. What Iāve been seeing over the past week or so is that sometimes iOS stops delivering any new location updates to the app, for 30+ minutes. The app is still alive, still doing wake ups, still requesting data, but not getting any at all.
That one is almost certainly an iOS bug. But Iāll do what I can to find a way to work around it, until Apple fix it on their end.
Oh and yeah, Iām seeing missed recording in my own data for both of those reasons. Sometimes itās still getting location data but sleep mode is refusing to let go. And other times itās simply not getting given any new data 
Anyway, Iām working on it! I added a bunch of debug logging yesterday to see if I can catch both of them in the act in more detail.
1 Like
@Leevio From the screenshots that one looks like a problem with the workout data - location data is missing.
Try opening up the workout in another app, to see what location data itās showing. The Apple Fitness app should show you a map of the location data it contains, and also under Workout Details show you any splits/segments.
Your workout screenshot is showing that the workout only has two 5 minute segments with location data. The rest of the workout doesnāt contain importable data. So the key detail will be whether other apps are seeing the same problem of missing location data, or whether thereās something about that workout thatās causing it to be misunderstood by the importer.
@matt I had already checked and both in the apple workout and health apps, and in other apps that race has all the location data on the map, complete, each segment. The other strange thing is that I divided that workout into segments but not for 5 minutes; however all 33 minutes have the data and I see the path on the map. I tried to open that workout also with other apps (Healthfit, rungap) and the route data is complete. Before (until a couple of versions ago) not even this problem had ever occurred, to me it appeared together with the data gaps similar to those reported by other users in this discussion.
Ah not sure maybe not then since it picked up automatically at some point Iāll have to check again if I notice an issue
the old app though recorded data fine which is why Iāll be reimporting data whenever you finalize
@Leevio Could you send me screenshots of the segments in other apps, and their associated location data on map views? It would be good to see that in detail, to better assess. Thanks!
@matt Here are the screenshots where you can see that in the Apple workout app the corresponding map covers the entire path actually made, there are three segments: two 5-minute preset (it was a workout preconfigured by Apple Watch) and then a 23-minute āfreeā segment. Even from the Healthfit app you can see that the map is complete and covers all 33 minutes of running BUT the segments recognized here are only the first two for 5 minutes leaving out the āfreeā segment! As it happens in Arc, only that Arc does not care about the data of the run out of 2 segments of 5 minutes while Healthfit (and also other apps) does as you can see from the screenshots of the map. Those with a dark background are the screenshots of Apple WOrkout those with a light background of the Healtfit App.
It seems that when there is a pre-configured workout in the app only the programmed segments are taken and the rest of the free training are ignored in the list of segments, but while the other apps trace on the map also the free training Arc is limited to the official segments of the workout, despite the fact that the workout has gone ahead and has been recorded; I hope I have explained myself!
I add that a few months ago, I found an example from January, instead Arc also imported the āfreeā segments of a structured training, not only the āofficialā segments I just checked.
1 Like
Thanks for that @Leevio! Most helpful.
So it looks to me like your predefined workout has two 5 minute segments? And then after that if you continue the workout the data that follows that isnāt put inside a segment - itās just left unattached in the workout.
Though Appleās Fitness app is presenting it as though it is a proper segment. While HealthFit doesnāt.
Anyway, if that description sounds right to you, then I think Iāve got a clear path to fixing the import code, so that it can catch that location data outside of a segment.
Thatās right, Mattāyou got it! But when the pre-set workout includes, for example, a second segment with no time limit, of course everything counts and Arc is able to import all the data . I realize this is a special case, but I wanted to chime in, and I can see that youāre paying close attention to these details as well.
1 Like
Excellent. Ok that means the fix is pretty clear, I think. Iāve got it filed in the tasks now, and will hopefully get that fixed up in v1.0.1, coming soon after the v1.0 release.
1 Like