Crash with null pointer dereference

Nobody has claimed this yet.

## Environment

- Android OS version: 36
- Devices affected: Any
- Maps SDK Version: 11.18 and previous as well

## Observed behavior and steps to reproduce

My production crashlytics reports issue i can't reproduce

```
Crashed:
null pointer dereference
0
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
1
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
2
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
3
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
4
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
5
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
6
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
7
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
8
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
9
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
10
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
11
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
12
split_config.armeabi_v7a.apk!libmapbox-maps.so
(Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc)
13
boot.oat
art_jni_trampoline + 68
14
base.odex
com.mapbox.maps.renderer.MapboxRenderThread.draw + 766
15
base.odex
com.mapbox.maps.renderer.MapboxRenderThread.doFrame + 334
16
boot.oat
android.view.Choreographer.doCallbacks + 1158
17
boot.oat
android.view.Choreographer.doFrame + 2266
18
boot.oat
android.view.Choreographer$FrameDisplayEventReceiver.run + 112
19
boot.oat
android.os.Handler.dispatchMessage + 70
20
boot.oat
android.os.Looper.loopOnce + 876
21
boot.oat
android.os.Looper.loop + 954
22
boot.oat
android.os.HandlerThread.run + 948
23
libart.so
art_quick_invoke_stub_internal + 68
24
libart.so
art_quick_invoke_stub + 248
25
libart.so
art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*) + 128
26
libart.so
art::Thread::CreateCallback(void*) + 1248
27
libc.so
__pthread_start(void*) + 40
28
libc.so
__start_thread + 30
```

First question is there a way to have readable data instead of `Missing BuildId 343200f4b0300639ed7f4660f6e6998cde3a18cc`

This crash hapens mostly on samsung and xiaomi devices but may happen on others

any help is appreciated

Start with the supplied Crashlytics trace, especially MapboxRenderThread.draw and the repeated Missing BuildId entries in libmapbox-maps.so. Investigate whether the native crash can be symbolicated or reproduced on the reported Samsung and Xiaomi devices running Android 36. Done means the failure has an identified cause or a reproducible case with actionable diagnostic data.

Written by the indexing model from the issue text.