discuitnet
Error whenever I open the site.
Whenever I go to discuit an error got triggered and I am left with the following massege:
Something went wrong Error: Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Try reloading page
I've spent some time trying to reproduce or get some detailed output but try as I might I can't get it to break. This goes for discuit.net and the dev instance I have setup.
OS: KDE Neon (using Wayland) Browser: Ungoogled Chromium Flatpak
Maybe someone else will have better luck?
I'm assuming, @XCE0, you're not talking about the discuit.net instance, since that's working fine. My guess would be that something's up with your config.yaml file. What does it look like?
I am not a developer, does the masseges in the browser console could benefit you in finding the bug?
if that is the case tell me and I will copy and paste it here.
Oh, this is extremely weird. I've never seen this error before, and I have no idea how to reproduce it.
I am not a developer, does the masseges in the browser console could benefit you in finding the bug?
The error logs in the browser console certainly could help, thanks. Maybe the addon is messing something up? Could you check if the site works in an incognito window?
The same error happens in the incognito window.
This is the error massages in the browser console :
The service worker navigation preload request was cancelled before 'preloadResponse' settled. If you intend to use 'preloadResponse', use waitUntil() or respondWith() to wait for the promise to settle.
Uncaught (in promise) DOMException: The service worker navigation preload request was cancelled before 'preloadResponse' settled. If you intend to use 'preloadResponse', use waitUntil() or respondWith() to wait for the promise to settle.
Error: Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at oc (app.b15ae39ad7d85c2435b8.js:2:176116) at nl (app.b15ae39ad7d85c2435b8.js:2:141111) at Object.e [as onStateChange] (app.b15ae39ad7d85c2435b8.js:2:259690) at Object.o [as callback] (app.b15ae39ad7d85c2435b8.js:2:257172) at app.b15ae39ad7d85c2435b8.js:2:257367 at dc (app.b15ae39ad7d85c2435b8.js:2:179434) at Object.notify (app.b15ae39ad7d85c2435b8.js:2:257336) at Object.notifyNestedSubs (app.b15ae39ad7d85c2435b8.js:2:257749) at o (app.b15ae39ad7d85c2435b8.js:2:257172) at g (app.b15ae39ad7d85c2435b8.js:2:230755) fl @ app.b15ae39ad7d85c2435b8.js:2
Thanks. What's the Linux distro you're using? (I'll try spinning up a VM to see if I can reproduce the error).
Opensuse Microos
Any chance you're running on ARM or another architecture? I only ask because it works fine on OpenSUSE MicroOS (KDE, which is in alpha support) and I could not get it to break. I did my best to recreate what you've mentioned here but I've had no luck. I'm using the Ungoogled Chromium Flatpak.
Screenshot of it working:
System information:
If you aren't running on another architecture or have some other, nonstandard hardware config (like I do, with my franken eGPU setup), I'm not sure there is anything to fix on the repo side (though I'm open to more testing)
This gets weirder and weirder.
@XCE0, did you notice any other sites breaking in a similar way?
I agree, this is very strange. I think I saw that Firefox was also included on the OS, does that work? (Waterfox would also work if you prefer not to install/use Firefox.)
I would just be curious if it works at all.