Always return to main menu at the end of get_wallet_address #282
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because of the asynchronous nature of the new UX (which returns the response from a command before the 'status' UX is cleared and its callback is called), some race conditions could be triggered in some situations where the
G_is_timeout_active.processing
global is not properly managed, possibly not clearing theProcessing
screen, giving the impression that the app is stuck, despite the app correctly returned from previous commands (sending a new command would actually clear it).In version
2.2.4
of the app, this happened in particular whenregister_wallet
for a relatively complex policy is followed by a silentget_wallet_address
(which is indeed common because the client libraries do this automatically).This PR forces to clear the UX after
get_wallet_address
; it is likely that other conditions could trigger the same issue, so this is left for a future PR as it requires a rethinking of the state machine managing the UX and theProcessing
screen.Opened a separate issue #283 for a more general solution to the problem.