Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0057951
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] POSmajoralways2025-02-11 17:592025-03-18 11:09
ReporterjfvaringotView Statuspublic 
Assigned ToAugustoMauch 
PriorityhighResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Statusapproved
Review Assigned To
OBNetwork customerOBPS
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0057951: POS 2 - POS is frozen after automatic logout out, when manual action to logout is in progress

DescriptionREPRODUCED ON 24Q4 and 25Q1 and MASTER

When the automatic logout (timeout) is set, that the user started to manually log out when he is logged out automatically, the POS is frozen at login.
Steps To ReproduceSet an automatic logout on back :
1. Preference 'Web POS Session Timeout' (for example 30s)
2. Preference 'Web POS Session Timeout - Alert Lead Time' (for example 10s)

On POS :
1. log in
2. click on deconnexion
3. do not disconnect and wait for the automatic logout
4. let the POS disconnects the user
5. log in

-> the POS is frozen
Proposed SolutionAffter having been disconnected, the user can connect again when login again.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
depends on backport 005827425Q1 closedmeriem_azaf POS 2 - POS is frozen after automatic logout out, when manual action to logout is in progress 
depends on backport 005827524Q4 closedmeriem_azaf POS 2 - POS is frozen after automatic logout out, when manual action to logout is in progress 

-  Notes
(0176129)
jfvaringot (viewer)
2025-02-25 16:58
edited on: 2025-02-25 16:59

2nd scenario :
On back-office, set your touchpoint type in order to display the Receipt delivery method on POS, after the payment.

On POS :
1. do a ticket
2. click on pay and process to payment
3. when the Receipt delivery pop-up is display, wait for the log-out
4. let the POS disconnects the user
5. log in

-> the POS is frozen

(0176433)
AugustoMauch (administrator)
2025-03-04 13:47

Another way to reproduce:

On POS :
1. add a line to the ticket
2. click on Delete Ticket. A popover will be displayed because a ticket with lines is being removed.
3. do not close the popover, wait for the log-out
4. let the POS disconnects the user
5. log in
(0176434)
AugustoMauch (administrator)
2025-03-04 13:48

The problem occurs because when the automatic logout took place, an action was in execution (i.e. DeleteTicket, with the latest steps to reproduce).

When logging in, the action will still count as in execution in OB.App.State.getState().UI.userActions.inProgressStack, so the user action scrim will be on top.
(0176436)
hgbot (developer)
2025-03-04 14:38

Merge Request created: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/pmods/org.openbravo.core2/-/merge_requests/1809 [^]
(0176687)
hgbot (developer)
2025-03-11 18:24

Merge request merged: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/pmods/org.openbravo.core2/-/merge_requests/1809 [^]
(0176688)
hgbot (developer)
2025-03-11 18:24

Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/pmods/org.openbravo.core2 [^]
Changeset: 0c349ff25d70df3be2ece5d48dfd298772a66286
Author: Augusto Mauch <a.mauch@orisha.com>
Date: 11-03-2025 17:24:39
URL: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/pmods/org.openbravo.core2/-/commit/0c349ff25d70df3be2ece5d48dfd298772a66286 [^]

Fixes ISSUE-57951: Screen is not locked after automatic logout

The problem was that if the automatic logout took place while a user action was blocked because of a dialog
in a prehook, the user action stack was never cleaned, and when the user logged in again, the application
would think the user action was still in execution, showing the user action scrim and blocking the screen.

Now, when the login screen is rendered for the first time, the user action stack will be reset.

---
M web-jspack/org.openbravo.core2/src/components/AuthProvider/LoginScreen.jsx
M web-jspack/org.openbravo.core2/src/components/AuthProvider/__test__/LoginScreen.test.jsx
M web-jspack/org.openbravo.core2/src/components/AuthProvider/stories/LoginScreen.stories.jsx
---

- Issue History
Date Modified Username Field Change
2025-02-11 17:59 jfvaringot New Issue
2025-02-11 17:59 jfvaringot Assigned To => Retail
2025-02-11 17:59 jfvaringot Triggers an Emergency Pack => No
2025-02-12 09:11 inaki_azkonobieta OBNetwork customer => OBPS
2025-02-12 09:12 inaki_azkonobieta Issue Monitored: inaki_azkonobieta
2025-02-12 09:42 guillermogil Assigned To Retail => Triage Platform Base
2025-02-25 16:58 jfvaringot Note Added: 0176129
2025-02-25 16:59 jfvaringot Note Edited: 0176129 View Revisions
2025-03-04 13:47 AugustoMauch Note Added: 0176433
2025-03-04 13:48 AugustoMauch Note Added: 0176434
2025-03-04 14:38 hgbot Merge Request Status => open
2025-03-04 14:38 hgbot Note Added: 0176436
2025-03-04 20:25 AugustoMauch Status new => scheduled
2025-03-04 20:25 AugustoMauch Assigned To Triage Platform Base => AugustoMauch
2025-03-11 18:24 hgbot Merge Request Status open => approved
2025-03-11 18:24 hgbot Note Added: 0176687
2025-03-11 18:24 hgbot Resolution open => fixed
2025-03-11 18:24 hgbot Status scheduled => closed
2025-03-11 18:24 hgbot Fixed in Version => 25Q2
2025-03-11 18:24 hgbot Note Added: 0176688
2025-03-18 11:08 meriem_azaf Status closed => new
2025-03-18 11:08 meriem_azaf Resolution fixed => open
2025-03-18 11:08 meriem_azaf Fixed in Version 25Q2 =>
2025-03-18 11:08 meriem_azaf Status new => scheduled
2025-03-18 11:09 meriem_azaf Status scheduled => resolved
2025-03-18 11:09 meriem_azaf Resolution open => fixed
2025-03-18 11:09 meriem_azaf Status resolved => closed


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker