#No signer found for address

5 messages · Page 1 of 1 (latest)

distant perch
#

if (!signer) throw new Error(No signer found for address ${sender})

in generated client i defined defaultSender and defaultSigner but still i get error No signer found for address

winged scrollBOT
#

Hi @distant perch. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

If you are seeing the error No signer found for address ${sender} even after defining both a defaultSender and defaultSigner in your generated client, it likely means that the signer for the specific sender address you are using has not been registered or is not being picked up as expected.

Here are some key points from the knowledge sources:

  • How signer resolution works: When you send a transaction, the Algorand client tries to find a signer for the sender address. If no signer is registered for that address, it will use the default signer if one is set. If neither is available, it throws the error you are seeing. This is true for both Python and TypeScript SDKs [Get signer].

  • How to register a signer: You can register a signer for a specific address using methods like setSigner or setSignerFromAccount. For a default signer, use setDefaultSigner [Account management TS].

  • How to retrieve a signer: If you call getSigner('SENDER_ADDRESS'), it will return the registered signer for that address, or the default signer if no specific signer is registered. If neither is found, it throws an error [Get a signer TS].

Common causes for this error:

  1. The sender address in your transaction does not match any address for which a signer has been registered.
  2. The default signer is not set correctly, or the client is not using it as a fallback.
  3. There is a mismatch between the sender address format and the registered signers.
#

What you should check:

  • Ensure you have registered the signer for the sender address using setSigner(sender, signer) or setSignerFromAccount(account).
  • If you want to rely on the default signer, make sure you have set it using setDefaultSigner(signer) and that the sender address does not have a conflicting (but missing) signer registration.
  • Double-check that the sender address in your transaction exactly matches the address for which the signer is registered.

Example (TypeScript):

// Set default signer
algorand.account.setDefaultSigner(myDefaultSigner);

// OR register a signer for a specific address
algorand.account.setSigner('SENDER_ADDRESS', myTransactionSigner);

// Now, sending a transaction from SENDER_ADDRESS should work
await algorand.send.payment({
  sender: 'SENDER_ADDRESS',
  receiver: 'RECEIVER_ADDRESS',
  amount: algo(1),
});

If you still get the error, try explicitly registering the signer for the sender address you are using, even if you have set a default signer [Account management TS].

If the problem persists after these checks, please ensure that the sender address is correct and that the signer registration code is executed before sending the transaction.

Summary:
The error means the client cannot find a signer for the sender address and is not falling back to the default signer as expected. Double-check your signer registration and sender address. If you continue to have issues, please provide a code snippet for more targeted help.