Project:
| View Revisions: Issue #57737 | [ Back to Issue ] | ||
| Summary | 0057737: Locking a terminal and opening the EnyoPOS on a different tab can lead to state persistence problems | ||
| Revision | 2025-01-23 12:21 by aaroncalero | ||
| Steps To Reproduce | - Open EnyoPOS in one tab - Work with it, create several tickets. Open the Orders window, check that the tickets that were created were synchronized - Logout, but keep the tab open - Open EnyoPOS in other tab (at this momento the persistence of the original tab will be stopped) - Create a one ticket, and close that tab - Log in again in the initial tab (the persistence remains stopped). - Create a few tickets - Switch to offline mode - Refresh the browser. The state recovered from the persistence layer will not contain the latest changes. - Create a few tickets more - Checke the Orders window, and notice that duplicated document numbers¡ |
||
| Revision | 2025-01-23 12:20 by AugustoMauch | ||
| Steps To Reproduce | - Open EnyoPOS in one tab - Work with it, create several tickets. Open the Orders window, check that the tickets that were created were synchronized - Logout, but keep the tab open - Open EnyoPOS in other tab (at this momento the persistence of the original tab will be stopped) - Create a one ticket, and close that tab - Log in again in the initial tab (the persistence remains stopped). - Create a few tickets - Refresh the browser. The state recovered from the persistence layer will not contain the latest changes. - Create a few tickets more - Checke the Orders window, and notice that duplicated document numbers¡ |
||
| Revision | 2025-01-23 12:00 by AugustoMauch | ||
| Steps To Reproduce | - Open EnyoPOS in one tab - Work with it, create several tickets. Open the Orders window, check that the tickets that were created were synchronized - Logout, but keep the tab open - Open EnyoPOS in other tab (at this momento the persistence of the original tab will be stopped) - Create a one ticket, and close that tab - Log in again in the initial tab (the persistence remains stopped). - Create a few tickets - Refresh the browser. The state recovered from the persistence layer will not contain the latest changes. - Create a few tickets more - Checke the Orders window, and notice that duplicated document numbers (caused by the |
||
| Revision | 2025-01-23 12:00 by AugustoMauch | ||
| Description | In certain circumstances, detailed in the steps to reproduce, it is possible for cashiers to work on POS terminals that will not persist the changes done in its state. As a consequence, when that terminal is restarted, the state that it will be recovered from the perseistence will be outdated. There are currently some mitigations in place to reduce the impact of this problem, but they do not cover all cases, and they do not work offline. Note that this steps reproducible the problem in EnyoPOS, but not in ReactPOS |
||
| Revision | 2025-01-23 11:44 by AugustoMauch | ||
| Steps To Reproduce | - | ||
| Revision | 2025-01-23 11:44 by AugustoMauch | ||
| Description | - | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |