Closed johnnymatthews closed 3 months ago
Nope, got the same error even after removing the line-breaks. Let me try a smaller message.
Hmmm, this time I tried Hello World!
as the message and got a different error:
/root/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12218
throw new Error(
^
Error: request failed 500, Internal Server Error fetch: http://44.204.64.128:3001/user/sign_tx FULLRESPONSE: Invalid Signer: Invalid Signer in Signing group
at sendHttpPost (/root/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12218:11)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /root/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12769:26
at async Promise.all (index 0)
at async SignatureRequestManager.sign (/root/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12670:18)
at async SignatureRequestManager.signWithAdaptersInOrder (/root/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12636:23)
at async Entropy.signWithAdaptersInOrder (/root/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:13186:12)
at async Object.sign (/root/cli/src/flows/sign/index.ts:91:24)
at async main (/root/cli/src/index.ts:89:30)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command
Tried with a message Will I Am went missing.
and everything worked fine... Maybe the CLI doesn't like special characters or long messages?
the special characters aren't an issue, the error you faced is a known issue with polkadot and how its handling our adapters, which is sorta being handled in #63 the real issue here is the length of the message being signed.
real issue here is the length of the message being signed.
This'll be mostly addressed by https://github.com/entropyxyz/entropy-docs/issues/112. Gonna close this one for now.
I just hit this error when trying to sign a message:
The message I was signing was this (from Alice in Wonderland):
Dunno if the line-breaks are freaking the signer out. I'll try again without them.