Hi, I'm developing a navigation app. Currently I'm using 100.14 version. (Not 100.15, because one thing was not working for me during navigation and changing to 100.14 fixed the issue - https://community.esri.com/t5/arcgis-runtime-sdk-for-android-questions/mapview-from-mmpk-not-loading....
Everything works fine when the phone is on, but since it's app for walking in the forest areas, it's convienient to turn off a phone, hide it in a pocket and turn it on when approaching a crossing. Sometimes after I turn on my phone, routeTracker behaves normally, traversed geometry updates to current location (there is only one issue while I'm passing by one of the stops during phone is off, it is not switching to next destination). But bigger issue is that sometimes when I turn on my phone, even after being off for just 30 seconds, routeTracker receives traversed geometry only from current location, not from the start of the route, so it looks like I just started traversing the route.
Maybe it is an issue with rerouting?
Hi @AnnaSzkibiel ,
Can you provide some more information about how you ensure that the RouteTracker keeps running while your application may not be in the foreground ("phone off")? If your RouteTracker instance is owned by your main activity (or other activity/fragment), those can be destroyed while the phone is "turned off". In that case your RouteTracker instance would also be destroyed and re-created at a later point. Based on your use case, it sounds like you need to ensure that the RouteTracker keeps running in the background. The recommended way of implementing this on Android is by using the WorkManager.
Feel free to share some of your code.