search

LBlend / mann-eller-kvinne

🤵 En nettside som bruker maskinlæring til å gjette om du er mann eller kvinne basert på hva du skriver 💃
https://mannellerkvinne.lblend.moe
GNU General Public License v3.0
1 stars 0 forks source link

Site crashes on load when using Safari on iOS #3

Closed LBlend closed 2 years ago

LBlend commented 3 years ago

image

See https://github.com/vercel/next.js/issues/8347 for a potential solution

marksverdhei commented 3 years ago

The server should host the app with serve -s build after calling npm run-script build (instead of using npm start). It might prohibit the site from breaking (which is better), so we should try to reproduce it after doing this Make sure to npm install -g serve first

LBlend commented 3 years ago

The server should host the app with serve -s build after calling npm run-script build (instead of using npm start). It might prohibit the site from breaking (which is better), so we should try to reproduce it after doing this Make sure to npm install -g serve first

I will check whether or not this resolves the issue when I can get a hand on an iOS device. Probably by 2020-01-22.

I'll report back to you then.

LBlend commented 3 years ago

The server should host the app with serve -s build after calling npm run-script build (instead of using npm start). It might prohibit the site from breaking (which is better), so we should try to reproduce it after doing this Make sure to npm install -g serve first

I will check whether or not this resolves the issue when I can get a hand on an iOS device. Probably by 2020-01-22.

I'll report back to you then.

Ok so I've tested the website and the error doesn't occur when the website is built. We should still consider fixing the issue though.

Even though I'm not 100% confident in what the issue is casued by, it is probably caused by this. If this is the issue I suggest we fix it by doing the following:

By implementing the idea that I have proposed in the first bullet point, you can address the 2nd point at the same time. I actually implemented this feature in early builds of this project but decided to get rid of it before the initial commit due to complications.

LBlend commented 2 years ago

Since we're doing a rewrite, this won't be an issue anymore.