Openbravo Issue Tracking System - POS2
View Issue Details
0045950POS2Corepublic2021-02-25 11:442024-01-10 12:30
lorenzofidalgo 
Triage Platform Base 
highminoralways
acknowledgedopen 
5
pi 
 
Automated tests
No
0045950: Cross Origin errors are thrown visiting the NewPOS
The following error is shown after vising more than once the NewPOS login page:
"Blocked a frame with origin "https://livebuilds.openbravo.com" [^] from accessing a cross-origin frame."
It has been reproduced in CI and much more easily with Cypress automated tests in local against NewPOS livebuilds. Check the attached videos since they are pretty informative to narrow the error down.
( https://drive.google.com/file/d/1P5tRmXshhWF1nxebrLMjMZ1Mas_X8cVm/view?usp=sharing [^] )
( https://drive.google.com/file/d/1ZWKLQUILVfztzT2aUDCKDIruO1lCBmsn/view?usp=sharing [^] )
( https://drive.google.com/file/d/1f_7-d0aXxPejKK21xdThVOcp4wezKwgW/view?usp=sharing [^] )
This seems to be related with Service Workers because the browser unblocks the sitauation after service workers are cleaned. Besides, after checking when the issue started to happen (around 15th February), a merge containing Service Workers changes was introduced in core2. So it seems to be related (but not sure 100%).

To be able to unblock Cypress tests and continue the executions, chromeWebSecurity has been disabled. To reproduce this issue, it is required to backout the following changeset: https://gitlab.com/openbravo/product/pmods/org.openbravo.core2/-/commit/ab3429626be38c53f337e1a1136b9696db5121b3 [^]
0-With the Cypress automated tests repo ready in your local machine, set "cypress.env.json" file with the following to be able to launch your tests against the livebuilds remote machine:
{
    "baseUrl":"https://livebuilds.openbravo.com/retail_pos2_modules_pgsql", [^]
    "terminalUrl": "/web/pos/?terminal=VBS-2"
}
1-Launch .../src-test/cypress/runAllSpecs/runFeaturesSpecsPOS2.spec.js suite against
"https://livebuilds.openbravo.com/retail_pos2_modules_pgsql/web/pos/?terminal=VBS-2" [^]
DEFECT: Realise when the second test executes the cy.visit command, it fails launching a Cross Origin error.
No tags attached.
Issue History
2021-02-25 11:44lorenzofidalgoNew Issue
2021-02-25 11:44lorenzofidalgoAssigned To => Retail
2021-02-25 11:44lorenzofidalgoRegression level => Automated tests
2021-02-25 11:44lorenzofidalgoTriggers an Emergency Pack => No
2021-02-26 13:52lorenzofidalgoDescription Updatedbug_revision_view_page.php?rev_id=22151#r22151
2021-02-28 18:30guilleaerAssigned ToRetail => alostale
2021-03-03 08:50alostaleNote Added: 0126481
2021-03-03 08:50alostalePriorityimmediate => high
2021-04-29 10:07guilleaerAssigned Toalostale => platform
2021-04-29 10:07guilleaerSeveritymajor => minor
2021-04-29 10:07guilleaerTypedefect => design defect
2021-04-29 10:57guilleaerStatusnew => acknowledged
2022-02-01 08:07alostaleAssigned Toplatform => Triage Platform Base
2024-01-10 09:07lorenzofidalgoSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=27314#r27314
2024-01-10 12:28lorenzofidalgoDescription Updatedbug_revision_view_page.php?rev_id=27315#r27315
2024-01-10 12:30lorenzofidalgoNote Added: 0159038
2024-01-10 12:30lorenzofidalgoNote Edited: 0159038bug_revision_view_page.php?bugnote_id=0159038#r27317

Notes
(0126481)
alostale   
2021-03-03 08:50   
Downgraded priority as it has been workarounded [1]

[1] https://gitlab.com/openbravo/product/pmods/org.openbravo.core2/-/commit/ab3429626be38c53f337e1a1136b9696db5121b3 [^]
(0159038)
lorenzofidalgo   
2024-01-10 12:30   
While I keep the "Steps to reproduce" as is for history purposes, right now, while following the same steps, a new and less informative error is shown:
After the step "1", while doing the visit, a timeout error is shown but no more info is shown. Probably same root cause but now it is harder to track.