400 Error, overspend account

[hmzdot]

Xxiled#0317's question

Hi all - quick one (hopefully) - any reason i'd be getting a 400, overspend error on my first use of:
acc = await stdlib.newTestAccount(startingBalance);?

[hmzdot]

This generally happens when standard library version doesn't match with the version of reach compiler contracts are compiled with

Reasoning:
When a new test account is created it is funded with a starting balance from an account called "faucet".
This account's address changes with each version so whenever there's a new update, trying to take funds from a previous one which has no tokens results with an overspend account error

Mitigation:

• Stop old instances of reach: ./reach down; ./reach docker-reset
• Update reach compiler: ./reach update
• Recompile existing contracts: ./reach compile
• Update your standard library on the frontend, if there's one: npm update @reach-sh/stdlib

[xxiled-plastic-cat]

Not that I can see, no

[jeapostrophe]

Okay, next thing to check is your Dockerfile it could be pinned to an old release

[xxiled-plastic-cat]

Dockerfile:

FROM reachsh/runner:0.1.7

# If your project needs more node dependencies:
# COPY package.json /app/package.json
# RUN npm install
# RUN npm link @reach-sh/stdlib

COPY . /app
CMD ["index"]

[jeapostrophe]

You have pinned it to 0.1.7 but are trying to use it with a 0.1.10 devnet

[xxiled-plastic-cat]

Ah, that's it! Thanks! What a stupid mistake!