[#2244] Update Navigation SDK to 1.1.10
- new features for expansion - We have given part of the app in the background a new version to make navigation run even better.
[#2233] Add dedicated MY TICKETS entry in feedback dialog
- Communication is important - To give you an overview of the messages you have exchanged with us, there is now a section "My Tickets" in the app's feedback area. Conveniently, without having to switch to emails or search for a long time.
[#2229] Remove debug logs
- Error found - We were able to reproduce the problem from the previous version and now fix it. So we no longer need the logs. And goodbye. NUNAV does not collect any data.
[#2226] Disable satellite map style
- We look from space - Until now, NUNAV had a view with satellite images. Unfortunately, these were not always up to date, and the images also required a lot of data volume. We have turned off the feature. This way, you always access a current map view while saving your data budget. Sometimes less is indeed more.
[#2223] Updated multiplatform sdk to v1.1.9
- We are restructuring - To ensure you continue to have the best user experience with NUNAV, our developers are diligently working in the background. This requires innovations that we have incorporated into this update.
[#2221] Add logs to identify positioning error
- Finding errors is not always easy - To better reproduce an error, we have set up a recording. Small step - big help
[#2217] Allow settings to be disabled via feature flags
[#2211] Destination reached dialog appears multiple times
- Arriving once is enough - The "Destination reached" dialog appeared multiple times upon arrival. We believe that when you are there, you are there. One view is sufficient. We have adjusted it, and now the message appears only once.
[#2210] Enforcement warning sounds are played too often
- The tone makes the music - Warning sounds are important. To draw the user's attention, they should be used thoughtfully. NUNAV played some sounds too frequently. We had the orchestra practice again. It was worth it.
[#2203] Debug code snipped leading to crash in production code
Start
Comments
0 comments
Please sign in to leave a comment.