`api-contracts`: handle foreign events gracefully

[peetzweg]

`api-contracts`: handle foreign events gracefully

[tad3j]

Could #5791 be responsible for this error?
Expected Option<*> definition for accountId in ContractEnvironment
I started getting this today with this new version but it works in old one so it seems like a breaking change?

[tad3j]

It's failing on line marked bellow (old version of code) when parsing this abi.

Code:

const contract = new PinkContractPromise(
      this.api,
      this.registry,
      contractAbi,
      contractAddress,
      contractKey,
    );
const keyring = new Keyring({ type: 'sr25519' });
const account = keyring.addFromUri('//Alice');
const certificate = await signCertificate({ api: this.api, pair: account });
onst response = await contract.query.encryptContent(
      account.address,
      {
        cert: certificate,
      },
      content,
    );
return response.output.toJSON()['ok'].ok;

[tad3j]

I'm using @phala/sdk. They've said they dont support ink v5 so maybe that's why it didn't work.

EDIT: I've completely removed phala but TX signing is still failing.

[peetzweg]

@tad3j Feels unlikely to me but not impossible. Could you share some code and steps to reproduce this? In which context is this happening?

[peetzweg]

@tad3j I was able to instantiate a ContractPromise instance without a problem with the latest pjs version.

Here is my code:

import { ApiPromise, WsProvider } from "@polkadot/api";
import { ContractPromise } from "@polkadot/api-contract";
import abi from "./abi.json";

const wsProvider = new WsProvider(`wss://rococo-contracts-rpc.polkadot.io`);
const api = await ApiPromise.create({
  provider: wsProvider,
});
const address = "5EnufwqqxnkWT6hc1LgjYWQGUsqQCtcr5192K2HuQJtRJgCi";

try {
  const contract = new ContractPromise(api, abi, address);
  console.log({ environment: contract.abi.environment });
} catch (error) {
  console.error("Initializing contract error", error);
}

process.exit(0);

You could run it by i.e npx tsx abi.ts

Not sure what the PinkContractPromise is about in your code. Maybe you are using some sort of wrapper library?

[tad3j]

Strange, maybe it's issue with Phala SDK...will check.

Locking to "@polkadot/types": "10.11.3", (version we used before) fixes the issue.

[peetzweg]

@tad3j can you share which sdk you are using? Sounds reasonable that it might cause issues with sdks building ontop of pjs. They have probably not yet upgraded their sdk and this could cause hiccups.