Joey Timmer

I was also having the issue where the preview showed up black. Tried all solutions given here and nothing worked, preview stayed black. After downloading the source code and adding...

@jush yes I do, but also manually initialize them the same way the docs explain. If I leave the initializer in the manifest i receive a lot more crashes related...

@jush I use this in my manifest: ``` ``` And this in the composable to initialize: ``` LaunchedEffect(Unit) { try { AppInitializer.getInstance(context) .initializeComponent(MapboxMapsInitializer::class.java) isInitialized = true } catch (e: Exception)...

@jush follow-up, after adding: ``` AppInitializer.getInstance(context) .initializeComponent(MapboxSDKCommonInitializer::class.java) ``` The crash of the app is unfortunately still there, I still see reports coming in through crashlytics.

@kiryldz you’re correct in the version number, small typo. When I left all the initializers in I got even more crashes, again on Samsung devices mostly, about not being able...

@kiryldz I just submitted a build to google where I removed all my manual initializing and just use the default way for Mapbox. Will report back with anything I find....

@kiryldz after reverting back to the original initializer like you suggested the crash has disappeared. I missed the part where you guys rewrote the initialization. I also haven't seen the...