while using the app everytime I record a new location that have not been visited/recorded before the app crashes and fully switches off which is very annoying. This pressuming I do have the latest iOS and app version on my iPhone 14 Pro.
Another one is when the app recognises a location on its own (which is great) and is still grayed out as in not confirmed there is no way to simply confirm it by clicking on it or long pressing it. At this point you need to eirhter edit and retype the location or got to the top to ‘uncertain’ section open the whole list, find it there and hit confirm there…both ways are unnecessarily long.
In both cases I’d appreciate any help in case I overlooked something or for developers I would appreciate fixing these bugs.
Hi blecha.pepa, two separate things there, so two answers.
Confirming a place Arc chose itself. You mentioned long-pressing didn’t give you a way to confirm, and that depends on which kind of grey you’re seeing. A grey dot beside a visit’s row means Arc has assigned a place but isn’t sure about it. A grey title means no place at all yet (it’s showing the street address), so there’s nothing to confirm on that one.
For the grey-dot kind there are two short routes:
Long-press the visit’s row in the timeline list. The menu has Confirm place at the bottom, below the divider. It only appears once Arc has picked a place.
Or tap the visit, then Edit (top right, not Edit Segments): the green Confirm button is at the bottom of that screen. Tapping a place in that screen’s list also sets and confirms it in one go.
In the list behind the “uncertain items” banner at the top of the day, long-pressing a row gives Confirm place directly too. If you long-press a grey-dot visit and don’t get that menu item, tell me and I’ll look into it.
The crash. There’s one crash we know of that happens right as the place-name search box closes, just after picking a result or tapping “Add a new private place”. Does yours happen at that moment, or earlier, while you’re out and the visit is still being recorded? You mentioned the latest iOS; could you give me the exact number (Settings › General › About)? That’s how we match it against what we have. If it’s the search-box moment, it’s very likely the same crash.
If you’re up for an experiment: for a new visit with no place yet (grey title), tap it, then Edit. The bar at the bottom shows Add private place; use that rather than the search box, and name it there. It’s a separate button from the “Add a new private place” row in search results. I don’t know yet whether that route avoids the crash, so whether it does or not is useful to know. If Arc has already put a wrong place on the visit, that button won’t be there; say so and we’ll go from there.
Thank for the answer. I’ll check the first issue later but when it comes to the crash, I don’t want to be adding private places but rather use existing places from your database.
For a new location that I never visited before I tap the edit icon, then the search below. I then type and select the suggested location and following that, the app crashes
@blecha.pepa and @pet.stes, thank you both. That crash, when choosing a search result in the place picker, is one we’re tracking as BIG-478, and both of your reports are recorded on it. I’ll say so in this thread when a fix ships. pet.stes, thanks for the steps and screenshots.
blecha.pepa, no need for the private-place experiment, then; picking from the search results is the normal way to do it.
