-
Notifications
You must be signed in to change notification settings - Fork 429
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
TokenIcon issue #5987
Comments
Hey @aiaug, When you say the |
Hey @gregfromstl |
Are you sure your image is available at the path |
yes, that worked |
Excellent, we'll get this triaged and looked into |
Great! |
Hey @aiaug - I can't replicate the issue you mentioned. You can see it working as expected here: https://codesandbox.io/p/devbox/nmdrvg?file=%2Fsrc%2FApp.tsx If you are still facing this issue - Please send a minimal reproduction (either a github repository or sandbox link) Note that if you are just passing a string as |
bro, I don't want customized image instead of default token Icon but yours display example.svg in all case |
in your case, import "./App.css"; import { TokenProvider, TokenIcon, ThirdwebProvider } from "thirdweb/react"; const client = createThirdwebClient({ const USDC_ADDRESS = "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"; function App() {
); export default App; this result displays start image instead of usdc icon. |
@aiaug Its not clear what exactly are you expecting here - Please elaborate. Here's whats happening in this example: The
If you want to resolve the icon using default method and only render a custom icon when resolving fails - you should render the custom icon using |
Thank you for providing this awesome service!
I’ve encountered an issue while using the TokenIcon component.
Here’s the code I’m working with (from the Thirdweb Playground example):
https://playground.thirdweb.com/connect/ui/token
tokenname and tokensymbol is working well, but tokenicon is not working.
The TokenIcon doesn’t seem to be working, even though my client is set up correctly. Is anyone else experiencing this issue?
I am using version 5.85.0
Looking forward to your insights!
The text was updated successfully, but these errors were encountered: