vmarkis Posted May 29 Report Share Posted May 29 (edited) I'm trying to reconnect the user and I'm handling all possible errors. As you can see in the logs, the first module I wrote in the stack trace is `SteamAccountClient.login()`, which calls `client.logOn() (a method from steam-user)` This image shows the code for `SteamAccountClient.login()`. It's wrapping `client.logOn()` in a try-catch block, so no error should've be thrown. I noticed an internal use of the `logOn()` method within a timeout, but without any try-catch block. This could be why my app is crashing, even though it's shown in the stack trace. Edited May 29 by vmarkis Quote Link to comment Share on other sites More sharing options...
Dr. McKay Posted May 29 Report Share Posted May 29 The "Already attempting to log on, cannot log on again" error cannot be caught under any circumstances. If you need to, keep track in your own code if you're already attempting to log on. vmarkis 1 Quote Link to comment Share on other sites More sharing options...
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.