Safari returns the same error. Even after DNS/VPN re fondling. So, you suggest it’s an provider thing?
At last the image generation isn’t even the killer argument for using perchance. For me it‘s the low entry level that finally made me getting in touch with js in general.
Learning about web frameworks always were my personal nemisis and I sticked with C - but perchance finally made me taking a look at js. That’s the great benifit of it. Learning-Platform/Playground instead of service application, tho
Noice. Let me search for a well-readable file (incl. all the other info you‘ll need),
Then I send all directly to the Devs. Thank you dude
New exports are working well now. (incognito/regular mode issues are similar.
I‘ll send you my original user agent, which should contain all version info you need, cool?!
Hey there; Thank you for answering.
The issue appears with older exports, as well as with exports I‘d done later.
The Error-Message I was reseaving in „incognito-mode“ isn’t the same as that one I got before.
Some of the exported json files worked earlier, but now (even it’s another) all of them error messageing me. I send you the given errors:
((iOS 15.3<)) (Safari version I need to research first)
Phew, lucky there is already a bug-Report. I thought it was my fault.
In my case it seems like there is a corrupted method within the „db“ build/read/store process. (Since I am on Safari mobile there could also be a little issue with GET. So it might not reproduce the exact same error as it would with chromium/FF based browsers).
Dizzle
joined 1 year ago
Man muss sich Sisiphus zufrieden vorstellen.