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.
After some reports of the "custom token import" failing, I did a check of valid urls to confirm our code was correct.
The only change was for bsc, and I set some others to null where I was unable to get a valid url from known contracts on a network and a variety of "platform" values (e.g. ftm, fantom, ftm20 etc).
When building this locally to test, I was still unable to import tokens, despite using the contract in the url comments in this PR, so there appears to be a deeper issue, or perhaps this is dead code, and the logic needing a change is in the Flutter DeFi SDK repo.
This error message may be improved to say "No token info found for contract in CoinGecko API", and a log in the console with full url for further debugging.
Curiously, while testing my PR, I was unable to find the expected coingecko api url in either the console or network tabs or my browser.
@CharlVS @takenagain @TazzyMeister I invite you to further investigate and offer a solution.