ONGOING: Android Navigation issues
-
@Timo-Martosatiman-MRA Great to see it is being worked on:).
@StefanHummelink
Thank you Stefan, it's been a crazy day so far. The Web development team, App development team and our Cloud Service Provider are in an emergency meeting as we speak.
The meeting is going well, right now the teams are aligning short term and long term solutions to an effective plan.
-
The web dev team, app dev team and Cloud Service Provider have finished their meeting.
The issue lies in that the data type of waypoints and routes was changed by the web dev team on sunday. However, this happened without the involvement of the app dev team who as a result did not adjust the code of MRA Navigation Android to accept the new data types. Logically, this results in the Android app being unable to "read" the web database. The iOS version of the navigation app is untouched by this issue because it is able to automatically change the data type to the right format.
While the app dev team was not at fault, they are now dedicating resources to have a fix ready today/tonight on Android. We hope that simply updating the app will allow you to continue normal usage. However, just to be sure, our official advice will be to reinstall the app after the update has been posted. As I've already chatted with several of our community members: I understand how frustrating that is if you have 5 gb of maps on your device.
Kind regards,
Timo
-
@Matt-Flaming Thanks for the tip, I've edited it!
-
The web dev team, app dev team and Cloud Service Provider have finished their meeting.
The issue lies in that the data type of waypoints and routes was changed by the web dev team on sunday. However, this happened without the involvement of the app dev team who as a result did not adjust the code of MRA Navigation Android to accept the new data types. Logically, this results in the Android app being unable to "read" the web database. The iOS version of the navigation app is untouched by this issue because it is able to automatically change the data type to the right format.
While the app dev team was not at fault, they are now dedicating resources to have a fix ready today/tonight on Android. We hope that simply updating the app will allow you to continue normal usage. However, just to be sure, our official advice will be to reinstall the app after the update has been posted. As I've already chatted with several of our community members: I understand how frustrating that is if you have 5 gb of maps on your device.
Kind regards,
Timo
@Timo-Martosatiman-MRA Will the App also Updated? As I am aware is Beta almost ready.
-
@Timo-Martosatiman-MRA Will the App also Updated? As I am aware is Beta almost ready.
@Kudee the android App will receive an update based on a previous stable build. As I've written in some other threads, this issue sadly coincided with feature updates to MRA Navigation for android. The added features will be reactivated in the coming days as a regular stable update. (you won't have to reinstall the app. As others have pointed out, reinstalling the app is not a preferred option)
-
Can you advise when this will be working as I have spent three months mapping for a trip to Scotland, I have also got some guys to get MRA and the app, and now it's not working and we are leaving Thursday morning.
-
Can you advise when this will be working as I have spent three months mapping for a trip to Scotland, I have also got some guys to get MRA and the app, and now it's not working and we are leaving Thursday morning.
@Vince-Hyde will absolutely keep you updated. While a fix wasn't rolled out yesterday, it should be up and running again today, in time for your trip to scotland to go through unhindered. I'll leave updates here regarding the progress.
-
@Vince-Hyde @Kudee @Matt-Flaming
A new official statement is out:
We have identified the problem that some routes can't be opened with MRA Navigation Android. Due to changes to the database, Android no longer recognizes the database with waypoints. That was unforeseeable. Yesterday night an update was offered to Google Play and we are awaiting approval by Google. The expectation is that there will be several further updates today and that everything will work as it should tonight. We apologize for the inconvenience and thank you for your understanding.In addition to this, as part of the ongoing informal discussion, I can add that the developers have been at work with this issue since 6:30 this morning after working late yesterday night to get the new update out. We now aim to first and foremost ensure that those routes affected can be opened again. We expect some things to break as this isn't a regular patch but an emergency fix. Parallel to the release of this first update, we'll have physical tests underway to experience the new android update from a user perspective as well. There's no doubt going to be some improvements there, so that's why we also expect to have some further updates happening along the day.
-
The issue has been resolved.
-
Solved
Version 1.6.4