d0zza

Your check in getState() does not matter if it is not being run, like I said above. For web walking read through this guide by Team Cape Otherwise add !getClient().isLoggedIn() as a break condition to your conditional sleeps and wherever else you feel necessary.

Bump

Some functions like walking wait till they're finished being executed before letting the rest of your code run again, what's probably happening is that you get logged out during an operation like this and so your login handler never gets to start running again. Add break conditions to your code for when the client isn't logged in.

Bump

Bump

Bump

Sold him 50m quick and easy

Bump

Make sure you have a SOCKS5 proxy as they're the only ones that work with osbot. If you do make sure you use port 1080.

Bump

Bump

Bump

Bump

Bump

Bump

Bump

Bump

Bump

You have a null pointer exception somewhere in your code. Have the logger open before you start the script and you should be able to see which line in your code is causing the problem.

Can you post a screenshot?

Bump

Buy your own private proxy.

If the login handler fails at logging back in the script will automatically stop, sometimes it fails to stop the script which is why you see that the script is still 'running'. There are a few reasons why the login handler failed: 1. Your account is banned. 2. You lost connection/servers are down. 3. The login info is wrong. 4. Too many connections from your ip. Check the logger, it usually has the reason why it wasn't able to log you back in.

Just click widgets in the osbot debug settings and you'll be able to find the right one

Bump