Description

~2% of Claim/Withdraw transactions are failing with Safe GS026 or GS013 errors. Root cause: EthQuery caches query results for up to 15 minutes, which can serve a stale nonce when signing Safe transactions. This fix calls invalidateQueryCache before prepareClaim and signWithdraw so the Safe TX is always signed with a fresh nonce.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/PRED-769

Manual testing steps

Feature: Predict Claim/Withdraw nonce freshness

  Scenario: User claims positions without GS026/GS013 errors
    Given the user has claimable positions on Predict
    And the EthQuery cache contains a stale nonce

    When the user initiates a Claim transaction
    Then the query cache is invalidated before signing the Safe TX
    And the transaction succeeds without GS026 or GS013 errors

  Scenario: User withdraws funds without GS026/GS013 errors
    Given the user has a balance available for withdrawal on Predict
    And the EthQuery cache contains a stale nonce

    When the user initiates a Withdraw transaction
    Then the query cache is invalidated before signing the Safe TX
    And the transaction succeeds without GS026 or GS013 errors

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.