Closed jonap339 closed 4 years ago
@jonap339 well I can do a fix to prevent the crash when username cannot be parsed. But without a username --unfollow-non-followers
won't work properly and session data won't be saved too. Anyway it's better than the crash I suppose.
But do you have any idea why it cannot be parsed sometimes? That's strange.
I don't know why it happens, because it cannot retrieve the username, what occurs to me is that the script can be restarted, since at this point it just cuts and does not start again. Regarding what you do, retrieve the username to do some validation?
Hi @alexal1 and @jonap339.
@alexal1, the bug that is reporting @jonap339 is showing up continuously and when you do the press profile action the bot is frozen.
It's already getting annoying those errors and I've noticed that by canceling the execution with the ctrl+c command it seems to be doing something of persistence that it can't do.
Log Error
-------- START: 2020-08-14 17:46:58.676818 --------
[08/14 17:46:58] Open Instagram app
[08/14 17:46:59] Sleep for 2 seconds
[08/14 17:47:01] Press profile
Traceback (most recent call last):
File "C:\Users\Alejo\AppData\Local\Programs\Python\Python38-32\lib\site-packages\urllib3\connectionpool.py", line 426, in _make_request
six.raise_from(e, None)
File "
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "insomniac.py", line 373, in
C:\Users\Alejo\bot\Insomniac>
today I got also this error with Failed to get username:
any clue?
seems like is still getting an error:
I´m, still facing problems showing an error with no user found Crash-2020-10-03-17-47-01.zip
Hello, This also occurs to me, I think this is due to the new version of the Instagram app where the bottom layer displays the "Reels" button for the video.
Hi good day. I believe the post since we are having this problem and it is a real headache. This happens randomly, sometimes it appears and sometimes it doesn't. It is corrected by restarting the script manually. The problem is that when automating it, when it throws this error, it is not recovered and therefore the session is dead. Any information you need, I am at your disposal! Regards