AcalaNetwork / Acala

Acala - cross-chain DeFi hub and stablecoin based on Substrate for Polkadot and Kusama.
https://acala.network
GNU General Public License v3.0
740 stars 533 forks source link

Unable to use Acala Bridge using latest Brave browser #2710

Open ltfschoen opened 9 months ago

ltfschoen commented 9 months ago

My Acala Address: 5F2QSwPHobet1pLFTEw6mkcT8bwZdEMmHfBGYPkiK7Pgxdex

Describe the bug

Expected Behavior

It should allow me to bridge tokens to Acala

Current Behavior

Acala Bridge appears unresponsive https://apps.acala.network/bridge. Latest Brave Browser console gives error

main.75c3f1f0.js:2 2024-02-22 10:04:26             VEC: Unable to decode on index 45 createType(Lookup0):: Invalid AccountId provided, expected 32 bytes, found 20

main.75c3f1f0.js:2 2024-02-22 10:04:26        RPC-CORE: subscribeStorage(keys?: Vec<StorageKey>): StorageChangeSet:: createType(Vec<StorageKey>):: createType(Lookup0):: Invalid AccountId provided, expected 32 bytes, found 20

Uncaught Error: createType(Vec<StorageKey>):: createType(Lookup0):: Invalid AccountId provided, expected 32 bytes, found 20

Steps to Reproduce

  1. Connect an account using Polkadot.js
  2. Go to https://apps.acala.network/bridge
  3. Choose Polkadot to Acala
  4. Choose to sent to same destination account as the origin account

Additional context

xlc commented 9 months ago

what extensions do you have?

ltfschoen commented 9 months ago

Polkadot.js, Metamask, Talisman, Argent X, Keplr.

Maybe it could also be something to do with this? https://github.com/polkadot-js/extension/issues/1250#issuecomment-1931926244

xlc commented 9 months ago

Yeah most likely you have evm account and the dapp wasn't handling it correctly. Will get someone to take a look.