New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instagram changed its inner data structure #145
Comments
+1 |
Do you think fix this or it is normal ? |
Instagram might have changed the structure of its data. I think Instagram-Scraper had a similar Problem: |
So, is anyone going to fix it here, or I have to do it by myself? :) |
if you fix it, can you share it ? :) |
No luck with this yet. |
Only he does not look active anymore. |
My studies are calling, so I don't have much time to invest in this. |
Hey, I've had a look at the new json structure, and as @althonos says it's different from what instaLooter expects to find, hence why there is an internal KeyError when the response data gets processed for the firt time in From analyzing the json reponse, all the information that may be wanted is in there: image src url, metadata etc... This is type of code that's needed to get what I think should be all the media info that instaLooter expects ( this will just print the response contents of all posts loaded in the first response): |
I've got a working-ish fix on the
I still want to check the code in greater detail before pushing a release, but at least it downloads pics as intended for both users and hashtags. |
@althonos Thanks for the quick fix! Edit: Lines 339 and 340 have a pprint call: |
@AbysmalBiscuit : fixed, thanks. |
another issue could be related, |
Using timeframes still doesn't work - had to change line 416 in core.py from "for media in page[media]['edges']:" to "for media in page[medias]['edges']:" |
I pulled the dev branch and the could not find page of user is still showing ? should i be doing something else ? |
@Bigben83 : could you give me some parameters so that I can reproduce this ? It works just fine with a public user on my machine. |
@althonos this is what i have been using |
@Bigben83 @rajnishcseku @JonasGrobe @oferchen @AbysmalBiscuit @jnskw @lynxrv21 @bilyboy785 : If you want to test the new version, you can pull from the The codebase is brand new, but the CLI should be very familiar, and most problems should be fixed. Note that I didn't test the login at all since I have no IG account and I don't know if the login procedure used before still works ! I'll release to PyPI once I've got the documentation updated and the API stabilised. In the meantime:
Oh, and by the way, you cannot directly download a profile without using the |
Hi, I followed following steps:
Output:
**2. pip install instaLooter Output:**
**3. pip install --user -U https://github.com/althonos/InstaLooter/archive/dev.zip Output:**
**4. opened cmd in windows system and ran this command: instaLooter inspirational.theory Output:**
I don't know what I am doing wrong. Can you please tell me which step I need to rectify? |
@rajnishcseku try to skip step 2 |
I did similar to @rajnishcseku but I did skip step 2. (So just uninstall, and then the install of the dev.zip) |
@djvanguard pip install setuptools --upgrade, then try again |
@JonasGrobe I ran the command given by you also uninstalled the instaLooter (i.e. skipping step 2) Now when I try to run command "instaLooter inspirational.theory" output comes: c:>instaLooter inspirational.theory Do I need to set some some kind of environment variable in my laptop or is there any other problem? |
@rajnishcseku: and on |
@althonos while getting a bit disappointing result, I never user --time-parameter in original command line and also login doesn't work |
@althonos I ran the command Output: C:\Users\rajnish.rana>python -m instalooter inspirational.theory C:\Users\rajnish.rana>python -m instaLooter inspirational.theory |
@rajnishcseku it looks like the module directory on windows is not instaLooter |
An alpha release of #150 was opened to fix the non-working login procedure. |
Getting the same error for any username I try.
The text was updated successfully, but these errors were encountered: