Yet Another PWA JNC Client

Iseguy

@Crimson-Wise Thanks for the updates! I noticed the “information” option; that's nice to have.

Unfortunately, refreshing doesn't seem to help. I also tried selecting “disable cache” in DevTools, didn't work either. ~~Maybe a CDN cache needs to be invalidated?~~

Iseguy

@Crimson-Wise OK, I was able to find a workaround. I reached into jncu-db and deleted the “user” and “login” keys. “.data” was undefined for both, but after deleting them and logging in again they're populated with reasonable data. Everything seems to be working now.

Crimson Wise

@Iseguy Interesting, thanks for letting me know, will add some safeguard for it most likely, whatever the cause was.

@alfonso_rd_36 said in Yet Another PWA JNC Client:

welp, finally managed to make the lñong series move (Click on the esries, then the arrows on the keyboard)

Wait, what?

alfonso_rd_36

@Crimson-Wise

As I said, for the "long series" (multiple volume series like Book-a-Worm or Demon Lord Retry!) When using the phone one can just swipe left or right and it moves to display the older prepubs, but on PC? There are no gestures on PC, so I assumed that one couldn't get to read those older prepubs, but lo and behold, once reading DLR! I clicked on the area of the book and then upon pressing the arrow keys, it moved!

Crimson Wise

@alfonso_rd_36 Ah, get you know. I was using the horizontal scrolling from my mouse so didn't pay too much attention to that behaviour. (Not that I use it that much on my computer either.)

sniper_samurai

Seems this has stopped working. Screen goes blank after a couple of seconds, I'd say it might be getting blocked by the API.

Crimson Wise

@sniper_samurai Not really, but some "inconsistency" on JNC's data if I can call it that - Potion Loli 5 has a part but is missing the volume on the JNC API, which crashes my app.

I pushed a workaround like a couple of hours ago, can you refresh the page if you're in the browser?

If you have it on the iOS Home Screen, it takes like a day before the website gets invalidated and refreshed, so tomorrow should be fine - I still need to figure out how to fix this.

sniper_samurai

@Crimson-Wise Yeah, just checked the website. Seems to show all the future parts of Potion Loli 5 as well, even though they aren't available yet.

Freyr

Works very well, I use it on a iPad and a iphone +. The following section works very well, I also like that it shows which parts have been read. So much better then the app.

alfonso_rd_36

@Freyr I know, right? It's a pinned tab nXt the JNC Forums tab

Shiny

@Freyr said in Yet Another PWA JNC Client:

Works very well, I use it on a iPad and a iphone +. The following section works very well, I also like that it shows which parts have been read. So much better then the app.

On Android phone and the UI works well and the functionality and reliability is better than the official all. Since it launched it has remained my go to reader.

Crimson Wise

Thanks! Glad that people enjoy the app.

Shiny

I'm still using this as my main reader on Android, so thanks again @crimson-wise for your work on it. One major improvement would be if it used the watch/follow list from the beta website/app. This would get around the app's problem that every so often it forgets all the follow settings.

Crimson Wise

@Shiny wasn't aware of that.

Well, took a look at the API for that and seemed simple enough, so replaced the follow logic with the one from JNC. Note that this means that current users' followed series are lost (sorry) but I think this is better long term.

Anyway, this release includes some other improvements:

Upcoming bar: noticed that the events API now includes the series ID so added the section, to see what is coming soon.
Manga is now listed: note that you can't read the chapters on the app, but it will tell you that a new part is available. I go to the beta app to read them. And regarding progress, the JNC API doesn't really say the percentage, so manga parts will be either read or not. I think the beta app ended up implementing it the same way.
And some other minor things since I haven't made a release since July.

~~Edit: noticed that the shadows are wrong on the Upcoming bar, more noticeable on light mode. Will fix some other day.~~ Done.

Freyr

The new version is great and still much better then the beta app which is hard to read on an iPad. The upcoming releases feature is even, more convenient then the main website.

Thanks.

Shiny

@Crimson-Wise said in Yet Another PWA JNC Client:

@Shiny wasn't aware of that.

Well, took a look at the API for that and seemed simple enough, so replaced the follow logic with the one from JNC. Note that this means that current users' followed series are lost (sorry) but I think this is better long term.

From my perspective it's definitely better in the long term. Thanks for the improvements.

Iseguy

I've noticed that the app is no longer sending my password to the server when I try to login, even though I've confirmed that my password manager is filling it in to the form:
(Literal traffic with the exception of my email address and encoding.)

App.tsx:137 Refreshing data...
App.tsx:399 Missing volume info for 600a84aed4a6298b3e69ba48
ViewLogin.tsx:20 POST https://api.j-novel.club/api/users/login?include=user 401
{"email":"xxxxxxxxxxx@gmail.com","password":""}
{"error":{"name":"Error","status":401,"message":"login failed","statusCode":401,"code":"LOGIN_FAILED"}}

App.tsx:137 Refreshing data...
App.tsx:399 Missing volume info for 600a84aed4a6298b3e69ba48
App.tsx:234 GET https://api.j-novel.club/api/users/undefined?filter={%22include%22:[%22ownedBooks%22,%22readParts%22,%22mangaReadParts%22,%22serieFollows%22,%22mangaSerieFollows%22]} 401
filter: {"include":["ownedBooks","readParts","mangaReadParts","serieFollows","mangaSerieFollows"]}
{"error":{"name":"Error","status":401,"message":"Authorization Required","statusCode":401,"code":"AUTHORIZATION_REQUIRED"}}

Crimson Wise

@Iseguy Thank for letting me know. Which browser/password manager are you using? Perhaps I'm running into this issue. Would you mind trying copy/pasting the password instead to confirm?

Iseguy

@Crimson-Wise I'm using Chrome 88.0.4324.104 (Official Build) (64-bit) with the built-in password manager.

I did a bit of exploration, and there seems to be some scripting running on that element that's interfering with the normal functioning of the <input>. Like, the app isn't looking at the actual value of the element but rather at some JavaScript variable that's normally updated by events that aren't getting fired when the password manager does it. I would guess that it's hooked the keypress events but not any other input or changed events.

I have found the workaround is to start by typing something into the field, which erases everything that was pasted in before the first keypress but seems to put it into a state where it acts like a real text box. Then, apply the password via the password manager. Then type another character at the end of the password, and then delete the character you added. Then submit.

Crimson Wise

@Iseguy Thanks, and yes, that's how it works. I guess I'll just replace Ionic's fields with raw HTML; will take a look.