Aaron Cook

> @iamacook @katspaugh Can I fix this? @SandeepGumaste, thank you for reporting the bug! You're more than welcome to look into this. It looks like it's related to the [claiming...

> The user still see the "1 to confirm" even tho the current connected user cannot confirm it I am looking into this issue from the backend perspective now. Edit:...

@francovenica, the "1 to confirm" issue appears to be solved now that we've merged the fix on our end.

> It seems to be indeed something on CGW, it returns > > ``` > "implementation": { > "value": "0x29fcB43b46531BcA003ddC8FCB67FFE91900C762", > "name": "SafeL2 1.4.1", > "logoUri": "https://safe-transaction-assets.safe.global/contracts/logos/0x29fcB43b46531BcA003ddC8FCB67FFE91900C762.png" > }, >...

I believe this is an issue on their side: https://github.com/MetaMask/metamask-mobile/issues/6655.

> can not reproduce now I'd suggest we close this now then (if you are in agreement). Consuming the queue directly likely solved this issue.

@liliya-soroka, can you test this again? After queuing 10 fully signed transactions, I was able to execute them immediately after each other without issue.

This only requires alterations on the backend to work. @fmrsabino, can we transfer this issue to the gateway?

I'm going to close this as we have now have https://github.com/safe-global/safe-client-gateway-sdk.

~I'm marking this as a draft whilst addressing the tests.~