try catch will hide the real error when instruction function parameter name does not match with #[instruction()]

[neil4dong]

https://github.com/coral-xyz/anchor/blame/72c7e09538f38fa98de56caeee6e8c030c8b66b2/ts/packages/anchor/src/program/accounts-resolver.ts#L337

Ambiguous error

but when I added console.error to the catch block, the actual error is

[acheroncrypto]

Thanks for creating the issue. This indeed looks like a problem, but it's a bit tricky to solve because of the issue mentioned above the try block:

anchor/ts/packages/anchor/src/program/accounts-resolver.ts

Lines 316 to 319 in 72c7e09

	// Accounts might not get resolved successfully if a seed depends on
	// another seed to be resolved *and* the accounts for resolution are
	// out of order. In this case, skip the accounts that throw in order
	// to resolve those accounts later.

To solve this problem, we can:

• Enforce the parameter names to be identical from Rust side (or at least in the IDL)
• Store the errors that get caught and show them if resolution fails due to reaching max depth.

Related: you should at least get which account has the resolution issue after #3207.