Thanks @mercuryfrost! Yeah it’s much more pleasant to use eh. All modern technologies and techniques, none of the decade of old cruft in the old app 
Hi @bmusgi!
I think probably the best move will be to delete the new app (keep the old app installed though!) then reinstall the new app so it gets a fresh database, and do the migration again from the old app.
That way you’ll get all the complete data from the old app imported, and can continue on from there.
Hi @obenn! Unfortunately the old app didn’t work fine without the indicator showing. Turning it off still causes data gaps (that Arc Recorder has to pick up from, if installed) and results in usually higher energy consumption / battery use.
Yeah, it would be great if Apple gave us the option to turn it off ourselves per app. That would be ideal. But until then, this is the situation as it stands now. Sorry about that!
I understand… do you think you could offer an option to revert to that mode for those who prefer it? Then everyone would win.
@plantemathieu Unfortunately not. This battle is lost.
Apple already cost me significant money more than once, due to having that option in the app. Each time they updated iOS with undocumented changes that intentionally broke things and hurt users because of that option’s presence I got angry emails, aggressive 1 star reviews on the App Store, lost subscriptions, high stress. It’s all extremely uncool and harmful to my goals of staying housed and fed.
At this point the only path forward is for Apple to relent and change something on their side. I’ve already taken enough punishment over this one in the past. It’s not a fight I can afford to have again.
It’s been working great for me for over a year! Really happy with it.
1 Like
Forgot if mentioned. With 4.x, visits to larger locations such as a big store might be marked as multiple visits with Car in between. Before it would reliably be walking yet seemingly I have to fix it often.
Related, sometimes I might mark such as stationary such as for home with weird gps info. Not sure how that affects accuracy such as if sometimes a location is listed multiple times with walking in between or other times I change such to stationary to make it one visit. If LokoKit2 can account for such over time, eg I find myself from what I recall often needing to still conform Home.
I wouldn’t worry about it. As long as you’re shaping the timeline so that it makes the most sense to you, that’s correct behaviour.
The app is learning at all levels. All confirmations, corrections, edits, they’re being learnt from. And then it knows to attempt to auto match those patterns in future. So if you like visits to certain places broken up, it’ll be learning that. If you prefer them as one big visit, it’ll be learning that. And likewise the activity type assignments you use, it’s learning all those patterns too.
For this, are you seeing the Home visits listed as “unconfirmed” or “uncertain”? The two have very different meanings.
Unconfirmed: The app is letting you know which ones haven’t been confirmed yet, so that you can lock in the assignments. Then once locked in with confirmation the auto assignment systems can’t change that later.
Uncertain: This is the app telling you “I’m not sure I got this right; my confidence is too low”.
For your Home visits they should almost all be falling under “unconfirmed”, not “uncertain”.
@matt Here I am: even though the trial week has ended, the new app has still carried over the annual subscription from the old one… all good!
1 Like
Glad to hear that @Leevio! Principle proven 
So the bulk of the problem seems to have been:
- The new app and old app weren’t immediately syncing up on first launch (something to do with App Store or RevenueCat caching, no doubt)
- The new app doesn’t tell you that it’s picked up the old app’s details, once you’ve already got a trial underway. So even though it’s probably all good at that point, there’s no way of double checking until the trial ends. Oops!
Anyway, glad to hear it does self resolve in the end! 
1 Like
First off — huge congratulations on Arc Timeline 4. The rebuild feels polished and the new recording engine is noticeably snappier.
One feature I relied on heavily in the old Arc Timeline that I can’t find in v4: the ability to export GPX files and share timeline pictures (the visual day/route summaries). I used both regularly — GPX for importing trips into other apps, and the timeline images for sharing routes with friends or just keeping a personal visual log.
Would love to see these make it into Arc Timeline 4. Happy to provide more detail on how I used them if that’s helpful for prioritisation.
1 Like
Hi @yegorhayk89! Thanks for the kind words
For GPX export and timeline image export, those have been getting lots of requests! So they’re definitely filed and prioritised, for getting into app updates as soon as possible.
I’ll double check the issue numbers and priorities now… Ok for GPX export that’s BIG-396, high priority, filed for the 1.1 update. For timeline image export that’s… BIG-387, also high priority and filed under 1.1.
Whether they both make it into the v1.1 update or not, I can’t be sure. Release shipping tends to get pushed around by a bunch of requirements each time - time pressure, quick bug fix shipping, etc. But given both of those are frequent asks on the forum, they’ve got a good chance. And if not in v1.1 then likely v1.2, not too long after.
Where do I find GPX export? In the old version it was in settings/backup, import & export. But in Arc 4 there seems to be only backup and restore?
Hi @krst!
GPX export isn’t in the new app yet. But it’s very high priority to get added soon!
We’re prioritising the auto daily/weekly exports first (issue number is BIG-292). Then the plan is to get the other export types in to a following update. But from your description it sounds like you’re wanting the auto exports, so that’s all good! That’s coming first, and already prioritised as urgent to get in 