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
When integrating MapLibre with Android Navigation Compose, the default fade-in/fade-out transitions provided by Navigation Compose do not apply smoothly to the MapView. Instead, the map disappears and reappears abruptly, disrupting the user experience.
Potential Cause:
The issue might be related to how MapView manages its lifecycle during transitions. Navigation Compose likely delays the disposal of a screen's UI for the duration of the fade-out animation, but MapView does not seem to respond correctly to these lifecycle changes.
Similar Issues:
The same issue has been reported to Ramani Maps.
The text was updated successfully, but these errors were encountered:
MapLibre Android Version
11.6.1
Android SDK Version
Android 14
Device
Google Pixel 9
What happened?
When integrating MapLibre with Android Navigation Compose, the default fade-in/fade-out transitions provided by Navigation Compose do not apply smoothly to the MapView. Instead, the map disappears and reappears abruptly, disrupting the user experience.
This issue occurs because MapView does not properly handle the lifecycle events triggered during these transitions. This behavior is inconsistent with other Compose-based UI elements, which handle transitions seamlessly.https://github.com/user-attachments/assets/0a69542b-27e7-4aa7-9a5a-5eb1df3b8ebb
Steps to reproduce
Clone the reproduction repository: https://github.com/TonyGnk/mapIssue.
Renderer
OpenGL (choose this if you are unsure)
Relevant log output
Additional context
Potential Cause:
The issue might be related to how MapView manages its lifecycle during transitions. Navigation Compose likely delays the disposal of a screen's UI for the duration of the fade-out animation, but MapView does not seem to respond correctly to these lifecycle changes.
Similar Issues:
The same issue has been reported to Ramani Maps.
The text was updated successfully, but these errors were encountered: