Closed ForcedToRock closed 2 years ago
fNs
?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
@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
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.
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
It didn't get the right token.
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