Upgrade to dfx 0.18.0 requires assetstorage.did

[jamesbeadle]

I’ve been updating my app to use dfx 0.18.0, when building the app I get the following error:

Candid file: /home/james/OpenFPL/.dfx/local/canisters/OpenFPL_frontend/assetstorage.did doesn’t exist.

[jamesbeadle]

Ok so I got this working by manually creating the .dfx/local folder and including the assetstorage.did file which I got from @borovan (thanks).

A copy of that file can be found here:

jamesbeadle/OpenFPL/blob/master/candid/assetstorage.did

[theoman42]

Did this ever resolve itself later? I am suddenly running into this error now, and can’t track done what caused it. Did you ever figure it out? Or are you still doing it manually. I am using dfx 0.26.0.

[jamesbeadle]

I haven’t had this error in a little bit. But when I do I just make the local folder in .dfx

[theoman42]

If I do dfx build --check, my frontend .did gets generated fine.

@Severin Do you know why this occurs?

@Severin

The issue with dfx generate (that’s what you’re running into) is already fixed on master. Should be in the next release. As a workaround you can try dfx build --check before dfx build --ic. As a last resort you can also try putting the did file there manually

You had mentioned here that this will be fixed, not sure if this is the same issue.

[Severin]

I have some suspicions, but would have to debug for a while before I can be sure.

The issue you link has the same symptom, but a different cause - the linked one concerns remote canisters and a frontend .did is not a remote canister (unless you’re doing something unusual), therefore I’m not surprised the fix (released in 0.25.1) didn’t help your case.

Here’s a few questions that may help tracking it down:

• What does dfx.json look like for the affected canister?
• What commands does the issue happen with? dfx build obviously, but maybe also dfx deploy?
• Only when you use --ic or also without?
• Does it only happen when you first delete .dfx or does it happen repeatedly?

[theoman42]

Hey, so I think I figured it out my issue specifically, but hope it helps diagnose future instances. This was all occurring locally so no --ic flag.

Ultimately, my mistake was that I was using --specified-id flag at dfx deploy , I was getting unusual errors stating that this id has already been used. Anyways, using --specified-id flag at dfx canister create seemed to fix my issue. There were potentially a few other snags, but I was moving in and out quickly, so it was hard to track what was triggering what warning/error.