we’ve encountered another problem here. ic-validator-ingress is indirectly using the ic0 api somewhere (probably not called at all). This was fine for us on x86 as it doesn’t try to link to the “ic0” module, but is a problem if we use it in apps targeting the wasm32 platform while not being a canister, as it seems to be forcing the linking of this module.
More specifically this is the error that I get: "ic0": module is not an object or function if we try to use it in a wasm32 app
EDIT: minimal reproduction: GitHub - rupansh-sekar-yral/ic-validator-ingress-message-wasm32
You can run npx wrangler dev to check
EDIT2: I manually patched the dfn_core crate and im using the following workaround in Cargo.toml for now:
[patch."git+https://github.com/dfinity/ic.git"]
dfn_core = { git = "https://github.com/yral-dapp/ic", rev = "1275d4affb39c0049a897f4b52541de82ad49c2b" }