[Bug]: auction house listing asset error SaleRequiresExactlyOneSigner

[boredjoker]

Which package is this bug report for?

auction-house

Which Type of Package is this bug report for?

Rust Contract

Issue description

when auction house requires_sign_off is true, how can we listing a asset by user, signing with authority,and send transaction by user(as fee payer),why can't we let user and authority as both signer like last version?

1. last version success transaction

2. new version error transaction
   Error Code: SaleRequiresExactlyOneSigner. Error Number: 6044. Error Message: This sale requires exactly one signer: either the seller or the authority..

3. new version error without authority sign transaction
   Error Code: CannotTakeThisActionWithoutAuctionHouseSignOff. Error Number: 6011. Error Message: Cannot take this action without auction house signing too.

Relevant log output

No response

Priority this issue should have

High (immediate attention needed)

[carriekellar]

Hey we're getting the same error! Any update on this?

[jdnichollsc]

Hello @samuelvanderwaal, do you need more details about this error? Thanks for your help, please let us know how can we help! <3

[samuelvanderwaal]

@boredjoker @carrie-hk @jdnichollsc hey everyone, I'm opening a PR to remove the double signer restriction as there does not appear to be a good reason to keep that in place. Keep in mind that the fee payer still defaults to the auction house fee account with two signers and it's out of scope to refactor this as it affects more than just this handler. However, to work around this you can include a simple system transfer instruction from the user to the auction house fee account if you want the user to pay for the creation of the trade state account.

[carriekellar]

Also @samuelvanderwaal there's a version mismatch on the deployed program see here. It should be v1.4.0, but says v1.3.4

[carriekellar]

This problem isn't in v1.3.4, but when we're calling on devnet we are facing this error! Not too sure what's up there -- maybe an IDL mismatch?

[samuelvanderwaal]

This problem isn't in v1.3.4, but when we're calling on devnet we are facing this error! Not too sure what's up there -- maybe an IDL mismatch?

Yeah probably just an IDL mismatch. I will bump versions and redeploy to both devnet and mainnet today.