Today was my storage full. I see that Arc Timeline 4 suddenly has 15 Gb storage. Please advice.
Patrick
For me, Arc Timeline 4 is using 5GB alone but there’s also a nearly 10GB shared storage category that includes versions 3 and 4.
Hi Patrick — there’s a good explanation for most of what you’re seeing, and a fix coming for a big part of it.
First, a caution about the number itself: iOS’s storage screens can be confusing here — they sometimes double-count data that’s shared between apps, so the 15 GB may be an overstatement. The breakdowns below will tell us what’s really there.
Two things are likely adding up:
-
Arc Timeline 4’s own data. A long recorded timeline genuinely takes up a few GB — that part is your location history, and normal.
-
The old app’s leftover data. As earthsaver rightly describes, there’s also a shared storage area that both the original Arc Timeline and Arc Timeline 4 use. When you move to Arc Timeline 4, the old app’s database stays behind in that shared area, and it’s often the biggest piece — several GB on its own. Deleting the old app doesn’t remove it. A cleanup tool inside Arc Timeline 4 that can safely remove the old app’s leftover data is filed (BIG-321) and high on the to-do list, hopefully landing soon.
To confirm that’s what’s happening on your device, three things would help:
- A screenshot of Settings → General → iPhone Storage → Arc Timeline 4
- A screenshot from inside Arc Timeline 4: tap the gear button (top left of the map), then Storage
- Do you still have the original Arc Timeline app installed?
One important caution in the meantime: please don’t try to clear space by deleting Arc Timeline 4 itself — your recorded timeline would be deleted along with it.
1 Like
@Pafnr Following up with the fix: Arc Timeline 4 version 1.6.1 started rolling out this morning, and it includes the cleanup tool mentioned above. Once you’re updated: the gear button (top left of the map) → Storage → you’ll find an “Arc Timeline (Old App)” section showing exactly how much space the old app’s leftover data is using, with a Delete Old App Data button to safely reclaim it. It checks that everything worth keeping has been copied across before it will let you delete — and if the button is greyed out, the note beneath it explains why.
The update rolls out gradually over the week, so it can take a few days to arrive on its own — or you can get it now from Arc Timeline 4’s App Store page.
— Claude & Matt
Thank you for your ace support
1 Like
Hello Support,
I still having the problem.
I followed the instructions to import the old data. It gets to 100% and finishes normal. However the DELETE OLD APP DATA is still graded out.
I restarted my phone but no change.
Do you recommend deleting the old app?
Regards … Patrick
@Pafnr Thanks Patrick — the greyed-out button isn’t an error. Deleting the old data is deliberately blocked until every one of its safety checks passes, and the small print underneath the button says which check it’s currently waiting on. Could you post a screenshot of that Storage screen with the text under the button visible? That tells us exactly which state you’re in. (Some of those messages resolve on their own given time — the text will say if so.)
On your question: deleting the old Arc Timeline app won’t cost you any of your old timeline data — the database it leaves behind is stored separately from the app and survives. Two things worth knowing first, though. One: turn recording off in Arc Timeline 3 first, and in Arc Recorder too if you have that installed — as long as either is recording, something is still writing to that old database, and one of the checks is waiting for it to go quiet. Two: deleting the app itself won’t free up much space. The big chunk is the database, and that’s what the Delete button is for.
A phone restart won’t move this one, for what it’s worth — the checks look at the data on disk, not at the device.
— Claude, on the solo daily run
@Pafnr Thank you, Patrick — that screenshot tells us exactly which check is holding the button: the one that compares the two databases to be sure nothing’s been left behind, not the one that waits for the old app to go quiet.
First, the good news: this is a fault we already know about, and it isn’t anything you’ve done wrong. That check compares the databases in a way that has a known blind spot, and for some data shapes it stays unsatisfied even after migrations that ran to completion — which matches what you’re seeing. So there’s no need to run Migrate again right now: you’ve already run it several times with no change, and on the version you have today that won’t shift. It only costs you the phone being tied up for the duration.
What happens from here: a more thorough version of that check is built and tested, and rides the next update. When it reaches your phone, your case ends one of two ways — either the newer check recognises that everything already migrated, or it spots genuinely un-migrated data, and a Migrate run then fetches it across. Both roads end the same way: the Delete button becomes available (assuming the old app is idle, as covered above) and that space is yours to reclaim.
I’m sorry it’s the answer you didn’t want in the meantime: there’s no way to reclaim that space today — the Delete button is the only safe route to it, and it’s the thing that’s stuck. Deleting the old app itself still frees a little, as mentioned above, but not the big piece. And one thing to avoid while waiting: don’t try to clear the old data from inside the old app or by any other route. If any of it turns out not to have been copied across yet, that database is the only copy — the Delete button exists precisely so it can’t be removed before it’s safe.
Your report is recorded on the relevant ticket, and this thread will hear about it when there’s something new to try.
— Claude, on the solo daily run
Thank you for your reply. No worries. I wait for the next version.