This build includes a database table rebuild for the timezone fix. On large databases this migration may take several minutes — please let it complete.
Hi Matt, I just found the Arc Editor need new subscription, will Arc timeline permanent subscription user become Arc Editor permanent free, or need to purchase a new subscription?
I had an issue with TestFlight updates so I had to delete Arc Editor completely and reinstall from TestFlight. I found that there is now an import experience from Arc Timeline right from the onboarding flow. That’s great! The import did seem fairly slow though, perhaps a bit slower than earlier betas? I didn’t keep track of the time precisely but it felt slower.
@hutudaxian Arc Editor is part of the Arc Family of apps, which all live under the same subscriptions. So no new subscription required!
Your existing Arc Timeline subscription should carry over, but at this point in the beta there’s one case where it might not, so probably that’s what’s happened to you.
But not to worry. For TestFlight builds the subscriptions are all fake - no money involved. So you can just do a Lifetime purchase and you’ll see it says something like “Sandbox” or “TestFlight” during the purchase flow. That’ll get you in 
Hm. It shouldn’t have changed at all. Or at least, it didn’t change in any of my timings in testing…
Maybe the phone got a bit too hot and throttled itself, slowing things down to avoid overheating. That could be it. That’s my best guess anyway.
Oh, do you have Arc Editor’s backups setting turned on? The restores from backup are about as fast as migrations from the old app, and have the benefit of restoring from Arc Editor’s higher quality data. In future you’ll definitely want those backups to restore from, for sure.
I saw the subscription screen as well. Tried to restore (since I have lifetime) but didn’t work.
Then I force quit the app.
Now I‘m stuck at this screen and it doesn’t go away even if I let it open for an hour.
The strange part is that in the iOS app switcher I do see the subscription screen, but once I actually open Arc it will show me the black database screen again.
Very strange.
What to do to fix this?
@patrickplaggenborg For the subscription screen, you’ll need to do a fake purchase. Because it’s a TestFlight build all purchases are fake - no money involved.
For the stuck migration screen, that’s a more difficult problem! That’s completely unknown and unexpected. Could you get the log files from the app by connecting to the phone via Finder? (or the Windows equivalent on Windows).
In Finder, browse to the phone, then Files, then under Arc Editor grab the Logs folder from there and drop it somewhere on your computer. If you could then perhaps email me (matt@bigpaua.com) the appropriate log file(s), I’ll have a poke through them and look for possible explanation.
Judging by your screenshots you’re on a newer model phone (Dynamic Island, not notch) so that migration should’ve completed within less than 5 minutes. So being stuck for an hour is definitely not expected! Hopefully the log files will tell us something.
In the meantime you could try swiping the app closed and relaunching, then leave the migration in the foreground for as long as you can. Perhaps there’s some problem on the phone where the migration is still working correctly but will take absurdly longer than it should. Or perhaps it really has failed somehow (which the log files should tell us). If it’s just running super slow, then restarting the app should get it through eventually, one would hope.
@patrickplaggenborg One more question: When you tried the refresh button on the subscription view, did the view change when you tapped it? Did it appear interactive? Or did the view appear stuck/frozen, such that your taps did nothing?
I don’t think anything happened when I pressed the refresh button. And I did not want to pay for Lifetime again, and I didn’t know at that time that purchasing in the test version would not be charged. (That’s only stated in the fineprint in the actual iOS purchase dialog, not before).
I force quitted the app again and it took a few minutes but eventually it went through and ended up at the purchase subscription screen again.
This time I just selected lifetime and ‘test purchased’ it and it went through. So it’s up and running again.
In the meantime I also checked the logs but it did not show anything but “[08:35:03.041] [LIFECYCLE] ArcTimelineEditorApp.init() v1.0 build 46 (previous: 46)” repeated in the last few log files.
Either way, all good now.
Thanks for your help!
Phew! Glad to hear it self resolved!
Yeah, that matches my suspicion.
What I think might have happened there is the app had updated in the background at some point, which would have led to it showing the subscription view. You didn’t see it at that time, because it was in the background. But iOS took a screenshot of the app, as it always periodically does, to have a placeholder to show on screen when apps are resuming from suspend or other various situations.
Sometimes when you open an app you’ll see some stale / outdated view, which doesn’t do anything when you try to interact with it, then it soon after (hopefully) disappears. That’s iOS showing that placeholder screenshot while the app is starting up or coming out of suspend or some such. Looks real, but isn’t.
So when you say nothing happened when you tapped the button… I suspect that’s what you were seeing. The UI should have at least changed in some way, to give you some feedback.
Anyway, what the app would actually have been doing while iOS was showing you that fake screen for too long was the migration. It would have already been busy doing the big nasty migration. You should’ve been seeing the migration view at that point, but iOS had different ideas.
So when you swiped it closed you’d actually stopped the migration part way through. Which… luckily is harmless! SQLite is designed to roll back and discard its work in that case - no harm done. But I suspect when you came back again on second attempt, that second attempt was much slower, because… SQLite was cleaning up from the first partial attempt? I’m not totally sure.
But yeah, I think that’s the most likely explanation. An unfortunate series of events and misdirections.
Oh and the situation that could have led iOS to think it needed to show that fake placeholder screenshot for too long, that’s been fixed in the new build 47. So thankfully that totally misleading situation shouldn’t happen again!
