-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dfx deploy --network=ic
failure on a newly created project
#3870
Comments
It looks like dfx was looking for a did file from local build
If I start replica and deploy locally first, then deploy to ic works as expected. |
We're running into this when trying to deploy to mainnet too. |
Hello, but this looks like a workaround... I have the same problem but with deploying to the playground. It's looking for a did file from the local build, not from the 'playground' (or 'ic' in your case) folder where all files are. |
Apparently, the issue is fixed here: #3987 |
Man, these types of errors should be fixed and tested for. These small confusing bugs make development a lot slower and tedious. Imagine a new guy running into this when finding out about IC. They are not coming back. Anyway, I have this error when deploying to the local network using 0.24.2 and also 0.20.1 Fixed by downloading the https://github.com/keygate-vault/multisignature/actions/runs/12090187932/workflow |
I tried the following:
I expected it to successfully deploy both backend and frontend canisters.
Instead, this happened:
Meta
dfx --version
:The text was updated successfully, but these errors were encountered: