You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
I've asked for help in the Truffle Gitter before filing this issue.
Issue
My migration deploys a few contracts in a row. The JSON files get created with ABI and bytecode, but only the first contract deployed gets the deployed address saved under the network in the artefacts.
@Pedro-vk Thanks for opening - this is a duplicate of #501.
The way async/await integrates with the migrations feature is confusing for a lot of users. truffle-migrate was written before await became common and it stages deployments as 'thennables' rather than executing them as true promises. See this comment for advice about how to resolve.
Issue
My migration deploys a few contracts in a row. The JSON files get created with ABI and bytecode, but only the first contract deployed gets the deployed address saved under the network in the artefacts.
Steps to Reproduce
Run a migration of that:
Expected Behavior
FirstContract
andSecondContract
must have the network parameter written, with the address where have been deployed.Actual Results
Check the result of the
FirstContract
andSecondContract
, onlyFirstContract
have written the network parameter.Environment
truffle version
): 4.1.5 and 4.1.3node --version
): 9.5.0npm --version
): 5.8.0The text was updated successfully, but these errors were encountered: