FuTTiiZ Posted March 9, 2019 Report Posted March 9, 2019 (edited) [REDACTED] Edited April 10, 2020 by FuTTiiZ Quote
Dr. McKay Posted March 9, 2019 Report Posted March 9, 2019 When error is emitted, that means you're logged off. You'll need to log on again. Quote
FuTTiiZ Posted March 9, 2019 Author Report Posted March 9, 2019 (edited) [REDACTED] Edited April 10, 2020 by FuTTiiZ Quote
Dr. McKay Posted March 9, 2019 Report Posted March 9, 2019 Try using process.nextTick(() => client.logOn(logInOptions)) when error is emitted. You're going to need to generate a new 2FA code, though. Quote
FuTTiiZ Posted March 9, 2019 Author Report Posted March 9, 2019 (edited) [REDACTED] Edited April 10, 2020 by FuTTiiZ Quote
FuTTiiZ Posted March 9, 2019 Author Report Posted March 9, 2019 (edited) [REDACTED] Edited April 10, 2020 by FuTTiiZ Quote
Dr. McKay Posted March 10, 2019 Report Posted March 10, 2019 You need to log back on after error before you do anything else, or else it will crash because you're trying to do things without being logged on. A call to logOn is what needs to go inside the process.nextTick. Quote
FuTTiiZ Posted March 11, 2019 Author Report Posted March 11, 2019 (edited) [REDACTED] Edited April 10, 2020 by FuTTiiZ 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.