The error as mentioned in the topic and attached as screenshot here is coming when we use our Smart Contract: indexed: 6310, with our Contract Schema which is:
The base64 conversion of the schema is:
//8DAQAAAAsAAABFZHVidWtlU2VhbAACAAAABwAAAGdldEZpbGUGHiAAAAAVAgAAAAQAAABOb25lAgQAAABTb21lAQEAAAAUAAIAAAAJAAAAdGltZXN0YW1wDQcAAAB3aXRuZXNzCxUFAAAACwAAAFBhcnNlUGFyYW1zAgcAAABMb2dGdWxsAgwAAABMb2dNYWxmb3JtZWQCCwAAAE9ubHlBY2NvdW50AhEAAABBbHJlYWR5UmVnaXN0ZXJlZAIMAAAAcmVnaXN0ZXJGaWxlBB4gAAAAFQUAAAALAAAAUGFyc2VQYXJhbXMCBwAAAExvZ0Z1bGwCDAAAAExvZ01hbGZvcm1lZAILAAAAT25seUFjY291bnQCEQAAAEFscmVhZHlSZWdpc3RlcmVkAgEVAQAAAAwAAABSZWdpc3RyYXRpb24BAQAAABQAAwAAAAkAAABmaWxlX2hhc2geIAAAAAcAAAB3aXRuZXNzCwkAAAB0aW1lc3RhbXAN
however the same error does not come, and all works fine: when we use old Smart Contract deployed (by Concordium easeling app) indexed: 2481 with their contract schema (which is different from our contract schema given above).
So our question is how can we do away with the only error we are getting while computing the register file: using our contract: 6310 (index) and our contract Schema. thank you.
Hi @Doris : thanks a lot man! a small fix but yes, updated the name of the contract and it is working perfectly. Consider this resolved now. thanks a lot.