Blank page login Komga accessing from Ipad Mini 3 on browser

[serpichino]

Steps to reproduce

Going online through browser Chrome, Safari,Firefox or others with Ipad Mini 3, it's about ten days that I cannot login on Komga. I just see the favicon and then nothing, a blank page. Until a couple of weeks ago everything worked fine, I changed nothing because I use this Ipad only for comics on Komga.

Expected behavior

I should see the login form like before.

Actual behavior

Blank page with only the favicon, but only with the Ipad. On PC or phone it works perfect. I made a complete factory reset but nothing changed.

Logs

No response

Komga version

web browser

Operating system

Ipad with 12.5.7

Other details

No response

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I have checked the FAQ.
• I have updated the app to the latest version.
• I will fill out all of the requested information in this form.

[gotson]

It's from 2014, it may be that the browser is out of date and does not support recent websites.

[serpichino]

Possible and I know it is an old device but I used it in the last months almost everyday to login on Komga and the problem appeared only two weeks ago. I have another old tablet android, a Samsung SM-T560 (Galaxy Tab E) that shows a similar problem, the access page is not totally blank but the Komga logo appears in the page. The funny thing is that a friend of mine has the same Mini Ipad 3 like me, on which Komga through Chrome works perfectly.

[Konne06]

me too, im mini2 and any browser has this problem

[Thilas]

Same here on my iPad mini 2 (iOS 12.5.7 as well) and Komga 1.7.2 (but the problem started when I was on a previous version). I tested several browser like Safari, Brave, Chrome (but not on the latest version because of the old iOS version) and Opera (latest version), private session or not, all have the issue: blank page instead of login page with favicon.

[gotson]

All ios browsers are using the same underlying engine so they are basically all the same browser.

[serpichino]

Ok, but why does it happen and why are there people who I know that have my same Ipad, using the same browser but they do not have the same problems accessing Komga?

[gotson]

Ok, but why does it happen and why are there people who I know that have my same Ipad, using the same browser but they do not have the same problems accessing Komga?

I don't know. No one in this thread managed to provide the exact version or information about the browser they use.

[serpichino]

English is not my mothertongue, maybe I did not understand exactly what you need to proceed. Which informations do you need?

[Thilas]

I don't know. No one in this thread managed to provide the exact version or information about the browser they use.

@gotson, I tried to provide all the information I have. If anything is missing, I'll give it here right away, just let me know.

All ios browsers are using the same underlying engine so they are basically all the same browser.

If you are correct, knowing the version of iOS (12.5.7 as mentioned above) and Komga (1.2.7) should be enough, right?

[gotson]

The ios version is useless to me. I need the browser engine version.

[kiriya-aoi]

Any iOS 12.5 device is running Safari 12.1/WebKit 607.x.y.

[gotson]

Any iOS 12.5 device is running Safari 12.1/WebKit 607.x.y.

Thanks, that's actually useful. Current browserlist is:

> 1%
last 2 versions
not dead

Maybe adding ios >= 12 would help.

[serpichino]

What does your last post mean? Where should I add "ios >= 12"?

[gotson]

What does your last post mean? Where should I add "ios >= 12"?

It's a build configuration that will build the website files with the target browsers. This should build a website that is supported on ios 12+.

Let's see at the next release if that works. If not, well, I don't have any more ideas.

[serpichino]

Thank you! Do you have an idea of when will next release be updated?

[gotson]

Soon™

[github-actions]

🎉 This issue has been resolved in 1.8.4 (Release Notes)

[gotson]

@serpichino did you try the latest version? Does it solve the problem on older iPad?

[Thilas]

I've tested the last version and the login page is back! Unfortunately I'm having an error while authenticating. I'll post a screenshot as soon as I can.

[serpichino]

Unfortunately it does not work. Safari says that the page cannot be opened because the server cannot be reached. So it remains blank. Chrome instead shows the login page and then the same problem reported by @Thilas . See the photo below after authentification.

[Thilas]

I confirm this is the same error I have. Though I have it on Safari (only browser I tested with the latest version so far).

[gotson]

Without more details on the error there's not much I can do.

[serpichino]

What kind of details do you need? Browsers and systems are the same above, you can not update anything on these old tablets.

[DieselTech]

Can you open up the dev tools for the page and try to get the error that is showing up there? How that's done on a iOS device I'm not sure, normally would be F12 on a keyboard.

[serpichino]

My device is an old Ipad Mini 3 that worked perfectly with Komga until about two moths ago. So the problem is due to some recent changes. There's no keyboard and the typical Apple interface does not let you too much freedom. The problem seems like the one below:

https://rollbar.com/blog/javascript-chunk-load-error/

Could it be?

[DieselTech]

The sad fact is your device is just too old and outdated to keep up with the ever evolving landscape of web design anymore. What used to work in the past no longer does because development of web standards doesn't stop. If you want to use such an outdated device then you also need to use an outdated version of komga. You'll forever be locked to that version of komga until you get a more modern device. This is the path apple has chosen, any beef should be taken up with with them.

[serpichino]

Well, I would certainly stay to that "outdated" version of Komga...if I could choose. Unfortunately, Komga version through browser is chosen by the web developer. A similar problem occurs with an old Android tablet. Until two months ago both worked. As I saw it is just a decision of the developer activate or not the option in the code for the version supported and resolve javascript errors, technically there is no "real" problem. So...even this is planned obsolescence like Apple does and like you said. Curious, right?

[DieselTech]

Well, I would certainly stay to that "outdated" version of Komga...if I could choose.

You can choose. Go back through github releases and grab an older version that will work with your device. You just won't be getting new features that are coming out because none of the web standards are targeting out dated unsupported by the manufacture devices anymore.

[serpichino]

Maybe you lost some steps. I access to Komga through browser, not through app. The version on the website is not chosen by me.

[DieselTech]

Maybe you lost some steps. I access to Komga through browser, not through app. The version on the website is not chosen by me.

Do you run your own instance or are you a user of someone else's instance where they invited you?

[serpichino]

I turn my Ipad Mini 3 on, i open Chrome/Safari/ (now only Chrome works), i write my server address in the address bar. That's all.