After about 45 minutes of my journey I opened Arc Editor for the first time today and unfortunately noticed that no recording had taken place (and the map focus was back on New York City instead of Berlin, where I am currently located): “red X” in the settings, even though the switch was set to “On”/green. How can I prevent this behaviour?
Arc Timeline, on the other hand, worked normally – without any gaps.
Speaking of gaps: there is no visible gap in the Arc Editor “timeline”: “Stationary” until 4:30 a.m., then followed by “Train” started at 8:45 a.m. But I left home at 7:59 a.m.
To restart the recording, I flipped the Timeline Recording switch twice: On > Off > On. Afterwards a completely white (info) screen opened immediately – I saw some text and/or graphics for just a fraction of a second. After closing this window, Arc Editor has worked perfectly so far. What was that?
I hope this information helps you in your further development of this really nice and helpful app for all of us. I really appreciate your efforts.
Side issue, but I’m still hunting this one! It’s something I’ve never seen, but it sounds suspiciously like … actually, I wonder if it’s related to the main problem you’re reporting. It sounds like something that might happen if Mapbox (the maps system) isn’t getting a location.
Yeah this is matching up. This is something I’d expect to see if the app isn’t getting location permission. Like, it’s being told it can’t access location data.
Have a check in iOS’s Settings app → Privacy & Security → Location Services → Arc Editor. Make sure that in there it’s set to “Always” and also that “Precise Location” is turned on.
If both of those are already correct, then I think it’s time to restart the phone. Because in that case it’ll be iOS messing up the authorisation states.
I saw this the other day on a friend’s phone with Photos library authorisation, in the Insta360 app. The app was insistent that it’d already requested Photos permission, and was thus pointing us to the Settings app to correct our mistake on denying permission. But in Settings app it showed as though the app had never requested. After restarting the phone it all came right
Yeah I’ve been seeing this behaviour too in data gap situations. I’ve got it on the todos to do more work on data gap handling. It’s not behaving intuitively or correctly in all cases. I did some improvements on it in a recent build, but clearly I haven’t got it fully right yet.
Ooh I should’ve read your full message before replying! Yeah that does indicate iOS’s auth states being a bit messed up. That thing you saw flashing briefly was probably the onboarding view, that’s triggered to appear when one of the required permissions either hasn’t been requested yet or has been denied. It’ll have popped up because location access was denied/missing, then on appear it must’ve triggered something that reset that state and resolved the problem.
I actually often see that “onboarding briefly appearing” thing when starting Arc immediately after restarting my phone. Because immediately after restart it seems as though iOS hasn’t finished figuring out what’s available to who yet. Or perhaps it’s still starting up the Location Services system, and thus denies Arc’s access to it when Arc first starts up.
I’ll keep an eye on this stuff, and hopefully can figure out a way to more smoothly work around it in future! Ironically, I think Arc Editor shows this kind of problem more frequently than old Arc Timeline because Arc Editor is more diligent in checking the auth states.
Arc Timeline mostly doesn’t bother - it just tries to go ahead and use it, and keeps at it until it gets through. Arc Editor follows the “proper” processes and checks before using, showing onboarding as appropriate, not starting recording until it’s been granted what it needs, etc. So old Arc Timeline’s aggressive “I’m not even going to ask, I’m just gonna charge ahead” bad behaviour ends up more successful in this case!
