Closed andrevenancio closed 2 years ago
It looks like the error originates from Temple Wallet: https://github.com/madfish-solutions/templewallet-extension/search?q=intercomerror
If they send that error over postmessage, the beacon-sdk will try to handle it, so the failure to handle the message results in this error.
I am using Temple Wallet as well during development, but I've never seen this error. Do you have anything special in your setup that could explain why you get this error and I don't?
I'll prepare a simple example to replicate it will share in the next couple of hours
Hi!
I'm not sure exactly why this error is happening, but it seems to be coming from this module. this is the error in question:
o {message: "Not Found", errors: undefined, name: "IntercomError"}
If I expand the stack of this error I can see its coming from available-transport.
I was using
airgap/beacon-sdk
directly on my codebase to have access to some Typescript types (import { AccountInfo, Network, NetworkType } from '@airgap/beacon-sdk';
) But I've remove them from my codebase, deleted yarn.lock and re-install my dependencies and its still there, so I'm assuming its a dependency inherited from either taquito/beacon-wallet or taquito/taquito.Either way, this error should probably not happen. Any help anyone can provide to explain what is happening?