Instapy: Unable to get followers and following information - Unfollow task is not working

[neonvandal]

Hello everyone, how are you?
I already uploaded an issue about this but it is still happening to me, maybe someone can help me out.
When starting any unfollow task for example:
session.unfollow_users(amount=10, onlyNotFollowMe=True, sleep_delay=60)
I get the following error on the navigator screen, it seems to try to update information but it just stays this way. The log in works fine.

My current quickstart.py is looking like this (All other tasks seem to be working fine, but I just want to try the unfollow one since is not working for me anymore)

This is my current Pull status, I got all new modifications:

This is the console Error data:

Please, if someone can help me out I would really appreciate it.

Best!

[redsector72]

You are missing the last part of the quickstart.py file.
these 2 lines.

finally:
    session.end()

[neonvandal]

The quickstart.py file si complete, I just added my configuration part for more information

[neonvandal]

Maybe @uluQulu knows about this? :)

[uluQulu]

hi @neonvandal,
onlyNotFollowMe method of unfollow_users feature uses graphql queries to get data. But if you use other method- onlyInstaPyFollowed, it will not request that screen, instead will get data from a local CSV file (username_followedPool.csv).
Please, have a read https://github.com/timgrossmann/InstaPy/issues/2010#issuecomment-388662620.
If you still have a problem, ask again, Hopefully, I will help.

[neonvandal]

Thank you so much! @uluQulu
I will try to complete this task and see if it is working correctly.
One quick question : It is possible that staying in that query state for long periods will result on any type of ban or something? Is there a safety check ?
Cheers!

[uluQulu]

My pleasures @neonvandal,
To be honest, I think querying too much (_like, getting the list of hundred thousands of users_) in short periods of time would bring unwanted results.
Also staying in the same page too long does not matter.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this problem still occurs, please open a new issue