JSONDecodeErrors about linkedin2username HOT 6 CLOSED

Hi @jkuensting-r7 - thanks for letting me know!

I recently switched from scraping text and using regexes (messy, prone to issues) to properly parsing the JSON from the mobile app API.

I can't replicate your error right now, but I'm sure it's related to the change. If you need a quick fix, you can download the previous version from the releases section.

I'd definitely like to fix this error, though. It looks to me like it is starting to work for you and then failing at a later loop (16 in this case).

Let me try some more testing later today or this week and I'll report back here.

from linkedin2username.

Ah! That makes sense. I may do just that; I've run into this same issue on a few engagements now. Might be some kind of edge case, like the API is returning null results in some cases or something like that. It seems like the API is just giving some response that your changes aren't prepared for.

Unfortunately I can't show much more of my command without showing my client, but if you need more testing on my end let me know.

Thanks for the prompt response! Love this tool; very useful for target recon.

from linkedin2username.

Thanks. In the meantime, you can use --proxy "http://localhost:8080" to proxy the results through Burp/etc. The last HTTP request that is executed when the script fails probably has some hints to the issue.

My script is attempting to to result_json = json.loads(result) with the text for the response body. Probably what is happening is that it isn't JSON at all, and is some unexpected error or something.

If you could provide context to that, it would be useful. Things like the following from the last response that triggers the error:

• HTTP response code
• Any part of the body that you are willing to share

Also, please test with the latest version as I fixed some other bugs I found while trying to reproduce your issue.

from linkedin2username.

FYI, I still cannot reproduce this. LinkedIn is whacky, and sometimes feeds different responses to different accounts for all kinds of reasons.

Let me know if you can provide the details above. I also just pushed another new version, which should assist in troubleshooting any JSON decode errors by printing some details to the console. If you pull the newest code from master it should work for you.

Also, if anyone else sees this issue and is having the same problem please comment so I know it is affecting multiple users.

Thanks!

from linkedin2username.

from linkedin2username.

Haven't hear back, hope you worked this out!

from linkedin2username.