You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When games that are live are using Paima, they need to ensure that the version the user is running locally matches the version running in the server (and throw an error otherwise)
The way this is done now is done by setting the game version in two places:
In the backend, where in paima-runtime, we have an endpoint /backend_version that returns the version used when Paima Engine was initialized.
In the middleware, we have a initMiddlewareCore function that takes in a version number of the app
Now, when a game calls userWalletLogin, we check if the two versions match
Issue
For the backend, the game version is set by ENV.GAME_NODE_VERSION. However, this is simply a constant that never gets updated. Probably we forgot to set this
The localRemoteVersionsCompatible function only checks if the major versions match, and all Paima games have the major version set to 1 so this has never been an issue
The text was updated successfully, but these errors were encountered:
When games that are live are using Paima, they need to ensure that the version the user is running locally matches the version running in the server (and throw an error otherwise)
The way this is done now is done by setting the game version in two places:
paima-runtime
, we have an endpoint/backend_version
that returns the version used when Paima Engine was initialized.initMiddlewareCore
function that takes in a version number of the appNow, when a game calls
userWalletLogin
, we check if the two versions matchIssue
For the backend, the game version is set by
ENV.GAME_NODE_VERSION
. However, this is simply a constant that never gets updated. Probably we forgot to set thisWhy hasn't this been an issue so far?
The
localRemoteVersionsCompatible
function only checks if the major versions match, and all Paima games have the major version set to1
so this has never been an issueThe text was updated successfully, but these errors were encountered: