Error Response verification failed sw.ts:50

I am getting this error on my deployed projects with react in the front end canister when try to navigate to other pages I am getting the Internet computer error page saying
" Page failed to load.

Response verification failed".

And this error message:

Timestamp: Thu, 01 Jun 2023 20:01:50 GMT

Request: {
  "method": "GET",
  "url": "https://canister_id/account",
  "origin": "https://canister_id"
}

Response: {
  "status": 500,
  "statusText": "Response verification failed",
  "body": "Response verification failed"
}

Only the main page is working, but I am seeing also seeing these error messages in the browser console:

Error with Permissions-Policy header: Unrecognized feature: 'ambient-light-sensor'.
Error with Permissions-Policy header: Unrecognized feature: 'battery'.
Error with Permissions-Policy header: Unrecognized feature: 'document-domain'.
Error with Permissions-Policy header: Unrecognized feature: 'execution-while-not-rendered'.
Error with Permissions-Policy header: Unrecognized feature: 'execution-while-out-of-viewport'.
Error with Permissions-Policy header: Unrecognized feature: 'navigation-override'.
Error with Permissions-Policy header: Unrecognized feature: 'web-share'.
Error with Permissions-Policy header: Unrecognized feature: 'speaker-selection'.
Error with Permissions-Policy header: Unrecognized feature: 'conversion-measurement'.
Error with Permissions-Policy header: Unrecognized feature: 'focus-without-user-activation'.
Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
Error with Permissions-Policy header: Unrecognized feature: 'sync-script'.
Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'trust-token-redemption'.

And then when I navigate to a certain page I am getting another error in the console when the whole page actually fails.

What could be problem? I wasnt having it before, it’s like it just started

2 Likes

I keep getting the same thing. The app is using sveltekit

1 Like

I forwarded your inputs to the team.

2 Likes

Yeah same thing, I wonder what that is.

@iamenochchirima @cyberowl are you reporting:

  1. an unexpected error as it used to work but since few days or hours it does not work anymore
  2. you deployed something new and you would like to understand why you get the issue

I can reproduce the same “error” with Juno but, in that case, it’s a valid and expected result. That’s why I would like to understand the context.

Same thing with IC front end assets url: Internet Computer Loading

Yeah so I have deployed it recently. I haven’t change any code out of the ordinary.

Also it works locally as you can see by the image above. Not sure what is causing it. It was working a few hours ago, around 10pm PST. I will keep digging but seems like some update might have gone out?

Thanks for the feedback @cyberowl.

In you bundle (npm run build outcome), you got a cyberowl.html or /cyberowl/index.html or your app isn’t pre-rendered and https://..../cyberowl is a route of the app?

Not sure it is related, just for my understanding as I can reproduce with Juno https://juno.build/docs but, in my case, it’s kind of expected.

This the build.

This is working locally.

I think its an internet computer problem and not our projects, because it just started from nowhere when everything was working fine

1 Like

Same issue in private tor window. So prob unrelated to anything stored in browser mem.

    • An unexpected error as it used to work but since a few hours it does not work anymore

Thanks for your answers, details and screenshots :+1:.

I forwarded your inputs. Team is - we are - currently analyzing the issue and discussing it.

2 Likes

Let me know if you need any other info. I can screen record and even go over code in vid call if you want. I will keep digging and see if I find anything.

1 Like

Hello, thanks for sharing this input with us! Could you both share what version of DFX you used to deploy your project?

1 Like

Seems to be working now.

Not sure what the issue was:

I also did a
dfx deploy --network ic --wallet l2eht-xxx-cai dsign_assets --mode=reinstall

I also reinstalled all node deps. So not sure what a fix would have been from my end.

The boundary node release has been rolled back, that’s why it’s working now :slight_smile: I’m looking to find the source of the issue so that we can release again.

2 Likes

I am using dfx version 0.14.0

EDIT: nevermind, the svelte-starter in the examples repo is a reproduction

Looks like I made a mistake when implementing certification v2 in the asset canister, but I cannot reproduce it myself. Do you have some way for me to deploy a reproduction of this? You can also use DMs if you prefer to

Update: I made a mistake with certification v2. For dfx 0.14.1 (beta 1 is currently available already) this is already (accidentally) fixed. The boundary node will most likely skip over certification v2 and fall back to v1 for the 0.14.0 asset canisters in the future

3 Likes