Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
don't update currency rates on transient errors (#4662)
## Explanation We think in MetaMask/metamask-mobile#11035, the intermittent 0 balances were caused by transient errors in requests to crypto compare. Instead of setting the conversion rate to null in this case, we'll omit the state update and keep the conversion rate from the previous successful fetch. ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/assets-controllers` - **FIXED**: In `CurrencyRateController` if unexpected errors occur during requests to crypto compare, the conversion rate in state will remain unchanged instead of being set to null. ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate - [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate
- Loading branch information