-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
[Bug]: Async call fails to return to Dapp #979
Comments
You'll need to give me a test eth account and i'll send you some eXEQ tokens for testing |
Same for me! |
any updates on this @abretonc7s |
I did some tests with cap. So:
|
the tes app i provided is not using the browser. its javascript to metamask mobile wallet. |
It doen't matter, app or mobile browser. |
and one of my testers is using iphone and it's not returning. |
Can confirm not working on iOS latest MetaMask app 7.28.0 on ip13 pro and latest iOS 17.6.1. |
Iphone 11, IOS 17.5.1, chrome mobile browser. In Metamask app after cap transaction I got "Go back to app" message and I have to go back manually, but Promise resolves. |
@muscleman @BigslimVdub |
actually on my iphone 14 this setting is on and it works for me |
Hmm I just tried this with smart transactions off and it worked first try, no issues or delays |
But still there is a bug in Metamask app with smart transactions, it does not resolve Promise, need to be fixed |
Hi all! |
SDK
Node.js
Provide environment information
works fine for me in Missouri, Does not work for my tester in St Louis or Poland
MetaMask SDK Version
0.27.0
MetaMask Mobile app Version
7.27.1 (1369)
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
pure js provided
Describe the Bug
the first call to approve a spending cap never returns execution back to the calling application.
So the next call to spend the allowance never gets called.
weird thing, when i run this it works. when my tester run this it doesn't return.
if they cancel the allowance/spend cap, execution returns to the app.
Expected Behavior
user can approve a spending cap, execution returns to my app and the user then approves my bridge to spend and burn the allowance.
Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster
https://github.com/muscleman/web3-tester
To Reproduce
run tester app.
app invokes the following method.
await tokenContract.methods.approve(this.bridge_address, web3.utils.toWei(1, "ether")).send({ from: tokenWalletAddress })
approve the spending cap in the mobile wallet
never returns execution in the app, no further code is executed.
when i run this locally, all works fine.
now, for me running the script, all works fine.
The text was updated successfully, but these errors were encountered: