Challenge required?

[ghost]

This is a new one because usually if you see this you sign in that account on the app to fix it but there is nothing. I have tried deleting cache/cookies for account to generate new ones and it still happens even if downloading just 1 live it'll stop randomly and merge the files.

[ghost]

To reproduce this, do pyinstalive -df then try it one more time (any time between the first command) it will give a long error and say challenge required. This even happens on fresh accounts.

Traceback (most recent call last): File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\site-packages\instagram_private_api\client.py", line 523, in _call_api response = self.opener.open(req, timeout=self.timeout) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\urllib\request.py", line 531, in open response = meth(req, response) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\urllib\request.py", line 640, in http_response response = self.parent.error( File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\urllib\request.py", line 569, in error return self._call_chain(args) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\urllib\request.py", line 502, in _call_chain result = func(args) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\urllib\request.py", line 649, in http_error_default raise HTTPError(req.full_url, code, msg, hdrs, fp) urllib.error.HTTPError: HTTP Error 400: Bad Request

During handling of the above exception, another exception occurred: Traceback (most recent call last): File "C:\Users\USERNAMEHERE\AppData\Local\Programs\Python\Python38\Scripts\pyinstalive-script.py", line 33, in sys.exit(load_entry_point('pyinstalive==3.2.4', 'console_scripts', 'pyinstalive')()) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\site-packages\pyinstalive\startup.py", line 332, in run downloader.start() File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\site-packages\pyinstalive\downloader.py", line 36, in start dlfuncs.download_livestream() File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\site-packages\pyinstalive\dlfuncs.py", line 232, in download_livestream print_status(False) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\site-packages\pyinstalive\dlfuncs.py", line 185, in print_status heartbeat_info = pil.ig_api.broadcast_heartbeat_and_viewercount(pil.livestream_obj.get('id')) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\site-packages\instagram_private_api\endpoints\live.py", line 75, in broadcast_heartbeat_and_viewercount return self._call_api(endpoint, params=params, unsigned=True) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\site-packages\instagram_private_api\client.py", line 527, in _call_api ErrorHandler.process(e, error_response) File "c:\users\USERNAMEHERE\appdata\local\programs\python\python38\lib\site-packages\instagram_private_api\errors.py", line 123, in process raise error_info['error']( instagram_private_api.errors.ClientCheckpointRequiredError: checkpoint_required

[dvingerh]

try testing branch it uses web api instead and its pretty much a rewrite of the entire script that i never finished https://github.com/dvingerh/PyInstaLive/tree/testing

the config file you use will no longer be valid you have to update the names of most values as stated under Usage in the readme

[ghost]

try testing branch it uses web api instead and its pretty much a rewrite of the entire script that i never finished https://github.com/dvingerh/PyInstaLive/tree/testing

This is what I originally had, only went to master release after this issue happened which also has the same thing.

Trying again and will report back when it happens again. Only made the issue because usually it's just account limit thing from instagram though this was also happening on a brand new account

[ghost]

Yeah my mistake seems like another instagram thing which is cringe. If anyone comes across issue wait a day or two for that account before idling with it again.