@_08

Gotcha

@myskaros Thank you

@sam-pinansky thanks. Looks like they all work now :)

I think you can alway redeem a credit by directly acceding the redeeming page of the book you want:
https://j-novel.club/mypage/redeemCredit?title=ao-oni-grudge
Here it's for "ao oni grudge" but you just need to change the title to the one you want with "-" in place of space.

Regardless of catchup you can not download prepub parts.

Thanks, I only saw it on my RSS Feed.

I wouldn't read too much into front line support for big companies. The people answering the ticket often don't have the ability to look too deeply into your issue. They're likely basing their response on the idea that Amazon processes should never allow them to upload the incorrect version of a file to their site, so the problem has to be the publisher.

But I'm with Pancake here, unless you have a specific reason to stick with Amazon here, you might see if they'll refund your purchase and just get it from somewhere else.

Yep me too. Firefox user on my android and my windows at home.
I am getting around it by using my phone only now, and taking a Screenshot of the text in the instant before it vanishes, reading it that way, and then going to the next page where the text problem surprisingly isn't acting up. Then I repeat the process on the page after that. It works out that I take a screenshot to read every second page.

Thank you for the responses, I checked today, and it is there when it's not on the featured search. I guess that's that!

the whole site has been super slow for the past few days no matter what network I'm on, phone client, web client, pc, etc.

Yeah, the site is having some backend troubles these days. Sometimes I have to wait even ~2 minutes for a part to load in the web reader. Hopefully Sam fixes it soon.

It was a mistake on our part! Sorry about that!

@saffire
sweet thanks

@rahul-balaggan i apologize i didn’t mean to do that

@someoldguy us, you're right. It's my email provider that has the upload limit of 20mb per.

I don't know if login tokens ever expire on their own, but the server doesn't keep them in permanent storage. IIRC it's a RAM cache, so whenever somebody has to restart/reboot anything (like after making an update to the site code), it invalidates all the existing login tokens. The handling for users with invalid tokens isn't the greatest, so instead of immediately kicking you back to the login page, you sometimes get strange behaviour like "can't access stuff even though it looks like you're logged in".

The issue has been already reported both here in the forum and in Discord. The epub file is manually uploaded by Sam, until he's around to fix it the error will remain. Considering today is a Sunday I guess it will be fixed tomorrow(?).

@kyanos The part is up now, it just got fixed like a minute ago 😁