My code has not been updated in month and for some reason it has suddenly broken lol.
I have found the line causing the issue
let memo = await Random.blob();
I am getting this error in response
Server returned an error:
Code: 400 (Bad Request)
Body: Invalid signature: Invalid basic signature: Ed25519 signature could not be verified: public key e9de264ff18e7faaf551b7bbbab85affed592b82643796abef20f1ff6b5ac9a3, signature 8f92f2f70c22e4bb422c16e8d46c6297391ad8698f6342ae5c8546f0b48c807dd88fdc34da291494f4e5fd03f30fbdaea750784c44fb5a6d7e6152015cc82903, error: A signature was invalid
please can someone at Dfinity have a look into this urgently
I don’t know if its also worth mentioning that once i receive this error from the canister and I try to redeploy the canister (without using --mode reinstall) i get this error:
Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to install all canisters.
Caused by: Failed to install wasm module to canister 'orderbook'.
Caused by: Failed during wasm installation call
Caused by: The replica returned a rejection error: reject code CanisterError, reject message Error from Canister i6gc2-jaaaa-aaaag-ak5dq-cai: Canister called `ic0.trap` with message: canister_pre_upgrade attempted with outstanding message callbacks (try stopping the canister before upgrade)
Canister Backtrace:
unknown function at index 685
.
Consider gracefully handling failures from this canister or altering the canister to handle exceptions. See documentation: http://internetcomputer.org/docs/current/references/execution-errors#trapped-explicitly, error code None
I have been getting this error too when running dfx locally. The function that is producing this error also involves both calls to Random.blob() and the ICRC1 transfer function. It only happens on occasion so I have just been hoping it has something to do with fetchRootKey or just local internet identity in general so have just been ignoring it hoping that it will not occur when I deploy to mainnet.
What leads you to believe that Random.blob() is the culprit?
I have changed my mind. I dont think it is Random blob that is the culprit i just think it is calls that take a long time to execute so a time out error. I am also seeing this error on mainnet