Besufekad Tamiru
Besufekad Tamiru
I have faced this bug while trying implement validation schema with yup. Changing numeric keys with string fixed the problem. Any Workaround?
It's properly working for me. The only difference is I don't use window checker to render the component. and Also I've attached onReady event handler that plays the video.
Inside RootStoreProvider.tsx file initializeStore function [the code that is responsible for hydration] instead of only using if(intialData) I replaced it with if(initialData && store===null). However we still need to hydrate...
> @Besuf Would you like to create a pull request? That'd be great thanks
Is there any updates on this? I'm having the same problem with Next 13.4.5. After some debugging, I discovered that the error is thrown when the rollbar instance is created.
Okay, I have resolved it. I forgot to use the 'use client' directive. So any component that uses a rollbar instance should be marked with `use client` directive in order...
Yes, currently, I don't report errors on the server component. According to the Next13 app router documentation, any server errors are serialized and sent to the nearest error.js component (the...
That's an excellent point. I haven't come up with a solution for that, at least not from the Next.js error handling perspective. I'm not sure if it's possible to make...
@Musashi-Sakamoto Which version of Nextjs and Rollbar did it work with?
The same issue is happening in Fedora38. Any updates?