Update action?

[hart2hart]

@firstoneand @gzahar  I installed PGx 3.2.1 yesterday and 3.2.2 today.  the NS shows 1.0.0 as the latest version and I show having 1.0.00 installed. "Update" is listed as the action (I'm thinking the difference between 1.0.00 and 1.0.0) but taking that action does not result in it being upgraded to 1.0.0 as it stays at 1.0.00 so "Update" remains as the action.  

[bpwwer]

Update is triggered on a difference between the installed version and version listed in the store.  It's a simple string comparison so yes, 1.0.00 is different from 1.0.0 and thus there's an update available (per the logic in PG3x).

[hart2hart]

Update is triggered on a difference between the installed version and version listed in the store.  It's a simple string comparison so yes, 1.0.00 is different from 1.0.0 and thus there's an update available (per the logic in PG3x).

Thanks for confirming. Do you know if data will be corrected so it shows correctly as installed is 1.0.0?

[bpwwer]

That's up to the developer to fix.  They control what shows up in the store and what the node server reports as it's version.  Unfortunately, we don't have any way to link those so the developer must make sure they both match.

[hart2hart]

That's up to the developer to fix.  They control what shows up in the store and what the node server reports as it's version.  Unfortunately, we don't have any way to link those so the developer must make sure they both match.

Thanks. I tagged developer in first entry so we’ll see if they respond.

[firstone]

On 8/18/2023 at 2:57 PM, hart2hart said:

@firstoneand @gzahar  I installed PGx 3.2.1 yesterday and 3.2.2 today.  the NS shows 1.0.0 as the latest version and I show having 1.0.00 installed. "Update" is listed as the action (I'm thinking the difference between 1.0.00 and 1.0.0) but taking that action does not result in it being upgraded to 1.0.0 as it stays at 1.0.00 so "Update" remains as the action.  

Removed extra 0. Next time it "updates", it should get fixed.

[hart2hart]

5 hours ago, firstone said:

Removed extra 0. Next time it "updates", it should get fixed.

Thank you @firstone for the Nodeserver and the fix.  I just ran Update and eISYIR versioning is now in sync.