This project is dead?

[douglasg14b]

The passionate dev seems to have left, and Unity doesn't appear to have hired another to maintain this SDK from what I've read.

No updated since last year, repo activity essentially died > 3 years ago (~may 2020), and the issues & PRs are piling up.

Is there a support lifetime on this before it's deprecated, or is the slow, painful, death the plan? Or are there plans to maintain it?

Unity really should have a support lifetime/agreement for this as this has paying customers, and is advertised as an official SDK on their platform.

[gangstageek]

I'm curious if this is dead or not as well. If so I will probably have to switch to something else

[douglasg14b]

It definitely appears to be. This was more me calling it out because Mapbox appears to have abandoned it, without actually dropping it as a "supported platform". Which is very frustrating,

[Markovicho]

I was contacting the support several times as the current version of the SDK will not be compatible to latest Android Versions anymore. There are minor changes for Android API Level 31 which are not included in the SDK and will cause breaking compile errors. You are fine when creating APKs for older API Levels but you can't upload the app to the store in this case (API Level 33 is required since August 23).

Besides that the support cleary said that there will be no bugfixing for Unity-SDK in the near future at all. Don't know why they are still listing this SDK on their website which is pretty misleading.
It's abandoned and just a matter of time until there will be API changes causing the SDK to stop working. It's the same risk on both sides Android and iOS...

I don't know whats the roadmap for mapbox + unity or if they are still looking into this direction at all. Currently Niantic is realsing their own Maps-SDK. You should consider looking into their solution at least for locationbaed apps. For realistic 3D-Terrain it will be more likely Bing-Maps to take a look into :-)

[douglasg14b]

@Markovicho Thanks for the Niantic callout, that looks promising. Assuming it has the usual features & support for the variety of map-based operations mapbox does.

[diogo-garcia]

Pretty sad, I was starting to use mapbox but after trying to compile for Android I started to see problems, I'm looking into testing other solutions...

[astojilj]

It's not dead. We're scoping work for the next release. Please continue using mapbox-unity-sdk.
cc @brnkhy.

[jhchnc]

Per https://stackoverflow.com/questions/71682845/mapbox-not-opening-in-unity -- if you're looking for this to instantiate it's core functions, minus AR stuff, you can load the package per instructions and "Just delete AR related things that came with Mapbox such as ARCore,Kit Interface, GoogleARCore, etc folders from your Assets."

This allowed the rest of the package to compile, gave me the Mapbox navigation item, and allows me to use example scenes.

[brnkhy]

It's not dead, we are still working on Unity SDK at Mapbox.
We haven't been able to put much time and effort in public repo for a while but behind the scenes we have been working on a new version for some time.
Unfortunately I'm not able to give any ETA on that, or I can't even say if it'll be production-ready in short term. That's one of the reasons I couldn't answer these question earlier. But I'm hoping to release at least a public alpha version (minimal features) soon.

Almost all our effort is going into this new work but regarding the issues with current public repo, I pushed a proposed fixed forandroid target api related issues here;
https://github.com/mapbox/mapbox-unity-sdk/tree/androidEventsFix

[douglasg14b]

Is the new SDK going to be proprietary & closed source then? Why would work not continue on this repo?

At this point though, I'm sure much trust has been lost. For a commercial project to essentially abandon it's offering for 4 years now, that's dead. Until activity indicates otherwise, and even then, if there is no explicit support policy what's to stop this from happening again?

The lack of communication from Mapbox is loud in this case. If mapbox wants trust in this, then there should be some form of official communication on the state of things...

[brnkhy]

@douglasg14b I agree with all you said; there's a lot of work needs to be done and definitely not all on the technical side.

Our new work is in a private repo simply because it's not ready yet, not even for alpha testing. It's still better for most people to just use last public release (I mean after we fix this android issue, maybe have a cleanup and remove AR etc.). But we also want to share new work as soon as possible as developer feedback is undeniably invaluable.

[enemali]

It's not dead, we are still working on Unity SDK at Mapbox. We haven't been able to put much time and effort in public repo for a while but behind the scenes we have been working on a new version for some time. Unfortunately I'm not able to give any ETA on that, or I can't even say if it'll be production-ready in short term. That's one of the reasons I couldn't answer these question earlier. But I'm hoping to release at least a public alpha version (minimal features) soon.

Almost all our effort is going into this new work but regarding the issues with current public repo, I pushed a proposed fixed forandroid target api related issues here; https://github.com/mapbox/mapbox-unity-sdk/tree/androidEventsFix

How do we try this proposed fixed

[lucasgray]

Any update here? Thinking to dive back into an AR project and I'd rather use Mapbox+Unity, but seems like I should go with an alternative