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
There is no loader on farming details while data is being loaded.
For some reason I don’t see a loader on farming details when the data is being pulled, and sometimes the start staking button is displayed although 91% pool stake is shared and if you go deeper into the details -> after the stake is loaded and there are already claim rewards and edit farm buttons - so here’s the intermediate there is no state in the form of a loader yet.
Expected behavior
We need to add a loader to farming details while the data is being loaded and staking is being pulled up.
Environment
{"label"=>"Stage"}
OS version
17.2.1
Additional context
Version 3.8.4(7) TF
The text was updated successfully, but these errors were encountered:
Trezeguet1
added
bug
Something isn't working
S2-major
Causes part of the system to not work properly. Has a significant impact on the UX
labels
Mar 22, 2024
Trezeguet1
changed the title
[Bug]: There is no loader on farming details while data is being loaded
[Bug]: iOS - There is no loader on farming details while data is being loaded
Mar 22, 2024
Preconditions
User has staking percents on farm
Steps to reproduce
Actual behavior
There is no loader on farming details while data is being loaded.
For some reason I don’t see a loader on farming details when the data is being pulled, and sometimes the start staking button is displayed although 91% pool stake is shared and if you go deeper into the details -> after the stake is loaded and there are already claim rewards and edit farm buttons - so here’s the intermediate there is no state in the form of a loader yet.
Expected behavior
We need to add a loader to farming details while the data is being loaded and staking is being pulled up.
Environment
{"label"=>"Stage"}
OS version
17.2.1
Additional context
Version 3.8.4(7) TF
The text was updated successfully, but these errors were encountered: