Rodrigo Posted June 16, 2023 Report Posted June 16, 2023 Sometimes my application throws the "Already logged on elsewhere" error randomly. I think it is during some re-login implementation of the lib + my setup. What has been happening is that this error is being thrown out of nowhere and I don't exactly know how to stop it from shutting down my application. I have catches everywhere and its not being catch by anything. If I put a event handler on the client.on("error") event should it stop throwing into some outer scope? Quote
Dr. McKay Posted June 16, 2023 Report Posted June 16, 2023 (edited) 9 hours ago, Rodrigo said: If I put a event handler on the client.on("error") event should it stop throwing into some outer scope? Yes. It's a universal feature of node's EventEmitter that the app will crash if an "error" event is not handled. https://nodejs.org/api/events.html#error-events Edited June 16, 2023 by Dr. McKay Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.