getCallsStatus indicates failure despite transactions succeeding

[ga-reth]

using the 5792 hooks to batch send erc20 approval and contract call, the sendCalls mutation succeeds, as do the on chain transactions, but the result of getCallsStatus has a status of failure

statusCode is 500 - indicating a chain rules failure and that the batch reverted completely (see here).

any ideas? tried to using showCallsStatus but it's widely supported by wallets

FWIW the atomic capabilities value of the wallet i'm using is supported and i'm using metamask (account on this chain is a mm smart account also)

you can see the successful tx hash here

code

const { sendCallsAsync, data: callsId } = useSendCalls()
const { data: status } = useCallsStatus({
    id: callsId?.id ?? '',
    query: { enabled: !!callsId?.id, refetchInterval: 1000 },
})

// simply doing an approval for demo
const batch = async (amount: string) => {
    if (!address) return
    return await sendCallsAsync({
      calls: [
        {
          to: someToken,
          abi: erc20Abi,
          functionName: 'approve',
          args: [nomina, parseUnits(amount, 18)],
        },
      ],
      forceAtomic: true,
    })
  }

useCallsStatus result

{
    atomic: true,
    chainId: 1,
    id: "0xab2de19a5c66491b9cfe3c289c4a0662",
    receipts: [],
    status: "failure",
    statusCode: 500
    version: "2.0.0"

[jxom]

Wagmi just forwards on the status from the wallet. I would suggest to raise this as an issue on the MM repo.

[ga-reth]

thanks @jxom, i'll raise with them

in your experience, which wallets are most stable with this 5792 functionality? to unblock working through the implementation in the meantime