"Response errors; Validity(InsufficientFeeAmount { expected: 652174, provided: 0 })" })

[chlenc]

gm guys, i trying to send some money to my contract address, but the call fails with error "Response errors; Validity(InsufficientFeeAmount { expected: 652174, provided: 0 })" }), can you help me how to fix that

    let amount = usdc.parse_units(3000_f64) as u64;
    usdc.mint(admin.address().into(), amount).await.unwrap();

    admin
        .force_transfer_to_contract(
            &spark.insurance_fund.contract_id(),
            amount,
            usdc.asset_id,
            TxPolicies::default()
                .with_gas_price(2)
                .with_max_fee(1000000000),
        )
        .await
        .unwrap();
        

    `fuels = { version = "0.55", features = ["fuel-core-lib"] }`

        Default host: aarch64-apple-darwin
fuelup home: /Users/alexey/.fuelup

installed toolchains
--------------------
beta-5-aarch64-apple-darwin
latest-aarch64-apple-darwin (default)
nightly-2024-01-24-aarch64-apple-darwin
nightly-2024-03-30-aarch64-apple-darwin

active toolchain
----------------
latest-aarch64-apple-darwin (default)
  forc : 0.49.3
    - forc-client
      - forc-deploy : 0.49.3
      - forc-run : 0.49.3
    - forc-crypto : 0.49.3
    - forc-doc : 0.49.3
    - forc-explore : 0.28.1
    - forc-fmt : 0.49.3
    - forc-lsp : 0.49.3
    - forc-tx : 0.49.3
    - forc-wallet : 0.4.3
  fuel-core : 0.22.1
  fuel-core-keygen : 0.22.1

fuels versions
--------------
forc : 0.54.0
forc-wallet : 0.54.0

[segfault-magnet]

This should have been solved here. It was released as 0.55.1 so it should be picked up by your cargo.

Make sure you run cargo update just in case your Cargo.lock still points to 0.55.0.

@hal3e fyi.

[Oleksii-Kshenskyi]

This should have been solved here. It was released as 0.55.1 so it should be picked up by your cargo.

Make sure you run cargo update just in case your Cargo.lock still points to 0.55.0.

@hal3e fyi.

Unfortunately I do know that it should have been fixed in 0.55.1 and I've checked and re-checked multiple times that we were using the correct version in our matcher. As you can see in the screenshot, we really do. And the issue is still there. Our production env matcher has just encountered this too. The only workaround we have for now is to create a new wallet for this and restart the matcher app.