Error building contract

[PaulZhemanov]

Hi guys! I posted earlier my problem that I have never been able to solve on the same issue. Here are the links for your reference.

Mystical mistake on the sames toolchains

hi guys! me with my friend running the same simple smart contract with absolutly similar toolchains and we got this… my laptop: [image] @fuel laptop: [telegram-cloud-photo-size-2-5465302179029045873-y] My build is ok, but Alex’s is failed. Help us please understand why it happend

Mystical mistake on the sames toolchains 2

Continuing the question… My issue is still not resolved. Running forc check inside contract is ok, but i got problems with building. [image] … [image] Help me reinstall forc or another stuff… I cant solve this problem long time…

Improve the way plugins are selected

I can’t build the contract due to Fork version conflicts. How do I properly uninstall and then install the latest version of Fork?

Now i cant build another contract . You can try with the build contract following the instructions from this topic

Error " IOError(Custom { kind: Other, error: "Response errors;" running open_order function

Hi guys! I’m developing a script create_order for orderbook. I got this mistake: Failed to open order: IOError(Custom { kind: Other, error: "Response errors; Validity(InsufficientFeeAmount { expected: 326087, provided: 0 })" }) Contract link how to reproduce the error Clone repo git clone https://github.com/compolabs/orderbook-contract git checkout -b scripts origin/scripts Create .env file in project root with private key echo "ADMIN=your_private_key" > .env Build contract cd co…

I have these errors

My current toolchain

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

installed toolchains
--------------------
beta-3-aarch64-apple-darwin
beta-4-aarch64-apple-darwin
latest-aarch64-apple-darwin (default)
latest-2023-01-18-aarch64-apple-darwin
new-creation

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

[kaya]

Let’s start by making sure you don’t have a dangling forc in your path that shadows the correct version.

You can use either:

1. which forc
2. whereis forc

This should report you a path where forc is installed. Mine returns something like:

/Users/USERNAME/.fuelup/bin/forc

If this is not pointing to forc inside fuelup that is your problem and you should remove that binary. An ususal suspect for these type of errors is installing forc via cargo, so check ~/.cargo/bin/ to see if it includes forc.

If this doesn’t help, can you share me a reproducible code that I can try on my own system to make sure your issue is due to tooling versioning.

[PaulZhemanov]

which forc                                                                                            (*match-orders+32) 11:03:24 
/Users/master/.cargo/bin/forc

@kaya