Fanfiction Reader app not working

[lucena3]

Fanfiction reader app still not working I hope someone fixes it soon.

[hallowknight99]

App should be now working once update become avaible on the play store

[hallowknight99]

Got update @genious7 library fails to update, but loads new stories

[canerolu2019]

Got update @genious7 library fails to update, but loads new stories

Well the app still doesnt work unfortunately. Also what's this new update you guys are talking about??

[hallowknight99]

@canerolu2019 I can read the stories like normal in version 1.60. The downloaded stories fails to download any updatds.

[hallowknight99]

63 "I just uploaded a "fix" that routes the app's requests through a hidden web browser to bypass Cloudflare's javascript check. It seems to be working for most of the app itself, although downloads are still failing with a Cloudflare 403 "forbidden" error, despite using essentially the same code to bypass the cloudflare captcha."

[genious7]

I just uploaded to beta (and I'll be deploying to existing users in general momentarily) a partial fix to the issue.

The issue that broke the app was a cloudflare captcha that FF.net added to browsers without javascript to block third party apps (like mine). I'm having the app load the web site on a "hidden" browser that can execute javascript to circumvent the issue.

It's slower than it was before, but it works for most of the app. It is unfortunately not working for downloads (no idea why). The only thing I can think of is that the "download" function uses the desktop web site (www.fanfiction.net) whilst the rest of the app uses the mobile web site "m.fanfiction.net". Maybe the "technique" to circumvent one doesn't work on the other one?

I'll try to look at the downloads issue whenever I can, although work is a bit heavy at the moment, so please keep that in mind.

[canerolu2019]

63 "I just uploaded a "fix" that routes the app's requests through a hidden web browser to bypass Cloudflare's javascript check. It seems to be working for most of the app itself, although downloads are still failing with a Cloudflare 403 "forbidden" error, despite using essentially the same code to bypass the cloudflare captcha."

Can u give me this app apk update pls

[genious7]

If you still have the app installed, you should be able to update it soon. I still haven't re-enabled the play store listing, as I'm not really looking for new users until the app is completely fixed.

If you uninstalled it and you still want the app (even though it doesn't download yet), here is a link to the apk.

[hallowknight99]

I just uploaded to beta (and I'll be deploying to existing users in general momentarily) a partial fix to the issue.

The issue that broke the app was a cloudflare captcha that FF.net added to browsers without javascript to block third party apps (like mine). I'm having the app load the web site on a "hidden" browser that can execute javascript to circumvent the issue.

It's slower than it was before, but it works for most of the app. It is unfortunately not working for downloads (no idea why). The only thing I can think of is that the "download" function uses the desktop web site (www.fanfiction.net) whilst the rest of the app uses the mobile web site "m.fanfiction.net". Maybe the "technique" to circumvent one doesn't work on the other one?

I'll try to look at the downloads issue whenever I can, although work is a bit heavy at the moment, so please keep that in mind.

How about setting the download page to the m.fanfiction.net?

[genious7]

The reason it is set that way is because, when downloading, it needs to download the desktop version to obtain the story summary. As shown in the comparison below, the desktop web page is the only one with the story summary, which is required for the menu in the "MyLibrary".

[hallowknight99]

The reason it is set that way is because, when downloading, it needs to download the desktop version to obtain the story summary. As shown in the comparison below, the desktop web page is the only one with the story summary, which is required for the menu in the "MyLibrary".

Okay. Also the add to follows and favourites isn't working when on a story

[Luminatrix-eng]

If you still have the app installed, you should be able to update it soon. I still haven't re-enabled the play store listing, as I'm not really looking for new users until the app is completely fixed.

If you uninstalled it and you still want the app (even though it doesn't download yet), here is a link to the apk.

I seem to be getting a "The Package appears to be corrupt" message when I try to install it from your dropbox https://www.dropbox.com/s/3rq2ptv0pvflr3d/fanfictionReader-release.apk?dl=0

Edit: I think it's probably because my Bluestacks is an older version and the the target SDK version is different to the current version. I'll update Bluestacks now.

Edit 2: After updating Bluestacks, I still can't seem to install the apk.

Edit 3: I also tried to install it on Anbox Application Manager with the same result "The package appears to be corrupt"

I suspect the reason this is happening is because the generated apk downgraded the targetSdkVersion in gradle app module file but I could be wrong.

[Luminatrix-eng]

I was wondering if there might be an update regarding my post above?

[mjs143]

Hi. I just noticed the app is back. I accidentally uninstalled my app and when i went to restore my backup it failed. Is it just mine or is everyone else experiencing the same problem? Thanks.

[canerolu2019]

It seems like I cannot install the apk cause it gives me error. Hey @genious7 can u pls fix this. Thank you and have a good day

[canerolu2019]

If you still have the app installed, you should be able to update it soon. I still haven't re-enabled the play store listing, as I'm not really looking for new users until the app is completely fixed. If you uninstalled it and you still want the app (even though it doesn't download yet), here is a link to the apk.

I seem to be getting a "The Package appears to be corrupt" message when I try to install it from your dropbox https://www.dropbox.com/s/3rq2ptv0pvflr3d/fanfictionReader-release.apk?dl=0

Edit: I think it's probably because my Bluestacks is an older version and the the target SDK version is different to the current version. I'll update Bluestacks now.

Edit 2: After updating Bluestacks, I still can't seem to install the apk.

Edit 3: I also tried to install it on Anbox Application Manager with the same result "The package appears to be corrupt"

I suspect the reason this is happening is because the generated apk downgraded the targetSdkVersion in gradle app module file but I could be wrong.

I am having the same problem unfortunately. The app keeps crashing whenever I install it. And idk why is this keeps happening. Also @genious7 should really fix this so I can enjoy reading stories again.

[Luminatrix-eng]

@canerolu2019 So it's not just me then. I suspect that the reason this is happening is because the generated apk downgraded the targetSdkVersion in gradle app module file...again I could be wrong.

We'll have to wait and hear back from @genious7

[genious7]

Knowing my luck, it's probably a bad DropBox upload or something equally unlikely. I'll reupload it on Friday, after I fix a small detail I missed (the view reviews and view author profile aren't working in that revision). Downloads are still pending; I'll look into that afterwards.

[canerolu2019]

Knowing my luck, it's probably a bad DropBox upload or something equally unlikely. I'll reupload it on Friday, after I fix a small detail I missed (the view reviews and view author profile aren't working in that revision). Downloads are still pending; I'll look into that afterwards.

Thx for everything dude. For trying to fix this amazing app of yours. Also it maybe a bad dropbox upload idk. It also maybe the android version I'm using its pie version maybe it is uncompatible maybe that is the case but I think that unlikely.

[Luminatrix-eng]

Knowing my luck, it's probably a bad DropBox upload or something equally unlikely. I'll reupload it on Friday, after I fix a small detail I missed (the view reviews and view author profile aren't working in that revision). Downloads are still pending; I'll look into that afterwards.

Thanks for trying to fix everything. Fingers crossed that things will work out.

[ghrrrr]

Knowing my luck, it's probably a bad DropBox upload or something equally unlikely. I'll reupload it on Friday, after I fix a small detail I missed (the view reviews and view author profile aren't working in that revision). Downloads are still pending; I'll look into that afterwards.

Did you have a chance to check the problem for transfering archives, view reviews and view author profile, app crashing while trying to browse? But most importantly did you manage to figure out the problem about stories still not downloading? This and transferring archive is the most important parts for most of us atm i think.

[Luminatrix-eng]

Knowing my luck, it's probably a bad DropBox upload or something equally unlikely. I'll reupload it on Friday, after I fix a small detail I missed (the view reviews and view author profile aren't working in that revision). Downloads are still pending; I'll look into that afterwards.

Hi there, out of curiosity, I was wondering if there are any plans for an update? I haven't been able to install the DropBox app because it still shows up as "corrupt file".

[canerolu2019]

Good news the app is working as it should but the down side is downloading or update stories, browse author and the reviews is not working. That's the only issue that has to be fixed. Other then that good job @genious7 . Keep going dude. Your doing great.

[Luminatrix-eng]

Knowing my luck, it's probably a bad DropBox upload or something equally unlikely. I'll reupload it on Friday, after I fix a small detail I missed (the view reviews and view author profile aren't working in that revision). Downloads are still pending; I'll look into that afterwards.

@genious7 I just wanted to provide more info here and hope this helps you. While I can't install the dropbox file you uploaded to my BlueStacks 4 or Anbox due to a message prompt "The package appears to be corrupt" however I can install the fanfic app on my phone just fine without Android Emulator.

But like other people here, I'm also experiencing the same issue that "Back up file not found" even though I put the .bak file in the main directory like I always do on my phone. https://github.com/genious7/FanFictionReader/issues/74#issue-839445905

Edit: To clarify, I checked the storage permissions on my phone to see if the permissions was set to 'Allow' which it is, so I'm not sure what is causing this. But someone commented a possible cause: https://github.com/genious7/FanFictionReader/issues/74#issuecomment-819109949

I also saw this article: https://www.xda-developers.com/android-11-all-files-access-permission-form/

Edit 2: I have noticed that my phone is Android 10 version.

Edit 3 (work-around): I managed to do a workaround by uninstalling the app and installing the older version 1.58b, then I restored the .bak file from memory which worked and then finally going to my playstore "Installed" apps and updating the app to 1.60. So for anyone who is having this issue, this is a potential workaround.

Unfortunately, when I tried to update my stories, it came up with "Error downloading story" "Failed to connect to server" same as what @canerolu2019 posted above.

[canerolu2019]

Ok so the latest update fixed the view reviews, browse author and download. So thx @genious7 for that. But another problem occured this time. It seems like I cant add the stories to fav or follow it says "failed to connecting to server". Also in the favourites and follows section when I touch a story it shows browse author however when I try to press browse author nothing happens. I hope this can be fixed in the future.

[Luminatrix-eng]

The latest update has definitely got it working initially and I was pretty excited to see the updates start coming through but it seemed to hang at 1.56% with only 11 stories out of the 642 stories I have updated so far. I had to close the app and restart the update stories again, which got past the 1.56% and all the way to 100% so I didn't have to close the app again. Whatever that initial hiccup that froze the updates, I can't be certain but it can be fixed by shutting the app and restarting the update again.

Thank you so much @genious7 ... you are a legend!

I'm not even bothered about the download speeds being slower.

On the hilarious side of things, since I haven't updated my stories since December last year, you can see the ridiculous number of stories updated lmao.

[ghrrrr]

I am still having problems with download after the app checks 25 to 40 stories it just stops like it didnt start at all. I managed to update a few other fics as well by manually entering the story and updating it but again if the chapter number is higher like more than 20 this method also doesnt work. I think this is due to the speed of the app requesting information from the site. If it is too fast or too much the site stops responding. In android 7.0 the push notification turns to "failed to connect to server" error. In 10.0 like i said it just dissapears like i never started to process. I too dont care how slow it is. I am hoping for a solution to this. As always great work @genious7 thank you for all your efforts. Hoping for a speedy solution to this final hurdle, fingers crossed. Edit: downloading completely new stories have the same problem if it has too many chapters it doesnt work.

[Luminatrix-eng]

I am still having problems with download after the app checks 25 to 40 stories it just stops like it didnt start at all. I managed to update a few other fics as well by manually entering the story and updating it but again if the chapter number is higher like more than 20 this method also doesnt work. I think this is due to the speed of the app requesting information from the site. If it is too fast or too much the site stops responding. In android 7.0 the push notification turns to "failed to connect to server" error. In 10.0 like i said it just dissapears like i never started to process. I too dont care how slow it is. I am hoping for a solution to this. As always great work @genious7 thank you for all your efforts. Hoping for a speedy solution to this final hurdle, fingers crossed. Edit: downloading completely new stories have the same problem if it has too many chapters it doesnt work.

Yeah I encountered the same problem as you can see above. The work around for this if the updates freeze up is to shut down the app and open it again and start updating again. At least for me, the stories were 100% updated on the second try. But I suspect you're right that it might be something to do with the request speed.

[ghrrrr]

I am still having problems with download after the app checks 25 to 40 stories it just stops like it didnt start at all. I managed to update a few other fics as well by manually entering the story and updating it but again if the chapter number is higher like more than 20 this method also doesnt work. I think this is due to the speed of the app requesting information from the site. If it is too fast or too much the site stops responding. In android 7.0 the push notification turns to "failed to connect to server" error. In 10.0 like i said it just dissapears like i never started to process. I too dont care how slow it is. I am hoping for a solution to this. As always great work @genious7 thank you for all your efforts. Hoping for a speedy solution to this final hurdle, fingers crossed. Edit: downloading completely new stories have the same problem if it has too many chapters it doesnt work.

Yeah I encountered the same problem as you can see above. The work around for this if the updates freeze up is to shut down the app and open it again and start updating again. At least for me, the stories were 100% updated on the second try. But I suspect you're right that it might be something to do with the request speed.

Yeah i saw that but didnt work for me in either of my devices. Even after a hard reset, it never went past 50/2800+ stories and usually stops long before it reaches 50 like at 20+. I thought it could have something to do with the number of stories it is trying to update so i filtered somethings out but even when the number of stories being updates is less than 500 it stops between 20-40+. I am just waiting to hear @genious7 take on that if i am missing something.

[Luminatrix-eng]

@ghrrrr I see. Out of curiosity, the last story (50 out of 2800)...how many chapters was that story? I'm wondering if there's a correlation if the amount of chapters in a story trigger a freeze up or hiccup so to speak....Or if it's another issue entirely.

[ghrrrr]

@ghrrrr I see. Out of curiosity, the last story (50 out of 2800)...how many chapters was that story? I'm wondering if there's a correlation if the amount of chapters in a story trigger a freeze up or hiccup so to speak....Or if it's another issue entirely.

I see where you are going with this but i never checked since it doesnt always stops at the same story. But i checked some stories individually to update manually and i know if a story has more than a few chapters to update since the last time it is a coin toss between it working or not and if the number of new chapters to add is more than 10 it almost always fails

[Luminatrix-eng]

Hmmm well aside from that, I can't think of what is causing the issue. I'm still pretty much a novice at android app coding so...

At least we can eliminate one probable cause that it's not an issue with amount of chapters or lengths to update. The issue seems to be something else. Or is it? Hopefully there's a solution for you mate.

[ghrrrr]

Don't be so quick to eleminate that since if it is as we theorized about the speed of requesting information it could also be affected by a slower or faster connection which would change where it stopped. Or it could be there is some randomness factor involved like with captcha appearing like "between 5 and 10 chapters" Actually if it is about the speed of new requests the changing numbers COULD mean with a little tweak by making it slower by a tiny bit it can be circumvented. Edit: i have an even older and fairly slow device i will try to find it whereever i stashed it and try it on that maybe it could make a difference i will let you know only if it works.

[darthShadow]

There are no known heuristics to figure out when or how a cloudflare captcha can appear, otherwise, there would be tools to bypass it and everyone would be using them.

[hallowknight99]

I am still having problems with download after the app checks 25 to 40 stories it just stops like it didnt start at all. I managed to update a few other fics as well by manually entering the story and updating it but again if the chapter number is higher like more than 20 this method also doesnt work. I think this is due to the speed of the app requesting information from the site. If it is too fast or too much the site stops responding. In android 7.0 the push notification turns to "failed to connect to server" error. In 10.0 like i said it just dissapears like i never started to process. I too dont care how slow it is. I am hoping for a solution to this. As always great work @genious7 thank you for all your efforts. Hoping for a speedy solution to this final hurdle, fingers crossed. Edit: downloading completely new stories have the same problem if it has too many chapters it doesnt work.

Yeah I encountered the same problem as you can see above. The work around for this if the updates freeze up is to shut down the app and open it again and start updating again. At least for me, the stories were 100% updated on the second try. But I suspect you're right that it might be something to do with the request speed.

Yeah i saw that but didnt work for me in either of my devices. Even after a hard reset, it never went past 50/2800+ stories and usually stops long before it reaches 50 like at 20+. I thought it could have something to do with the number of stories it is trying to update so i filtered somethings out but even when the number of stories being updates is less than 500 it stops between 20-40+. I am just waiting to hear @genious7 take on that if i am missing something.

It took me like 30 minutes to check all my 1983 stories that I downloaded (about 300 updated) when it didn't lose connection sometimes after the 1000+. just wish it could check for updates faster, but at least it is working.

[ghrrrr]

Am i the only one who it doesnt work for on all 3 of my devices?

[hallowknight99]

@genious7 Remember to update the app store with the new faster download option that you added 4 days ago as the version hasn't yet changed.

[hallowknight99]

Am i the only one who it doesnt work for on all 3 of my devices?

It could be something to do with captcha where it gets stuck or finds a story that is no longer on site.

[4LaERz0GWNnuZqmnH]

Would one of you be willing to upload the updated apk to an external site? Aurora Store fails to load the app's page

[ErinArt]

I'm not someone who knows code, but I love this app, so here I am. :) Was really surprised when I could download the updated chapters again last night. As I have a lot of them I left it running overnight only to come back this morning to see that only a handful of stories were updated by the app. It then said 'Error downloading story - Failed to connect to server' when I tried again. Now if I go manually to every story and try updating it like that, one story at a time, it really is hit or miss (mostly miss) if it will work or not. I can give you a few titles that were updated and some that show the error if you want? So you developers can see if there is something connecting the stories that don't update? I know it's not about how many chapters the story has or doesn't have or the size of them, neither does it seem to be only stories that were deleted by the writers, nor do I think it's because of changes of the username, and restarting the app doesn't work. Thank you for your time and effort btw! It really is appreciated!

[genious7]

@ErinArt You could send me the name of a story just to double check, although I doubt the issue is actually related to the stories at all. The FanFiction.net added the Cloudflare system to discourage downloading stories. Whenever Cloudflare thinks a download is occuring, it blocks the request.

I do think there is some sort of criteria regarding when Cloudflare blocks a page and when it doesn't, as some users report that it's working perfectly, and ... well... some don't.

[ErinArt]

@genious7 ah, okay. I understand it a little better now! I think.. ^^' I tried downloading one of those stories again just now, after not downloading updates for two days and it's now downloaded so you are totally correct. Which means giving you that list now would be a waste of time. But thank you for taking the time to double check! :) I'll try massdownloading the updates one more time, see if it gets any further now ^^' Though it does seem a bit strange to me that some users have issues with it and some don't. Wonder why that is. Anyways, thank again! Hope you'll find the problem/answer soon! :D edit: nope xD did not work, very quickly either. though one by one is working at the moment

[Luminatrix-eng]

@genious7 I just updated my stories again today. I am happy to confirm that I had no issues updating my stories on Bluestacks. Although one thing to note is that I noticed after 33% of downloads, the percentage started ramping up in speed and in less than a minute the rest of the updates was done.

It was strange which leads me to think that there might be more stories after the 33% progress that haven't been updated but ignored. I got a message saying "Error downloading story. Please contact developer" so that seems to support the idea that some stories probably haven't been updated.

[ghrrrr]

@ErinArt You could send me the name of a story just to double check, although I doubt the issue is actually related to the stories at all. The FanFiction.net added the Cloudflare system to discourage downloading stories. Whenever Cloudflare thinks a download is occuring, it blocks the request.

I do think there is some sort of criteria regarding when Cloudflare blocks a page and when it doesn't, as some users report that it's working perfectly, and ... well... some don't.

I have no updates still having the same problems (if anything it got worse it never checks more than 20 stories anymore) but i have a couple of questions if you don't mind. Is it possible to partition updates or is it too much work that you might as well redesign the whole thing? What i mean is say if there is 15 new chapters to download if the error comes after 5 is downloaded that error still cause you to lose those chapters so it goes back to where it was but if there is a way to download them 5 by 5 it could potentially make a dfference. In the same vein i am currently trying to download a new106 chapters story but it never download more than 10 before it flashes the error again so those downloaded chapters are also lost. Similar but this one has to do with filtering, is it possible to add more options to filtering including "exclude"? And maybe some thing like (include or exclude) "last updated between this and this dates" and "recently checked for updates with no results" This could partially solve rechecking the recently updated chapters again and again every time you try to update but not checking older ones (or least popular or least followed etc...). Since i never went past checking 100 stories out of 2.8k before getting the error it always checks the same stories. There were some other questions i have been meaning to ask but i just woke up so i cant think at the moment😋 . Anyway once again thank you for your hard work

[hallowknight99]

@ErinArt You could send me the name of a story just to double check, although I doubt the issue is actually related to the stories at all. The FanFiction.net added the Cloudflare system to discourage downloading stories. Whenever Cloudflare thinks a download is occuring, it blocks the request. I do think there is some sort of criteria regarding when Cloudflare blocks a page and when it doesn't, as some users report that it's working perfectly, and ... well... some don't.

I have no updates still having the same problems (if anything it got worse it never checks more than 20 stories anymore) but i have a couple of questions if you don't mind. Is it possible to partition updates or is it too much work that you might as well redesign the whole thing? What i mean is say if there is 15 new chapters to download if the error comes after 5 is downloaded that error still cause you to lose those chapters so it goes back to where it was but if there is a way to download them 5 by 5 it could potentially make a dfference. In the same vein i am currently trying to download a new106 chapters story but it never download more than 10 before it flashes the error again so those downloaded chapters are also lost. Similar but this one has to do with filtering, is it possible to add more options to filtering including "exclude"? And maybe some thing like (include or exclude) "last updated between this and this dates" and "recently checked for updates with no results" This could partially solve rechecking the recently updated chapters again and again every time you try to update but not checking older ones (or least popular or least followed etc...). Since i never went past checking 100 stories out of 2.8k before getting the error it always checks the same stories. There were some other questions i have been meaning to ask but i just woke up so i cant think at the moment😋 . Anyway once again thank you for your hard work

If you exclude completed, choose a certain category (star wars, iron man etc) and choose a sort by view (last added, follows) this should help you find the story that is causing you the problem.

[ghrrrr]

@ErinArt You could send me the name of a story just to double check, although I doubt the issue is actually related to the stories at all. The FanFiction.net added the Cloudflare system to discourage downloading stories. Whenever Cloudflare thinks a download is occuring, it blocks the request. I do think there is some sort of criteria regarding when Cloudflare blocks a page and when it doesn't, as some users report that it's working perfectly, and ... well... some don't.

I have no updates still having the same problems (if anything it got worse it never checks more than 20 stories anymore) but i have a couple of questions if you don't mind. Is it possible to partition updates or is it too much work that you might as well redesign the whole thing? What i mean is say if there is 15 new chapters to download if the error comes after 5 is downloaded that error still cause you to lose those chapters so it goes back to where it was but if there is a way to download them 5 by 5 it could potentially make a dfference. In the same vein i am currently trying to download a new106 chapters story but it never download more than 10 before it flashes the error again so those downloaded chapters are also lost. Similar but this one has to do with filtering, is it possible to add more options to filtering including "exclude"? And maybe some thing like (include or exclude) "last updated between this and this dates" and "recently checked for updates with no results" This could partially solve rechecking the recently updated chapters again and again every time you try to update but not checking older ones (or least popular or least followed etc...). Since i never went past checking 100 stories out of 2.8k before getting the error it always checks the same stories. There were some other questions i have been meaning to ask but i just woke up so i cant think at the moment😋 . Anyway once again thank you for your hard work

If you exclude completed, choose a certain category (star wars, iron man etc) and choose a sort by view (last added, follows) this should help you find the story that is causing you the problem.

Thanks for the suggestion i have already done what i can short of entering each story manually and updating one by one (which also doesnt always work in case of multiple new chapters) but it is not easy to divide ~3k stories to chunks of 20 plus knowing what you have updated what you never checked. And it is not like only 1 or 2 particular stories that is causing the problems. I still think it has to do with how many request the program makes of the site in a limited timeframe. I cant be sure of course but that is my experience so far.

[hallowknight99]

@ErinArt You could send me the name of a story just to double check, although I doubt the issue is actually related to the stories at all. The FanFiction.net added the Cloudflare system to discourage downloading stories. Whenever Cloudflare thinks a download is occuring, it blocks the request. I do think there is some sort of criteria regarding when Cloudflare blocks a page and when it doesn't, as some users report that it's working perfectly, and ... well... some don't.

I have no updates still having the same problems (if anything it got worse it never checks more than 20 stories anymore) but i have a couple of questions if you don't mind. Is it possible to partition updates or is it too much work that you might as well redesign the whole thing? What i mean is say if there is 15 new chapters to download if the error comes after 5 is downloaded that error still cause you to lose those chapters so it goes back to where it was but if there is a way to download them 5 by 5 it could potentially make a dfference. In the same vein i am currently trying to download a new106 chapters story but it never download more than 10 before it flashes the error again so those downloaded chapters are also lost. Similar but this one has to do with filtering, is it possible to add more options to filtering including "exclude"? And maybe some thing like (include or exclude) "last updated between this and this dates" and "recently checked for updates with no results" This could partially solve rechecking the recently updated chapters again and again every time you try to update but not checking older ones (or least popular or least followed etc...). Since i never went past checking 100 stories out of 2.8k before getting the error it always checks the same stories. There were some other questions i have been meaning to ask but i just woke up so i cant think at the moment😋 . Anyway once again thank you for your hard work

If you exclude completed, choose a certain category (star wars, iron man etc) and choose a sort by view (last added, follows) this should help you find the story that is causing you the problem.

Thanks for the suggestion i have already done what i can short of entering each story manually and updating one by one (which also doesnt always work in case of multiple new chapters) but it is not easy to divide ~3k stories to chunks of 20 plus knowing what you have updated what you never checked. And it is not like only 1 or 2 particular stories that is causing the problems. I still think it has to do with how many request the program makes of the site in a limited timeframe. I cant be sure of course but that is my experience so far.

I am only short of 2k. I agree with you regarding the number of requests. I think it should be more like wattpad as that checks for updates in the backbround even when app isn't open. Also wish it checks faster. The backup and restore doesn't seem to work on android 10 for a new device.

[ErinArt]

@ErinArt You could send me the name of a story just to double check, although I doubt the issue is actually related to the stories at all. The FanFiction.net added the Cloudflare system to discourage downloading stories. Whenever Cloudflare thinks a download is occuring, it blocks the request. I do think there is some sort of criteria regarding when Cloudflare blocks a page and when it doesn't, as some users report that it's working perfectly, and ... well... some don't.

I have no updates still having the same problems (if anything it got worse it never checks more than 20 stories anymore) but i have a couple of questions if you don't mind. Is it possible to partition updates or is it too much work that you might as well redesign the whole thing? What i mean is say if there is 15 new chapters to download if the error comes after 5 is downloaded that error still cause you to lose those chapters so it goes back to where it was but if there is a way to download them 5 by 5 it could potentially make a dfference. In the same vein i am currently trying to download a new106 chapters story but it never download more than 10 before it flashes the error again so those downloaded chapters are also lost. Similar but this one has to do with filtering, is it possible to add more options to filtering including "exclude"? And maybe some thing like (include or exclude) "last updated between this and this dates" and "recently checked for updates with no results" This could partially solve rechecking the recently updated chapters again and again every time you try to update but not checking older ones (or least popular or least followed etc...). Since i never went past checking 100 stories out of 2.8k before getting the error it always checks the same stories. There were some other questions i have been meaning to ask but i just woke up so i cant think at the moment😋 . Anyway once again thank you for your hard work

If you exclude completed, choose a certain category (star wars, iron man etc) and choose a sort by view (last added, follows) this should help you find the story that is causing you the problem.

Thanks for the suggestion i have already done what i can short of entering each story manually and updating one by one (which also doesnt always work in case of multiple new chapters) but it is not easy to divide ~3k stories to chunks of 20 plus knowing what you have updated what you never checked. And it is not like only 1 or 2 particular stories that is causing the problems. I still think it has to do with how many request the program makes of the site in a limited timeframe. I cant be sure of course but that is my experience so far.

I am only short of 2k. I agree with you regarding the number of requests. I think it should be more like wattpad as that checks for updates in the backbround even when app isn't open. Also wish it checks faster. The backup and restore doesn't seem to work on android 10 for a new device.

I just had a thought, but, maybe it has something to do with the incremental updating? I use the option where a story will redownload every chapter, maybe the option where it only downloads the new chapters has less issues with downloading updates? It's just a thought I had, no idea if that could be the issue, but I thought I'd mention it.

[Luminatrix-eng]

@ErinArt from what I understand, the app only checks for new chapters instead of redownloading every chapter. I could be wrong but it does this by using the mobile version of m.fanfiction.net and then matches the story via the id number and then checks for new updates.

@hallowknight99 I have a solution that you guys can use if you don't want to do mass bulk updating. If you set follow your stories, fanfiction sends a notification to your email advising you that a new chapter is out. Then choose the category that story is updated, you can manually update the specific story only.

This gives me an idea of potentially making a script that reads the notification, probably in a hidden mobile browser and somehow direct it at the app to manually update stories in the background in real-time. But this is far outside my experience at this point of time. I wouldn't even know where to begin lol.

[Quetzalcoatless]

The update check failing may be an old, pre-Cloudflare issue. FFN will very rarely return a 503 error for a request (so rare that it usually only shows up when updating a multi-thousand story library), and the app will currently abort the update check after a single error even though subsequent requests will almost always succeed. People updating large libraries that are several months out-of-date are very likely to run into this issue due to the sheer number of requests they're making.

I added an error threshold in my personal branch so the app only cancels the update check if multiple errors occur in a row for a single chapter. I haven't tested my branch with the Cloudflare changes yet, but it should still work.