FIX: Fee Asset Selection #11397
<
8000
/div>
Merged
FIX: Fee Asset Selection #11397
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
valentinfernandez1
approved these changes
Mar 19, 2025
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
📝 Description
Sometimes, a discrepancy occurs when selecting fee assets. Specifically, switching between native and non-native assets for fee payment can display an incorrect fee and prevent paying the fee in native tokens until the page is reloaded.
This PR resolves the issue by ensuring seamless switching between fee assets without requiring a page reload.
🤔 Current behaviour
Screen.Recording.2025-03-18.at.13.15.35.mov
✅ Expected behaviour
Screen.Recording.2025-03-18.at.13.16.32.mov