Enrique Arrieta
Enrique Arrieta
This is most likely an issue with your code/domain/walletconnect integration/etc so you will need to give more details (sharing your full code/integration or the public site where we can test...
If you are instantiating the walletconnect client twice then you will have a race problem between both. I suggest only starting the one that will be needed at a time...
> NO SIDE EFFECTS: need isConnected, need explicit requestAccess, and getAddress should NEVER open a modal Question: how can you sign using a, let's say, Ledger device without showing a...
@pselle it depends, because if all you care is Freighter's flow then maybe is better to not use the kit and instead just use their api directly because it's the...
@jeesunikim also writing here to give the update: I added the `skipRequestAccess` parameter to the `getAddress` method so Freighter's module doesn't request access to the wallet if set to true....
@jeesunikim I just submitted a new version that includes the fix for the typescript type.
Hi @chadoh, I understand the concern, and it's something I've been working on in the past few weeks for the v2 of the kit. Unfortunately it's impossible to prevent the...
Yeah I can add this, I will add it in the next release
@janewang I agree with @JakeUrban in not showing the wallet if we know is unsupported by the platform, I also believe is going to be difficult to know that a...
@jeesunikim is there a public preview with that one? I need to see how the kit is attaching the modal to the DOM in order to be able to fix...