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
I have searched the history bug list, and have not found a similar bug.
The bug was found on the latest version 0.13 on google play (can be reproduced on an Android emulator 6.0 and a Redmi Note 4X phone )
Bug: I install the version 0.13 and start the app, create two simple trips(eg, test1 and test2). I click "test2" as shown in the video below(or "test1") and it get to the list page of "test2"(or test1). Everything works fine.
But when I long click "test1", then click "test2". It get to the list page of "test2" with the wrong action bar which points to "test1". If I click the "delete" icon in the action bar it will delete "test1" trip, even though this part is not recorded. And this could be confusing and a bug.
reproducing video
It would be really appreciated to get your concern on this. Thanks
The text was updated successfully, but these errors were encountered:
Hello, Thanks and sorry to interrupt. Is there anything updated about confirming this issue and issue78 as well?
Thank you again for your quick reply sincerely!
I have searched the history bug list, and have not found a similar bug.
The bug was found on the latest version 0.13 on google play (can be reproduced on an Android emulator 6.0 and a Redmi Note 4X phone )
Bug: I install the version 0.13 and start the app, create two simple trips(eg, test1 and test2). I click "test2" as shown in the video below(or "test1") and it get to the list page of "test2"(or test1). Everything works fine.
But when I long click "test1", then click "test2". It get to the list page of "test2" with the wrong action bar which points to "test1". If I click the "delete" icon in the action bar it will delete "test1" trip, even though this part is not recorded. And this could be confusing and a bug.
reproducing video
It would be really appreciated to get your concern on this. Thanks
The text was updated successfully, but these errors were encountered: