Mobile application caches password in transaction signing form

[Balanced02]

Expected behavior

Should not cache users password in the transaction signing form

Actual behavior

Caches users password in transaction signing form

Steps to reproduce

• Create a new, invalid transaction in the “Send token” form. To make the transaction invalid, set the amount to larger value than available balance
• Click “Continue” button, and then “Send” button
• Provide password
• The transaction will fail as shown in figure 87.1, in the left screenshot
• Click “Try again” button
• Change parameters of the transaction arbitrarily and make the transaction valid
• Again click the “Continue” button, and then the “Send” button
• The password will be populated automatically and can be made visible by clicking the “eye” icon

Which version(s) does this affect? (Environment, OS, etc...)

• Android and iOS