Bug: Account SDK does not return detailed errors when signer fails to sign transactions

[sazanovtim]

Describe the bug

When using the Base Account SDK to prepare and submit a transaction, if the configured signer fails (for example, due to missing private key, user rejection, or invalid signer state), the SDK often returns a generic error without detailed information about the cause. This makes it difficult for developers to differentiate between signer failure modes and handle them appropriately in the UI.

Steps

Steps to reproduce:

1. Integrate the Base Account SDK in a test application.
2. Configure the account with a signer that will reject signing (e.g., prompt user rejection or undefined private key).
3. Invoke a transaction signing method (e.g., prepare and submit a simple transfer).
4. Catch the error returned by the SDK.
5. Observe that the error lacks structured details indicating why the signing failed.

Expected behavior

When the signer fails to sign a transaction, the SDK should return a structured error object containing specific failure information (e.g., "user_rejected", "missing_private_key", "invalid_signer_state"). This enables applications to display the correct UI message and handle different failure scenarios programmatically.

Version

No response

Additional info

No response

Desktop

No response

Smartphone

No response