availproject / bridge-ui

UI for the Avail bridge
https://bridge.availproject.org/
8 stars 12 forks source link

Bridge UI: Many reports that some users cannot claim #36

Closed vthunder closed 1 month ago

vthunder commented 1 month ago

Not clear if this is a single issue, and not everyone seems to hit this problem. At this point we cannot repro in house. Reports look like:

Image

This is the corresponding initial tx for that log: https://avail.subscan.io/extrinsic/0xa7749988c115ff4af070e438e05dbd012f18556f15550c36bb31590e12e0e6b8

And from that tx we can look it up in the DB, note that it is READY_TO_CLAIM, suggesting the issue is purely in the frontend/wallet:

Image

Another log:

Image

Logs are all similar.

We've asked for a peek at the Network tab from an affected user, nothing of note:

Image

In that case, the wallets are Subwallet and Metamask, which we can successfully use.

We've also asked to clear cache and cookies, no effect.

Note that we had some issues with CORS early on, but this doesn't seem to be related -- there are no CORS errors in these logs.

mikedemarais commented 1 month ago

indeed an issue

im trying to help a friend, but no combination of wallets is working.

VPNing to another country had no impact either.

my friend is seeing exact errors in their console as posted by OP initClaimAvailToEth

shuklaayush commented 1 month ago

I was able to fix it by manually putting in the amount here. I think the issue might be related to typecasting of the API amount response into BigInt https://github.com/availproject/bridge-ui/blob/7feb7ffac04a7f2d93e789bd15e0b98a448b1d43/hooks/useClaim.ts#L61

junhoyeo commented 1 month ago

I was able to fix it by manually putting in the amount here. I think the issue might be related to typecasting of the API amount response into BigInt

https://github.com/availproject/bridge-ui/blob/7feb7ffac04a7f2d93e789bd15e0b98a448b1d43/hooks/useClaim.ts#L61

Can confirm that this worked for me as well

signorecello commented 1 month ago

Still doesn't work for me, I get invalid leaf. The output of getMerkleProof returns leaf index 0 which is unlikely. Something is not right with the proof API

signorecello commented 1 month ago

I could go and try to get the index from eth storage on the contract but honestly this is just hacking at this point

0xSasaPrsic commented 1 month ago

Closing as fixed.