Openbravo Issue Tracking System - Retail Modules
View Issue Details
0043931Retail ModulesWeb POSpublic2020-04-30 10:322020-05-05 10:26
caristu 
migueldejuana 
highminorhave not tried
closedduplicate 
5
 
RR20Q2 
migueldejuana
No
0043931: Error when login into WebPOS having messages pending to synchronize in the state
If we login into WebPOS an there exists messages in the state pending to be synchronized, then the following error is raised when login:

0522af920179e8c1b4896634bd7b7672.js:42453 Uncaught (in promise) TypeError: Cannot read property 'transaction' of null
    at IndexedDBController.getReadWriteTransaction (0522af920179e8c1b4896634bd7b7672.js:42453)
    at IndexedDBController.write (0522af920179e8c1b4896634bd7b7672.js:42317)
    at IndexedDBController.put (0522af920179e8c1b4896634bd7b7672.js:42309)
    at MessageModelController.put (0522af920179e8c1b4896634bd7b7672.js:44054)
    at SynchronizationBuffer.onMessagesChanged (0522af920179e8c1b4896634bd7b7672.js:44180)
    at 0522af920179e8c1b4896634bd7b7672.js:41298

This is because we are trying to save the messages into the synchronization buffer IndexedDB database before it is initialized.
0) Leave a message pending to be synchronized in the state. For example force an error in the "onMessagesChanged" before executing "OB.App.State.Messages.removeMessages"

1) Login in WebPOS, note that the error mentioned in the Description is raised in the console
Ensure that we save the pending messages once the IndexedDB database is ready
No tags attached.
duplicate of backport 0043909RR20Q2 closed Retail Error when login into WebPOS having messages pending to synchronize in the state 
blocks defect 0043907 closed migueldejuana Error when login into WebPOS having messages pending to synchronize in the state 
Issue History
2020-05-05 10:25migueldejuanaTypedefect => backport
2020-05-05 10:25migueldejuanaTarget Version => RR20Q2
2020-05-05 10:26migueldejuanaReview Assigned To => migueldejuana
2020-05-05 10:26migueldejuanaRelationship addedduplicate of 0043909
2020-05-05 10:26migueldejuanaStatusscheduled => closed
2020-05-05 10:26migueldejuanaResolutionopen => duplicate

There are no notes attached to this issue.