Avnsx / fansly-downloader

Easy to use fansly.com content downloading tool. Written in python, but ships as a standalone Executable App for Windows too. Enjoy your Fansly content offline anytime, anywhere in the highest possible content resolution! Fully customizable to download in bulk or single: photos, videos & audio from timeline, messages, collection & specific posts 👍
https://fansly.com/
GNU General Public License v3.0
1.27k stars 63 forks source link

API Returned unauthorized #39

Closed ForcedToRock closed 2 years ago

ForcedToRock commented 2 years ago

This started happening after updating to 0.3.4. The error message would show "Used authorization token" but it's completely different from the actual cookie. Pretty much like this issue. https://github.com/Avnsx/fansly/issues/30

Avnsx commented 2 years ago
  1. What browser and Operating System are you using?
  2. Does your fansly account have two factor authentication enabled?
  3. Have you just recently tried getting the auth token with Automatic Configurator?
  4. If you have tried getting it with Automatic Configurator does your auth token string end with fNs?
  5. Are you sure you've tried using fansly scraper & automatic configurator both on version 0.3.4? (right click any .exe and go to the details tab to find out)
  6. Does the issue also happen when you manually add the auth token with the Get Started Tutorial?
ForcedToRock commented 2 years ago
  1. Firefox, Windows 10
  2. No
  3. Yes, it spits out some cookie that starts with "M4" but when I got the cookie manually, it's something else.
  4. Yes
  5. Yes
  6. It happens on both occasions, after using the automatic configurator, and then after manually adding the token.
Avnsx commented 2 years ago

Okay I figured out why this happens will push a fix soon, also I developed the recent update over a little time span and I forgot I did not properly finished implementing stuff that I thought I had implemented properly, which resulted in all these issues

Avnsx commented 2 years ago

@forcedtorock one more question, was automatic configurator even able to get the correct token from firefox in version 0.3.3 (the version before)? I am wondering if I should improve automatic configurators support for firefox or if it was getting the job done already good before

ForcedToRock commented 2 years ago

No, it spit out a token that ends in ZGE, while manually getting the token reveals one that ends in something different. I couldn't run the scraper fully anyway because it keeps prompting for an update, even though 0.3.4 got removed. I would try to "update" but the scraper would close by itself afterward.

Avnsx commented 2 years ago

Have you tried out automatic configurator on version 0.3.5 now? Is it able to geta correct auth token for you? I just recently released it as executable @ForcedToRock

ForcedToRock commented 2 years ago

It didn't get the right token.