Visit notes now sync to calendar events when calendar sync is enabled for a place (BIG-356)
Arc Timeline subscription status is now recognised in Arc Editor via shared identity, removing the need for the previous AppGroup workaround (BIG-347). Note: requires an Arc Timeline update to take effect, which will ship separately.
Added warning alert and visual indicators when a user has both a lifetime purchase and an active subscription (BIG-353)
Bug Fixes
Fixed activity type model updates still flooding beyond the 3-concurrent cap introduced in Build 43, caused by a race condition in the concurrency check (BIG-358)
Fixed stale backup metadata being displayed after a fresh install on a device with an existing backup directory (BIG-273)
Any ETA on the Arc Timeline update that’ll allow for subscription linkage? I bought a lifetime subscription for Arc Timeline and this update has effectively locked me out of Arc Editor as it says I need to buy a subscription to continue using it.
Edit: just realised TestFlight purchases don’t involve real financial transactions.
@Hutima Yeah I haven’t added the 6 month option to Arc Editor’s subscriptions. The yearly subscription is the best value short of lifetime, so it felt kind of … redundant. People can use monthly when they’re not sure if they want to commit yet, then switch to yearly once they’re confident they want to stick with the app.
Though if you’ve already got a 6 monthly sub with Arc Timeline app, that’ll carry over fine. No need to change or have any new subscription.
It’ll just mean you need to manage your subscription either via the old app or in App Store’s subscriptions view. Arc Editor can see the subs from the other apps, but can’t make changes to them.
I see you found the workaround No money involved for TestFlight builds. But yeah subscription linkage is already built in.
It just needs a new Arc Timeline build shipped, to hook up the linkage on that side too. So I’m just holding off on shipping that Arc Timeline update until I’m ready to start pointing everyone to the new app properly.
But in the meantime, yeah no harm in doing a fake lifetime purchase in Arc Editor. It always makes me nervous, every time I do it, but it does say “TestFlight” or “Sandbox” at the top, so it is safe. It hasn’t lost me money yet
I used 6 mo. Both because I want to support the project and it was a less noticeable fee on the months it was billed but up to you if you want to keep it, I’ll switch to yearly if not
Hah! If you want to pay more I’m not going to discourage that
The best thing for me would be if everyone were on monthly subscriptions, no yearly or lifetime. Monthly costs the most, and earns the most money. That’s why all the massive services, Google, Apple, etc, usually only offer monthly options. More money for them, and people are usually already locked in so they’ve got no choice.
But that feels too evil for me. I’d prefer people got better deals if they’re sticking around.
Anyway if you’re wanting to stick with 6 monthly, no need to change! It’ll keep working as is, no problems there.
I don’t have the option to turn on calendar access. I see the orange circle in the editor settings, but if I go to IOS setting there is no option to calendars in the app settings.
Hi @biota-jingles-05! For that one, Arc won’t ask for calendar permissions until the first time you try to turn on calendar sync for a place.
Go into the Place Details view for any place in your timeline, from a visit’s details view, down the bottom. Then on the toolbar at the bottom of that view you can see a calendar button. When you tap that it’ll ask for permission then.
I’ll improve the text on the Permissions view to make that more clear. Thanks for the heads up!
I’d had the app open for a couple of days. When I opened the UI, I think it was on the Places tab. I switch to the Timeline tab, and of course it tried to load that day’s items (which were very few and local in nature; not my usual timezone-hopping issues).
…and that load never completed. It was still attempting to load those items the next morning:
Hm. That’s a weird one @kronk! Not sure what to make of that.
Well, sort of. I’ve seen the hung fetchItems() and update(from:) before. But I’d assumed that those were cases of the db reader pool being saturated, which other fixes have already mostly resolved.
This case looks more like a deadlock of some kind. The TimelineSegment in question is the current day’s, and there’s no heavy or complex data in that period. So really does have that smell of structural deadlock rather than resource exhaustion.
I wonder if it could be something like… if the app goes into the background, and something like a HealthKit query or Photos query are in flight, but then fall into the bottomless pit that those frameworks sometimes possess… But TimelineSegment doesn’t depend on those in any blocking way. So that theory doesn’t feel very solid…
No money involved for TestFlight builds. But yeah subscription linkage is already built in.
