[BUG][GUI] Don't return StakingOnlyUnlocked from WalletModel::sendCoins #2104
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.
Bug found in current master.
Steps to reproduce
for staking only.Issue:
Instead of sending the tx, the wallet asks again for the password, and still doesn't send the transaction (without any feedback) even when the password is entered a second time.
Cause:
By the time the flow reaches
WalletModel::sendCoins, the UnlockContext is lost, and the wallet has been relocked (for staking only) already.This is correct, as the transaction is created and signed in
WalletModel::prepareTransaction, andsendCoinsonly commits the transaction, therefore it doesn't need a fully-unlocked wallet.The function, though, currently returns early with return value
SendCoinsReturn::StakingOnlyUnlocked, if the wallet is unlocked for-staking-only, and the transaction isn't sent.Fix:
Simply remove the un-needed check in sendCoins.