flutter_mapbox_navigation: Mapbox is not working after migrating to null safety flutter_mapbox_navigation@0.0.26

Hello eopeter, Let me fist think you for making this amazing project. And let you know that any comment or guiding that you provide will be helpful in my case (because i have an app in beta testing blocked by this issue)

Recently i migrated my project to Null Safety and it was dependent on flutter_mapbox_navigation version 0.0.19

So i needed to migrate to the Null Safety version of the package which i assume is 0.0.26

The navigation view doesn’t work anymore, nor the map view.

I thought it’s maybe something wrong with my project so i cloned yours and tried to start the example provided as is (i just changed the mapbox tokens)

These screenshots are from your project’s example (same issue in mine also)

The navigation view is like this: image

And these two exceptions shows up image

I noticed something strange in this class, i started a debug session and sometimes the object json doesn’t have the structure you are waiting for eventType and data fields are missing and the structure looks like RouteProgressEvent class.

Something else, your model is different from the model provided in the 1.2.0 navigation ui api https://docs.mapbox.com/android/navigation/api/1.2.0/libnavigation-base/-base/com.mapbox.navigation.base.trip.model/-route-progress/

image

Any help will be appreciated.

Thank you.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 28 (8 by maintainers)

Most upvoted comments

Thank you for the reactivity. Do you have any estimated release date 😭 ?

This should be fixed in the latest. The library is migrated to MapBox Android 10 and once I deploy it, should address a lot of the open bugs

my vacation begins today so hoping to close this out. Experiencing a weird issue where the map tiles won’t load when embedded. Hoping to get resolution on it today.

Library changed significantly on MapBox 2.0 so taking longer to upgrade.

On Dec 7, 2021, at 12:30 AM, John Brian @.***> wrote:

@eopeter where are we on this

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Please @elFallino can you show how to do that. An example would be nice.