We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.0.2
Calling sdk.getTokenBalances() with empty (or valid) account_addresses: string[] returns the error:
sdk.getTokenBalances()
account_addresses: string[]
Uncaught RuntimeError: unreachable
We should be able to fetch all tokens without errors.
Note: I am using the latest torii from main branch, which includes dojo#2777
main
These snippets will raise the error. It looks like the error happens every time there is a result from torii.
useEffect(() => { const _fetch = async () => { // const response: Token[] = await sdk.getTokens([]) const response: TokenBalance[] = await sdk.getTokenBalances( [], // accounts [], // contracts ) console.log("sdk.getTokens() =>>>>>>>>>", response) } if (sdk) { _fetch() } }, [sdk])
const { address } = useAccount() useEffect(() => { const _fetch = async () => { // const response: Token[] = await sdk.getTokens([]) const response: TokenBalance[] = await sdk.getTokenBalances( [address], // accounts [], // contracts ) console.log("sdk.getTokens() =>>>>>>>>>", response) } if (SDK && address) { _fetch() } }, [SDK, address])
Looks like requests are processed Torii and received by the client:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Dojo.js Version
1.0.2
What happened?
Calling
sdk.getTokenBalances()
with empty (or valid)account_addresses: string[]
returns the error:What is the expected behavior?
We should be able to fetch all tokens without errors.
Steps to reproduce
Note: I am using the latest torii from
main
branch, which includes dojo#2777These snippets will raise the error.
It looks like the error happens every time there is a result from torii.
Additional context
Looks like requests are processed Torii and received by the client:
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: