# Fail to verify certificate in development update calls **URL:** \ **Category:** Developers\ **Created:** [May 20, 2021, 3:26pm UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078 "2021-05-20T15:26:08Z")\ **Posts on this page:** 9\ **Page:** 2
**Author:** ![anon74414410](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@anon74414410](https://forum.dfinity.org/u/anon74414410)\ **Post date:** [November 22, 2021, 4:46pm UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/21 "2021-11-22T16:46:03Z")
This is the first report I’ve heard of this. Feel free to open up an issue with steps to reproduce, and I’ll look into it. ---
**Author:** ![jzxchiang](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jzxchiang/32/2592_2.png) [@jzxchiang](https://forum.dfinity.org/u/jzxchiang)\ **Post date:** [November 23, 2021, 6:50am UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/22 "2021-11-23T06:50:52Z")
I can’t reproduce it in web (using the hello Quick Start project)… but I can reproduce it in React Native. No clue what’s going on. Might need to stick with `Buffer` in mobile… 🤦‍♂️ ---
**Author:** ![jzxchiang](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jzxchiang/32/2592_2.png) [@jzxchiang](https://forum.dfinity.org/u/jzxchiang)\ **Post date:** [November 23, 2021, 7:07am UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/23 "2021-11-23T07:07:13Z")
Were there any gotchas you encountered when implementing that [migration](https://github.com/dfinity/agent-js/commit/2fe3dd99cddfcf45c6d9d5b7a199a86285ce9740) from nodejs `Buffer` to ECMAScript `ArrayBuffer`? ---
**Author:** ![jzxchiang](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jzxchiang/32/2592_2.png) [@jzxchiang](https://forum.dfinity.org/u/jzxchiang)\ **Post date:** [November 23, 2021, 7:47pm UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/24 "2021-11-23T19:47:46Z")
I’m ashamed to report that the issue was because I forgot to call `agent.fetchRootKey` in a particular location (after signing in). I had only called it in the constructor, but I should’ve called it in both. I am so dumb. This mistake cost me 16 hours of work. Sorry for the trouble. ---
**Author:** ![lastmjs](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lastmjs/32/3406_2.png) [@lastmjs](https://forum.dfinity.org/u/lastmjs)\ **Post date:** [November 23, 2021, 8:04pm UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/25 "2021-11-23T20:04:38Z")
This fetchRootKey requirement seems to be confusing a lot of people and causing headaches, myself included. Is there some way to abstract it away so that we never have to deal with it again? ---
**Author:** ![lastmjs](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lastmjs/32/3406_2.png) [@lastmjs](https://forum.dfinity.org/u/lastmjs)\ **Post date:** [November 23, 2021, 8:05pm UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/26 "2021-11-23T20:05:01Z")
I’m sorry for your loss 🙂 ---
**Author:** ![roy4roll](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/roy4roll/32/4893_2.png) [@roy4roll](https://forum.dfinity.org/u/roy4roll)\ **Post date:** [March 25, 2022, 7:36am UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/27 "2022-03-25T07:36:26Z")
I guess that doesn’t always seem to work out. In our project, we’ll be running integration tests in a Nodejs way. And these integration tests always come up with errors by accident. But after a retry it might work. For example, here is a recent log of a failure. > **[Update reserved list · IC-Naming/icnaming@cdad0a3](https://github.com/IC-Naming/icnaming/runs/5687957481?check_suite_focus=true)** > > Contribute to IC-Naming/icnaming development by creating an account on GitHub. If possible, I hope you can help me analyze the possible causes. I am willing to provide assistance. Many Thanks. ---
**Author:** ![anon74414410](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@anon74414410](https://forum.dfinity.org/u/anon74414410)\ **Post date:** [March 25, 2022, 8:45pm UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/28 "2022-03-25T20:45:10Z")
There’s only so much I can do, when environment-specific implementations are necessary. The current abstraction of the codegen + webpack config is better than it was, but we can probably do better. I’m open to changing the `dfx generate` `index.js` template, or adding more configuration to it, in order to generate `createActor` abstractions that people are more able to use ---
**Author:** ![0xlup3x](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/0xlup3x/32/5816_2.png) [@0xlup3x](https://forum.dfinity.org/u/0xlup3x)\ **Post date:** [June 4, 2022, 1:46am UTC](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078/29 "2022-06-04T01:46:15Z")
> [@skilesare](#): > > Where should we put this call if we are running the local identity service? I am facing this while using candid ui. Any fixes? [Previous page](https://forum.dfinity.org/t/fail-to-verify-certificate-in-development-update-calls/4078.md?page=1)