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
OS Version: Windows 10 (1909, Build 18363.1316)
Wallet App Version: 2.1.6
Issue:
Not possible to add BTC/DFI to Liquidity Mining.
Error message is displayed (Code 16). See attached picture.
Expected behavior :
It should be possible to add BTC/DFI to Liquidity Mining without error.
Proposal:
In case of error please display a readable message which makes it clear what the root cause of the error is. Use an unique error Code which is explained in detail in the Help Menu or in a FAQ section, add a link to this in the error message. Also explain what the user should do now.
The DeFi App "Logs" menu should lead to specific Log files (or a function witch creates a DebugInfo.zip which can be uploaded here) to support the developer.
Steps to Reproduce:
Go to Liquidity section.
Select BTC-DFI
Click on Add more
Click on "MAX" next to DFI
Click on Next
Click Supply
→ Error is displayed (code 16)
Comment:
Looks like there is probably a mismatch between available coins and tokens. The point is the end user can not know what the issue is here and what to to next. The system should fix this in the background.
Please let me know if I can support you.
Attachment:
The text was updated successfully, but these errors were encountered:
OS Version: Windows 10 (1909, Build 18363.1316)
Wallet App Version: 2.1.6
Issue:
Not possible to add BTC/DFI to Liquidity Mining.
Error message is displayed (Code 16). See attached picture.
Expected behavior :
It should be possible to add BTC/DFI to Liquidity Mining without error.
Proposal:
Steps to Reproduce:
Go to Liquidity section.
Select BTC-DFI
Click on Add more
Click on "MAX" next to DFI
Click on Next
Click Supply
→ Error is displayed (code 16)
Comment:
Looks like there is probably a mismatch between available coins and tokens. The point is the end user can not know what the issue is here and what to to next. The system should fix this in the background.
Please let me know if I can support you.
Attachment:
The text was updated successfully, but these errors were encountered: