Please or Register to create posts and topics.

Using with Start flagged (only) to record track to update OSM maps. App hangs when try to add first stop

I am new to scenic but like what I see so far. I have been trying to update the OSM maps in my area. I have poor cell reception and do have the offline map downloaded. I have successfully done one track, exported the points, imported to OSM and created my road. This is solely with an iphone 15 pro.

I tried to do a secondary road walking using 4.27. I set a Start, then started the ride and began  walking. At a juncture point I thought I should record a ‘waypoint’ so I paused the ride, went to Plan and put in a ‘Stop’ (first one). At this point, scenic went into recalculating and never returned. However, I continued the walk to where I could ensure I had network connection (I believe I had network connection at the time), It was still ‘recalculating’.

Checked what version I had and discovered there was an update so I put the update in first (4.28). On restarting scenic it noted it had quit unexpectedly and asked if I wanted to save the ‘ride’. YAY! saved the walking points. I note it recorded past where it ‘hung’ so I have all the data points for the map update but was not able to add a Stop while recording.

But i had also noticed changing information while ‘riding’ (even in car mode), that it sometimes gets stuck ‘recalculating’ and has to be restarted.

Hmmm. I thought I resolved this in 4.28. It shouldn't hang (I assume you mean the "calculating route" spinner kept spinning) it should give you a route, or an error message if the route can't be recalculated. I'll take another look.

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

To be clear, it was USING 4.27 when it happened. I updated to 4.28 (which caused the ‘unexpected’ stop error message I suspect when the app got restarted),.  Let me test again with 4.28 (I need to walk again tomorrow :)) before wasting any time looking.

I tested a similar scenario this morning with 4.28 and did not encounter any issues 👍