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
For androidNode we manage versioning directly using gradle because we have static control of it.
For the xClients, after the first release we will need some sort of versioning handshake to manage the app bisq required version (R) and the trusted node runing version (V):
R <= V. -> proceed normally
R > V -> Overlay error requesting the user to upgrade the trusted node, only option is to quit the client
From a UX perspective, I think the best is to present the user with the TrustedNode onboarding setup screen to give the option to connect to other trusted node, and also use the test button to verify it can connect and check if the trusted node upgraded its running version
The text was updated successfully, but these errors were encountered:
For
androidNode
we manage versioning directly using gradle because we have static control of it.For the
xClients
, after the first release we will need some sort of versioning handshake to manage the app bisq required version (R
) and the trusted node runing version (V
):From a UX perspective, I think the best is to present the user with the TrustedNode onboarding setup screen to give the option to connect to other trusted node, and also use the test button to verify it can connect and check if the trusted node upgraded its running version
The text was updated successfully, but these errors were encountered: