If the client's clock differs from the server's clock more than a few minutes, no indication of the problem arrives at the user, just silent non-operation. To fix this, the low-level error codes sent by the server should be extended by a specific one for this problem, and the client should implement proper exception handling for this code.
Client fixed in Rev. a6057fd50629c3bef9684577bb9dccb5afac9f68.
Rollout of server feature postponed, because this error code could cause RuntimeException in prior clients because of a previous implementation bug.
If the client's clock differs from the server's clock more than a few minutes, no indication of the problem arrives at the user, just silent non-operation. To fix this, the low-level error codes sent by the server should be extended by a specific one for this problem, and the client should implement proper exception handling for this code.