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
Describe the Device, Operating System, and Browser
Samsung Android, limited details.
Describe the bug
Original description
"RST QC on droid OS, when user selected the back key then edit, this created a duplicate RST waypoint. Cell service was poor. I couldn’t duplicate this issue on my iPhone unfortunately.
I watched it with my own eyes. We had spotty cell service… In QC RST the droid user noticed a mistake before submitting the project then chose the back (<) “button” at the bottom of the screen to edit. Only droid OS phones have this option, my iPhone app didn’t have a back option. When he made the edit, two waypoints were submitted, one with the original or mistake info and one with the corrected info. I couldn’t confirm with another droid phone users. Really strange behavior."
We did a little digging and think it was this built in back button, not something within the QuickCapture interface.
Expected Behavior
At a minimum, the end user would expect the back button to behavior similarly to the Back button in QuickCapture. In this case it sounds like it might have somehow added a point?
Which app?
QuickCapture
Describe the Device, Operating System, and Browser
Samsung Android, limited details.
Describe the bug
Original description
"RST QC on droid OS, when user selected the back key then edit, this created a duplicate RST waypoint. Cell service was poor. I couldn’t duplicate this issue on my iPhone unfortunately.
I watched it with my own eyes. We had spotty cell service… In QC RST the droid user noticed a mistake before submitting the project then chose the back (<) “button” at the bottom of the screen to edit. Only droid OS phones have this option, my iPhone app didn’t have a back option. When he made the edit, two waypoints were submitted, one with the original or mistake info and one with the corrected info. I couldn’t confirm with another droid phone users. Really strange behavior."
We did a little digging and think it was this built in back button, not something within the QuickCapture interface.
Expected Behavior
At a minimum, the end user would expect the back button to behavior similarly to the Back button in QuickCapture. In this case it sounds like it might have somehow added a point?
Reproduction Steps & Sample
Other Relevant Info
We will try to get more information on this.
Priority impact
p0 - not time sensitive
Impact
It could be confusing for the end user, although this is the first time we've been notified about it so unsure how common it is.
The text was updated successfully, but these errors were encountered: