You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The application is unable to execute transactions with gas price set to 0 on free gas networks. Metamask reports 0 as invalid number.
Screenshots
To Reproduce Steps to reproduce the behavior
Connect to a Free Gas Network
Execute a transaction and try to set the gas price to 0
See error
Expected behavior
The app should allow the execution of a transaction on a free gas network and let the user modify accordingly the advanced transaction fee settings.
Smartphone (please complete the following information):
Device: iPhone6s
OS: iOS 14.0.1
App Version v1.0.3 (528)
to be added after bug submission by internal support / PM Severity
How critical is the impact of this bug on a user?
Add stats if available on % of customers impacted
Is this visible to all users?
Is this tech debt?
The text was updated successfully, but these errors were encountered:
What advantage was obtained by making this change? In my current use, it prevents mobile users from accessing smart contract methods on private networks, that are available to the desktop version.
TL;DR: Please allow zero in custom gas price, unless there is a security reason not to.
This issue was closed because it has been stalled for 7 days with no activity. If you feel this was closed in error please reopen and provide evidence on the current production app. Thank you for your contributions.
Describe the bug
The application is unable to execute transactions with gas price set to 0 on free gas networks. Metamask reports 0 as invalid number.
Screenshots
To Reproduce
Steps to reproduce the behavior
Expected behavior
The app should allow the execution of a transaction on a free gas network and let the user modify accordingly the advanced transaction fee settings.
Smartphone (please complete the following information):
to be added after bug submission by internal support / PM
Severity
The text was updated successfully, but these errors were encountered: