Fixed: Solana Blink Action error when signing a custom Anchor Program transaction

As a developer working on connecting a custom Blink Action to your program for a presale, you are probably no stranger to the intricacies of Solana programming. Recently, I encountered an error when signing a custom Anchor Program transaction with Blink Action. In this article, I will explain what may be causing the issue and provide a step-by-step solution.

Error: Unexpected error

When running the following code, the following error occurs:

GOT ERROR Error: Unexpected error
Xe <

This error typically indicates that the transaction signing process encountered an unexpected issue during the Anchor Program validation phase. The exact cause of this error can be difficult to pinpoint without additional context.

Possible Causes and Solutions

This error can have several possible causes, including:

  • Invalid or Missing Anchor Program Contract Code

    : Make sure you have verified that your custom Anchor Program contract is properly deployed with the required code.

  • Incorrect Validation Rules: Make sure that your validation rules in the Anchor Program contract match those specified in the Solana CLI or Anchor Program documentation.
  • Insufficient Validation Inputs: Make sure that all required input values ​​are provided when signing the transaction, as specified by the validation rules.

To resolve this issue, try the following steps:

Step 1: Verify the Anchor Program Contract Deployment

Please double-check that your custom Anchor Program contract is properly deployed with the required code and metadata (e.g., id, name, etc.). Make sure that you have verified that the contract deployment function returns a valid transaction.

const Deployer = require("@solana/web3.js").Deploy;
const anchorProgram = await Deployer.deployYourContractId();
const deployTransaction = await anchorProgram_deployTransaction({
id: your_contract_id,
name: "Your Contract Name",
// Add other required metadata...
});

Step 2: Verify Validation Rules

Make sure that your validation rules in the Anchor Program contract match those specified in the Solana CLI or Anchor Program documentation. You can verify this by examining the validate function in the contract.

const validate = async (tx, programId) => {
// Validate input values ​​here...
if (!tx.amount || !tx.signedBy) {
throw new Error("Invalid validation inputs");
}
};

Step 3: Verify transaction signing inputs

Make sure that all required input values ​​are provided when signing the transaction. You can verify this by checking the transaction metadata.

const tx = await anchorProgram_signTransaction({
id: your_contract_id,
programId,
amount,
signedBy,
// Other required properties...
});

If you have verified that these steps resolve the issue, you should no longer see the “Unexpected error” message. However, if you continue to encounter errors after attempting these fixes, please provide more details about your code and environment for further assistance.

Conclusion

Signing a custom Anchor Program transaction with Blink Action can be a challenging task. By ensuring that the contract deployment is correct, checking the validation rules, and ensuring that all required input values ​​are provided when signing the transaction, you should be able to resolve any issues that arise during this process. If you still encounter issues after attempting these steps, please feel free to contact us for further assistance or support.