-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix userAssets query enabled config #6243
Conversation
4c55bd1
to
785117c
Compare
try { | ||
const url = `/${chainId}/${address}/assets/?currency=${currency.toLowerCase()}`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was where we were seeing the "No auth" error message on the retries - have it following the same pattern we have elsewhere now
600978a
to
f3f7994
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I think after fixing the serialization issues, this should be good to merge
…ues on the results
…p and fails when trying to index get function
…n userAssets store
…open but missing user assets data
1415171
to
0e8830c
Compare
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Fixes APP-1977
What changed (plus any additional context for devs)
There is a race condition that can happen when we first start the app and do a user assets query function call without the address. We weren't disabling the query function call, resulting in us to just return an empty state and therefore empty objects. There could be a race condition from when we set the incorrect data but before we get the latest data with the account address, when a user could open the swap state, preventing further updates from the user assets store from getting synced.
There were a few different issues happening at the same time, but the retry errors we were getting were not causing this - they were other issues.
This will also be improved once we have Ben's user assets consolidation work in place - we should just make sure to keep some of the changes we introduced here, some of which is more aligned with the original user assets query logic.
Screen recordings / screenshots
RPReplay_Final1730337157.MP4
What to test
Try to open swaps right after starting the app - the input asset may not be selected by default automatically if it hasn't loaded in time, but the input asset list should refresh with updated assets when they arrive.