Closed jet082 closed 1 year ago
threads' devs changed api, wait for author fix
First of all, thank you for taking interest in threads-api :)
It seems the login API indeed had changed a little (as can be seen in other APIs eg. for NPM) Having said that, my locally saved token in the cache is still working (feature added to our threads-api yesterday).
I will be monitoring and researching solutions for this. Thanks for notifying.
@Danie1 seems like the password is now encrypted looks like the logic is supposed to be similar to the one on instagram-private-api
so maybe this helps
https://github.com/junhoyeo/threads-api/issues/118#issuecomment-1632503110
Hey, please try v1.1.3. I changed the login logic to useinstagrapi
which seems to work for generating tokens.
I believe it will also fix this as well https://github.com/dmytrostriletskyi/threads-net/issues/46
I will close this issue to mark as complete. Please open a new issue if the problem / a new one persists from v1.1.3+.
I went ahead and looked at the data being returned by Threads. I'm getting the following JSON with a known good username/password. I replaced anything that looks like sensitive data and presented the json in pretty printed format (removing the escapes as well).
The error given by the module is:
The code generating this is simply: