[Bug]: mapbox::navigation::TilesetDescriptorFactory::getLatest(std::__1::shared_ptr<mapbox::navigation::CacheHandle> const&)

[dmitry-yashkin]

Mapbox Navigation SDK version

v2.0.1

Steps to reproduce

A crash report from Crashlytics:

Crashed: com.mapbox.common.Worker 3
0  MapboxNavigationNative         0xd1738 mapbox::navigation::TilesetDescriptorFactory::getLatest(std::__1::shared_ptr<mapbox::navigation::CacheHandle> const&) + 491320
1  MapboxNavigationNative         0xd0a84 mapbox::navigation::TilesetDescriptorFactory::getLatest(std::__1::shared_ptr<mapbox::navigation::CacheHandle> const&) + 488068
2  MapboxNavigationNative         0xd35c4 mapbox::navigation::TilesetDescriptorFactory::getLatest(std::__1::shared_ptr<mapbox::navigation::CacheHandle> const&) + 499140
3  MapboxCommon                   0x3f194 mapbox::common::TaskSequence::scheduleTask(unsigned long long, std::__1::chrono::time_point<std::__1::chrono::steady_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > >)::'lambda'()::operator()() const + 480
4  MapboxCommon                   0x435e4 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, mapbox::common::ThreadedSchedulerBase::makeSchedulerThread(unsigned long, mapbox::base::WeakPtr<mapbox::common::Scheduler>)::$_0> >(void*) + 708
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

97% occurs in background.

Expected behavior

Doesn't crash

Actual behavior

Crashes

Is this a one-time issue or a repeatable issue?

repeatable

[1ec5]

No debug symbols, but maybe this rings a bell for @mapbox/navnative?

[1ec5]

@dmitry-yashkin, does this issue still reproduce with the latest version of the navigation SDK?

[dmitry-yashkin]

We are still on 2.0.1 so I can't confirm if it's happening on the latest version. Hope we will update the navigation SDK soon and I will be able to provide additional details.

[kried]

Please re-open the question if there is any additional information.