-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnhandledPromiseRejectionWarning: Conflict: Store already exists #540
Comments
what is the error you see in the browser? Does it occur after you sign in, or only if you try to sign up with a username that already exists? Make sure you have the latest version of For the Server error ( |
I have @hoodie/client version 10.1.0. I downloaded all hours before reporting. I didn't try to sign-in. Just sign-up then I noticed the error and tried to know when it happens. It doesn't throw any error on the client. It registers successfully. I see the error on the server after a successful account creation
|
there is no version 10.1.0 of |
I meant version 10.1.0 of this command didn't work Running
|
okay but you have
and
|
When I start the hoodie server and my React client app, I call the
account.signUp
and everything works fine. If the user exists, it shows an error in the client. But then if I refresh the page (for now I just have a single page for sign-up and within it I initialise @hoodie-client) or I restart the client dev server, and then try making similar calls I get the following warning in the consolenode:16033) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Conflict: Store already exists
If I add
process.on('unhandledRejection', (error) => console.log(error.stack));
to my code, it shows thisBut it still creates the User Account.
I tried starting the server, then the client. I opened it in two separate browser and made the same call and got no such warning on the server. But then if I refresh the page or restart the client dev server, the error pops up
The text was updated successfully, but these errors were encountered: