Important update for DFX v0.14.0 users

TL;DR:

Upgrade any projects with asset canisters using DFX v0.14.0 to v0.14.1 and redeploy before Monday, the 26th of June.

Full post

Hello everyone, Nathan here from the Trust team :wave: I hope you are all having a great day building on the Internet Computer :woman_astronaut::man_astronaut:

I have an announcement to share with you regarding an upcoming boundary nodes deployment on Monday, the 26th of June. This deployment will introduce a change that will affect asset canisters deployed using DFX v0.14.0. This is part of our ongoing efforts to roll out response verification v2, which will help to improve the security and flexibility of canister response certification and verification.

If you have deployed your asset canister with DFX v0.13.1 or lower, then you are good to go and you don’t need to worry about anything. However, if you have deployed your asset canister with DFX v0.14.0 then I kindly request you to upgrade to DFX v0.14.1 and redeploy your asset canister as soon as you can. Otherwise, your asset canister will stop working after the deployment and the only way to fix it will be to upgrade to v0.14.1 and redeploy.

This change will not impact any canisters deployed with DFX v0.14.0 that are not asset canisters (they do not have type: “assets”), but I would still recommend upgrading at your earliest convenience since v0.14.0 is no longer supported and has been deprecated since June 6th.

DFX v0.14.0 was announced on April 27th and then removed on June 6th due to an issue that caused index.html fallbacks to not work correctly with response verification v2. Since then, it has been impossible to install DFX v0.14.0.

I’m very sorry for any inconvenience that this deployment may cause for your development :pray: Please let me know if you have any questions or concerns and I’ll be happy to assist you :rocket:

13 Likes

What’s the Wasm hash of the asset canister that’s deprecated? I’m not sure what version I used to deploy.

You can find the hash in the dfx changelog. It is e7866e1949e3688a78d8d29bd63e1c13cd6bfb8fbe29444fa606a20e0b1e33f0

3 Likes

Hey everyone, as announced, we have just completed the rollout of the boundary nodes that enables response verification v2.

2 Likes

Redeployed asset canister but still getting this err

https://www.dsign.ooo/project/7VAFT84WG459JZMR9KYJJ7PVHY?canister_id=23fub-taaaa-aaaag-abkta-cai

		"dsign_assets": {
			"dependencies": [],
			"frontend": {
				"entrypoint": "build/index.html"
			},
			"source": ["build"],
			"gzip": true,
			"optimize": "cycles",
			"type": "assets"
		},

dfx 0.14.1

Same here. Redeployed the asset canister with v0.14.1 and still getting the error. Homepage is working fine but if you try to reload any screen other than the homepage, it returns the “response verification failed” error.

Hey I’m having the same issue, navigation through my dapp works fine providing you load it from the base entry point but trying to reload assets on any page within the app fails:

Timestamp: Tue, 27 Jun 2023 16:09:25 GMT

Request: {
“method”: “GET”,
“url”: “Internet Computer Loading”,
“origin”: “https://6t32g-3yaaa-aaaao-ai56a-cai.icp0.io
}

Response: {
“status”: 500,
“statusText”: “Response verification failed”,
“body”: “Response verification failed”
}

1 Like

Sorry about the issues everyone. We’re rolling back the release now.

4 Likes

I’m now able to refresh all pages throughout my dapp, thank you for responding and resolving. Is there a date for an updated patch upcoming or should we just keep our eyes peeled for now?

We have the same issue at the moment using dfx_0.14.1 you can Internet Computer Loading has 500 error, and root is working fine.

1 Like

Update DFX and redeploy to fix it

It should work properly on 0.15.0-beta.1? Or what is a proper version to use on prod?

0.14.3 is fine to use

1 Like