0041323: Store server source version check not comparable with central server version check

Description

In the changes introduced in the related issue the assumption was that the same source code would result in the checksum being the same on central and store. This showed however not to be true.

Snippet from email:
The mechanism to check if the webpos and store server have the same version uses the source version code. This source version code can be retrieved in the javascript console in the browser with:
OB.UTIL.localStorage.getItem('SourceVersion_' + OB.MobileApp.model.get('appName'))
(after logging into webpos)

The source version code is also used to generate the javascript source filename. The store server and the central server should have the same source version code, so the same filename. You can find the javascript file in the webapps folder of tomcat and then:
openbravo/web/js/gen
(this folder might not yet be there on a ss, to let it be generated visit the webpos url of the store server directly, that's the reason I indicated to visit that url, just to make sure the file gets generated once)

The current cs source version is:
8d54a111656735b15960db18558c8bb7
So the javascript source file in the above gen directory in cs is: 8d54a111656735b15960db18558c8bb7_WebPOS.js

We are fine if the store servers have the same javascript source filename (as this means they have the same source version code generated).

What I see however when I check some store servers at the customer:
store1: 0f726c47e2c1a090e04c482a6c8c80e5_WebPOS.js
store2: 0f726c47e2c1a090e04c482a6c8c80e5_WebPOS.js
store3: 0f726c47e2c1a090e04c482a6c8c80e5_WebPOS.js

So all these store servers generate the same source version but a different one than central. This eventhough the source files are exactly the same (I did a byte-byte comparison).

Steps To Reproduce

Have store and central in same version but run them on different images

Proposed Solution

backout related issue

Issue History
Date Modified	Username	Field	Change
2019-07-09 15:57	mtaal	New Issue
2019-07-09 15:57	mtaal	Assigned To	=> mtaal
2019-07-09 15:57	mtaal	Triggers an Emergency Pack	=> No
2019-07-09 15:57	mtaal	Relationship added	caused by 0041069
2019-07-11 22:17	mtaal	Status	new => closed
2019-07-11 22:17	mtaal	Resolution	open => invalid

Notes
There are no notes attached to this issue.