The only GetBalance flow in GloebitAPI is synchronous because most flows require a balance response in the flow. This was then used in OnCompleteMovementToRegion() to trigger a balance update when a user enters a Gloebit enabled region. Unfortunately, we discovered (Ubit alerted us) that the OnCompleteMovementToRegion function is being called during the region transition and our call is delaying that from completing. Ubit may fix OnCompleteMovementToRegion so it is called after and separate from important core functionality of the region transition, but we should also have an asynchronous version of GetBalance since this does not need to be completed synchronously here.
mdickson
commented
5 years ago
The only GetBalance flow in GloebitAPI is synchronous because most flows require a balance response in the flow. This was then used in OnCompleteMovementToRegion() to trigger a balance update when a user enters a Gloebit enabled region. Unfortunately, we discovered (Ubit alerted us) that the OnCompleteMovementToRegion function is being called during the region transition and our call is delaying that from completing. Ubit may fix OnCompleteMovementToRegion so it is called after and separate from important core functionality of the region transition, but we should also have an asynchronous version of GetBalance since this does not need to be completed synchronously here.