mapbox / mapbox/mapbox-maps-android
ViewportStatusChangeReason unexpected value after TRANSITION_FAILED
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 578
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
Environment
- Android OS version: 14
- Devices affected: Samsung Galaxy A53 5G
- Maps SDK Version: 11.8.0
Observed behavior and steps to reproduce
-
I am reviewing the values for
ViewportStatusChangeReasonincameraChangedEvents. When performing theflyToanimation on the mapView: -
If the
flyToanimation completes without any user interactions that cancel it, the status updates fromTRANSITION_STARTEDtoTRANSITION_SUCCEEDED. When I manually move the map afterward, it correctly displays theUSER_INTERACTIONevent.
-However, if theflyToanimation is interrupted by user interactions that cancel it, the status updates fromTRANSITION_STARTEDtoTRANSITION_FAILED. When I then move the map manually, it continues displaying this status and never updates back to theUSER_INTERACTIONevent. This behavior seems like a bug to me.
Expected behavior
- If the
flyToanimation is interrupted by user interactions that cancel it, the status updates fromTRANSITION_STARTEDtoTRANSITION_SUCCEEDED. When I manually move the map afterward, it correctly displays theUSER_INTERACTIONevent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Android 14 behavior with Maps SDK 11.8.0 on the reported Samsung Galaxy A53 5G, focusing on flyTo, cameraChangedEvents, and ViewportStatusChangeReason. Compare the event sequence for a completed animation, an interrupted animation, and subsequent manual movement. Done means the interrupted transition produces the expected status and later manual movement reports USER_INTERACTION.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100