Closed ifavo closed 1 month ago
I must correct myself, I was able to reproduce and solve the issue by upgrading/downgrading dapp kit in a demo project and somehow it defaults back to 74 also on 1.0.11 again. Sorry for the confusion.
I can reproduce the problem now within VeWorld:
git clone https://github.com/vechain-energy/example-buy-me-a-coffee
npm install
npm start
Within the App:
The problem seems to happen due the persistence feature in VeWorld, which does seem to lose the network used during connection.
Because I don't have a repository to place this issue for VeWorld, I will re-open it here. Is there a public repo for VeWorld?
we are aware of this bug, guys are working on this on the veworld side, thanks for reporting tho 🙌 I'm going to close this here
@davidecarpini thanks a lot 🙏
I have upgraded dApp-kit to 1.0.13 and it fails to build transactions for TestNet and Solo using VeWorld.
My integration is as simple as:
https://node-testnet.vechain.energy
orhttp://localhost:8669
-geneiss is eithertest
or the genesis block from the solo nodemy transaction is done within react:
The transaction is prompted for signing in VeWorld and is always built with chainTag
74
.Downgrading to 1.0.11 solves the problem and it works. The issue seems to have started with 1.0.12.
Has the handling changed or is this an issue within the dapp kit?