Minified React error #185 - can't access my notes

[merry stream]

The app is broken. Displays this and nothing else (no menus, notes, not even a title bar).

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.
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 Gr (https://app.notesnook.com/assets/root-CfZWotN9-dhZ.js:296:33813)
at vI (https://app.notesnook.com/assets/root-CfZWotN9-dhZ.js:294:21874)
at Object.onChange (https://app.notesnook.com/assets/index-B5c9iR0fkS-H.js:10:13207)
at Virtualizer.notify (https://app.notesnook.com/assets/index-B5c9iR0fkS-H.js:10:3799)
at Virtualizer.resizeItem (https://app.notesnook.com/assets/index-B5c9iR0fkS-H.js:10:8827)
at Virtualizer._measureElement (https://app.notesnook.com/assets/index-B5c9iR0fkS-H.js:10:8223)
at Virtualizer.measureElement (https://app.notesnook.com/assets/index-B5c9iR0fkS-H.js:10:8993)
at R2 (https://app.notesnook.com/assets/root-CfZWotN9-dhZ.js:296:24408)
at nv (https://app.notesnook.com/assets/root-CfZWotN9-dhZ.js:296:32541)
at T8 (https://app.notesnook.com/assets/root-CfZWotN9-dhZ.js:296:31451)

[cyan bane]

Hi, can you give more information about this bug? Where does it occurs? which device? OS version? app version?

[crimson oriole]

Just got this as well in the Desktop version on Windows.
App+version:+3.3.8-406c637-desktop

[cyan bane]

make sure your app is up-to-date

the latest version is v3.3.16 (released today)

[crimson oriole]

Sure but I can't update the app as it crashes immediately

I use self-hosted btw so maybe Im not representative for OP's situation

I guess I can reinstall a newer version to try and fix it. Still strange it happened without me making any changes

[cyan bane]

you should post this in the #self-hosting @crimson oriole, im sure the people there will help you sort this out

I dont have the self-hosting knowledge to help

@crimson oriole dont forget to give all the info you can share so people there can help you properly

[crimson oriole]

So I'm back because it's not self-hosted related (Im pretty sure): I updated to the latest version of the desktop app and it still crashed. Figured out it is on a specific note. If I'm super quick with hitting tab/ctrl+tab to select a different open tab, the app won't crash. As soon as I open the specific note, notesnook crashes.. Unfortunately on the desktop app I can't restore an older version (feature tip!) like on Android.

I did think of a workaround: copy the contents on a client that does work (in my case Android) > paste contents to new note. On windows desktop I could open the new note. Unfortunately you do lose the history of the old note...

[cyan bane]

can you export the contents of the note, using the right click options and see whats bugged there?

this is really weird

I'll let @viscid fox know about this

[merry stream]

Thanks for the replies. Here's more detail and how I managed to work around the problem.

I have v3.3.15 on Fedora 43. The problem occurred on the desktop version, and I agree that it was caused by a single note. Let's call it "faulty."
It was much better with the browser (Brave) – I had access to all notes except the faulty one (because by default, the web app opened on a different note). Clicking on the "faulty" note would freeze website – nothing happened in the console or network. This is probably why the web app still opened on some other note by default.

The most interesting thing was on Android – everything worked perfectly. I could even see the last changes I made to the "faulty" note before the desktop app stopped working. So what I did on mobile was export this note (just in case), then cut all the content from the "faulty" note and pasted it into a new note, then deleted the original "faulty" note. This allowed the desktop app to work again — it doesn't try to open the deleted "faulty" note. And the best part is, I can access the created copy on the desktop and work on it 🙂

The note is ~32,500 words long, and its size after export is 803 KB, so I guess that wasn't the problem.

[viscid fox]

Are you facing the same error? Can you send me a screenshot?

[merry stream]

I'll probably be able to generate this error again myself. Currently, while working on a copy of the note I mentioned, I'm getting the notification shown in the screenshot. I'm almost certain I was also receiving this notification before the original error occurred.

[crimson oriole]

This is my error

[crimson oriole]

I don't see this message (at least not in my note where I copied the content from the faulty note)

[crimson oriole]

At first glance nothing is bugged, but I don't know what I'm looking for and it is a rather big note. I do see something strange: when copying as markdown and pasting it in a new note on Notesnook desktop, all the check boxes are turned into task lists with empty tasks. Don't think that is the issue though, because this also happens with the working version of the note (the one I copied the contents of via the Android app).

[crimson oriole]

New observation: I restored the faulty note to the day before the crash on the Android app, but Notesnook desktop still crashed on the note. Figured that maybe the error was still on the last change of the desktop, so I then restored on Android again and tried to force pull on desktop before opening the note; but it crashed again. Then restored again on Android, force push and then force pull on desktop; still no dice...

Can I somehow remove the faulty change on the desktop app?

[viscid fox]

I don't think its related to the note

[crimson oriole]

Ok, check. Then I'll stop messing with it 🙂

You want me to check anything else to give you more debug info?