You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.
Use a real device, not an emulator, because emulators don't have the issue for some reason
Open an activity with a map using an Intent
Perform usual steps (set token, add style etc.)
Expected behavior
Map renders correctly
Actual behavior
Map flashes correctly rendered, then turns black with attribution still visible for more than a second and finally appears correctly rendered again.
Log (verbose):
2020-04-27 18:00:57.994 12598-12598/de.kaffeepott.mockup W/ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@c03d7e2
2020-04-27 18:00:58.019 12598-12598/de.kaffeepott.mockup I/FloatingActionButton: Setting a custom background is not supported.
2020-04-27 18:00:58.030 12598-12598/de.kaffeepott.mockup I/FloatingActionButton: Setting a custom background is not supported.
2020-04-27 18:00:58.112 12598-12598/de.kaffeepott.mockup E/Minikin: addFont failed to create font, invalid request
2020-04-27 18:00:58.126 12598-12598/de.kaffeepott.mockup V/Activity: mLastPackageName-de.kaffeepott.mockup.MapActivity
2020-04-27 18:00:58.113 12598-12598/de.kaffeepott.mockup I/chatty: uid=10204(de.kaffeepott.mockup) identical 2 lines
2020-04-27 18:00:58.114 12598-12598/de.kaffeepott.mockup E/Minikin: addFont failed to create font, invalid request
2020-04-27 18:00:58.167 12598-12941/de.kaffeepott.mockup I/Mbgl-EGLConfigChooser: In emulator: false
2020-04-27 18:00:58.175 12598-12598/de.kaffeepott.mockup V/Mbgl-ConnectivityReceiver: connected - true
2020-04-27 18:00:58.521 12598-12598/de.kaffeepott.mockup D/ViewRootImpl[MapActivity]: changeCanvasOpacity: opaque=true
2020-04-27 18:00:58.550 12598-12598/de.kaffeepott.mockup V/Activity: onStop mLastPackageResume = false de.kaffeepott.mockup.CafeActivity@8835bcf
2020-04-27 18:01:00.124 12598-12598/de.kaffeepott.mockup D/ViewRootImpl[MapActivity]: changeCanvasOpacity: opaque=false
I've tested this on multiple devices and emulators and this bug seems to affect devices prior to Android 10.
Note: 2020-04-27 18:01:00.124 12598-12598/de.kaffeepott.mockup D/ViewRootImpl[MapActivity]: changeCanvasOpacity: opaque=false happens at the same time as the map showing correctly again and I would guess canvasOpacity has something to do with this.
Overall, my issue sounds exactly like fixing this issue should have fixed it, but it still persists
The text was updated successfully, but these errors were encountered:
@genericusername3 Thanks for reporting this. Can you upload your test project or create a new project that could reproduce this issue to GitHub and share it with me?
Hello,
I want to report the same problem, but without the flashes;
my map is always rendered black, with only the mapbox logo visibile.
This happen either in emulator and real device.
I've tried to fix in many ways, like changing ndk version, changing emulator render engine, and other, but problem still persists.
I've noticed in the debug log, mapbox call tiles, symbols and icons of the map correctly, but unfortunately they are not showed on screen.
This is content of my build.gradle module file:
Mapbox SDK version: com.mapbox.mapboxsdk:mapbox-android-sdk:9.1.0
Steps to trigger behavior
Expected behavior
Map renders correctly
Actual behavior
Map flashes correctly rendered, then turns black with attribution still visible for more than a second and finally appears correctly rendered again.
Log (verbose):
I've tested this on multiple devices and emulators and this bug seems to affect devices prior to Android 10.
Note:
2020-04-27 18:01:00.124 12598-12598/de.kaffeepott.mockup D/ViewRootImpl[MapActivity]: changeCanvasOpacity: opaque=false
happens at the same time as the map showing correctly again and I would guess canvasOpacity has something to do with this.Overall, my issue sounds exactly like fixing this issue should have fixed it, but it still persists
The text was updated successfully, but these errors were encountered: