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.
1 Like
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… 
Were there any gotchas you encountered when implementing that migration from nodejs Buffer to ECMAScript ArrayBuffer?
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.
7 Likes
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?
3 Likes
I’m sorry for your loss 
3 Likes
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.
If possible, I hope you can help me analyze the possible causes. I am willing to provide assistance. Many Thanks.
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
1 Like