-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Events not coming in with Trust Wallet #925
Comments
You should be using your own web3 provider for events or any other activity. Read more details here: trustwallet/trust-web3-provider#58 (comment) |
I do, i am using web3.js, i only want my dapp to work in your browser. So far i don't even know how to debug it |
I now tried using nodesmith.io. Edit:// In case it isn't obvious, i am not using the injected web3.js, never have. I bring my own web3.js and now also tried to use a third party provider. Both don't work Trustwallet. No idea why you closed the ticket really |
this repo not related to the problem. For any issues you can create discussion on https://community.trustwallet.com/c/feedback/2 or https://github.com/trustwallet/trust-web3-provider @MythicalToken show me example of your code that does not work
|
Does not work. Contracts.contract is returning:
As already said i never used trustwallet, so i really have no idea which repo/component is the right one to ask for help. Obviously it is not here but on that forum where i can't post anyway, but have to wait for the support ticket :/ Edit:// Pretty sure the ticket form is the wrong place as well, there is no option that fits my question |
if you are using your own provider - why there is should be an issue on the wallet side? As mentioned before, use your own provider for such calls (which ever node you use, nodesmith, infura and etc) Only use injected provider for sign message and transactions. |
Your wallet contains a browser doesn't it? So if the issue only happens with that specific browser where else should i look for the problem? |
Please read explanation by MetaMask: https://medium.com/metamask/no-longer-injecting-web3-js-4a899ad6e59e. Solution / Explanation from the article: use your own provider for anything not related to signing. If it works today - it does not mean it will work tomorrow, so if you follow this solution it will always work for you, independent from the wallet or the browser you use.
|
I tried to understand all this now but i don't get it. So MetaMask does not ship with web3 anymore, got it, no problem i use my own, have been the whole time. I have to use their provider to gain access to accounts, again obvious, so i am using that. So far this setup works with trustwallet too. I can read & write methods with both. No where does the article you are linking suggest to use my own provider, in fact they even say:
So either the thing you are telling me is that your (trustwallets) default provider is simply not supporting events (then no idea what this would have to do with Metamask) or i simply do not understand what you are talking about. |
I hope this is the right repo, i haven't used Trust Wallet before and am unsure about all its components.
My dApp (https://myth.cash) is not loading any events, you can check this by opening any page other than the startsite, they all have some kind of tables that should display events but don't. I've tried to connect sentry to get any way to catch errors but all i get is:
TypeError: Failed to fetch
The website works as it should with MetaMask a user noticed this for me.
Any ideas how i could fix this behaviour? Or what the actual issue is behind that?
The text was updated successfully, but these errors were encountered: