I am reviewing the values for ViewportStatusChangeReason in cameraChangedEvents. When performing the flyTo animation on the mapView:
If the flyTo animation completes without any user interactions that cancel it, the status updates from TRANSITION_STARTED to TRANSITION_SUCCEEDED. When I manually move the map afterward, it correctly displays the USER_INTERACTION event.
-However, if the flyTo animation is interrupted by user interactions that cancel it, the status updates from TRANSITION_STARTED to TRANSITION_FAILED. When I then move the map manually, it continues displaying this status and never updates back to the USER_INTERACTION event. This behavior seems like a bug to me.
Expected behavior
If the flyTo animation is interrupted by user interactions that cancel it, the status updates from TRANSITION_STARTED to TRANSITION_SUCCEEDED. When I manually move the map afterward, it correctly displays the USER_INTERACTION event.
Environment
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
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.