Skip to content
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

Method eth_call should require redirect to the Metamask Mobile app #150

Closed
dms120 opened this issue Jun 21, 2023 · 5 comments
Closed

Method eth_call should require redirect to the Metamask Mobile app #150

dms120 opened this issue Jun 21, 2023 · 5 comments
Labels
enhancement New feature or request

Comments

@dms120
Copy link

dms120 commented Jun 21, 2023

Describe the bug
After the connection is established and connectionStatusis linked i am not able to get responses from a call to a smart contract without manually entering on the MM mobile application and returning to my application.

To Reproduce
Steps to reproduce the behaviour:

  1. Initialize the SDK and successfully establish connection
  2. Initialize a Smart Contract and try to call a method
  3. RCPMS::_write method eth_call doesn't need redirect. is logged and no value is returned

Expected behaviour
I should be able to have a response from the eth_call. If the only way to accomplish this is by redirecting the user to the MM app, the redirect should occur.

Screenshots
If applicable, add screenshots to help explain your problem.

** Provide environment information**

  • Platform (Eg. Web / React-Native / Node.js / Unity): NextJS
  • MetaMask SDK Version: 0.3.2
  • MetaMask Mobile Version: 7.0.1
  • Browser (if relevant): Chrome Android
@abigail-0111
Copy link

same problem.. have any ideas?

@abigail-0111
Copy link

i got 'RCPMS::_write method eth_getBalance doesn't need redirect.', so i switch to metamask mobile and switch back to my dapp, got balance value, it seem work?

@andreahaku andreahaku added the bug Something isn't working label Jul 5, 2023
@andreahaku
Copy link
Contributor

We are aware of the issue and we are working on finding a solution that doesn't break the UX by calling the MM mobile app on every RPC call.

One option may be having an Infura key that the MM SDK can use to query the network for all the requests that don't necessarily need the MM mobile app to be awakened.

@andreahaku andreahaku added enhancement New feature or request and removed bug Something isn't working labels Jul 5, 2023
@dms120
Copy link
Author

dms120 commented Jul 5, 2023

We are aware of the issue and we are working on finding a solution that doesn't break the UX by calling the MM mobile app on every RPC call.

One option may be having an Infura key that the MM SDK can use to query the network for all the requests that don't necessarily need the MM mobile app to be awakened.

That would be ideal because otherwise, i'm thinking in using a default RPC url to make these requests.

@christopherferreira9
Copy link
Collaborator

Hi all! This has been address in the latest Wagmi connectors (2.12.22)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants