Uncaught (in promise) TypeError: Cannot read property 'children' of null

[martonlederer]

The bug
Navigating from a specific page to another causes Uncaught (in promise) TypeError: Cannot read property 'children' of null and a blank page. It only occurs when navigation from /app to /app/all-transactions (repo below). Going to the route directly or reloading does not cause this issue

Logs

VM9796:118 Uncaught (in promise) TypeError: Cannot read property 'children' of null
    at removeNode (<anonymous>:118:31)
    at Object.block.d (<anonymous>:280:11)
    at destroy (LatestTransactions.svelte:136)
    at updateProfile (<anonymous>:49:7)
    at Object.block.d (<anonymous>:283:9)
    at destroy_component (index.mjs:1396)
    at destroy (app.svelte:28)
    at updateProfile (<anonymous>:49:7)
    at Object.block.d (<anonymous>:283:9)
    at destroy_component (index.mjs:1396)

To Reproduce
Use this repository: https://github.com/useverto/verto

Information about your Svelte project:

• Your browser and the version: Brave 1.10.97 Chromium: 83.0.4103.116 (Official Build) (64-bit)

• Svelte version: latest ("^3.24.1")

• Rollup

• Using Sapper ("^0.28.0")

[martonlederer]

Tried updating all rollup/svelte dependencies and tried this comment from #2086

[arggh]

I'm encountering possibly the same bug:

Uncaught TypeError: Cannot read property 'children' of undefined
    at removeNode (<anonymous>:118:31)
    at Object.block.d (<anonymous>:280:11)
    at destroy_component (modules.js?hash=241e361d86eb4a5c7deb890962cfc97e6c02b251:9785)
    at Confirm.$destroy (modules.js?hash=241e361d86eb4a5c7deb890962cfc97e6c02b251:9914)

Happens when I'm using a Dialog component that gets rendered as it's own "app" on the document.body, and then removed.

[arggh]

I was puzzled why this specific bit of our app was suddenly broken - haven't touched it, haven't updated Svelte, haven't done nothing but vacationing for three weeks.

I just tried to trigger the bug with Firefox, but I can't. It works. It also works on Safari. And Brave.

So, my suggestion is... Chrome pushed out a new release that broke Svelte? 😬

[arggh]

I think my guess was correct.

The previous version of Chrome on my laptop was 83.0.4103.116.

I now updated to 84.0.4147.135 and the error disappeared 🤷‍♂️

[martonlederer]

No idea. I'm using brave and it throws the error. Brave uses chromium

[arggh]

No idea. I'm using brave and it throws the error. Brave uses chromium

Have you tried Firefox, Safari, Opera etc. to rule out the possibility that your Brave browser is using a version of Chromium that has the same (potential) bug that I (think I) had?

[martonlederer]

I will make sure to do so

[Thijsrausch]

Not sure what is the cause of the bug, but I have the same problem in the latest Chrome, latest Firefox (80.0.1) and latest Edge 85.0.564.51 (but that's Chromium as well). I don't think it is an issue with browsers.

[Thijsrausch]

The answer to this related stackoverflow question solved my problem, maybe it can help you guys as well.

[gijswobben]

Same issue here. I'm not using Sapper, just Svelte. I'm using page for routing, but even with plain <a href="/somepath" ... it's not working... Only for specific routes though. I haven't been able to pinpoint the issue so far, any help is appreciated!

[newtriks]

I've been having this issue in various instances also, typically within if blocks (and font-awesome for example) or using slots. #5290 (comment) SO solution seems to work 🙏 but it's nay cool.

[jiangfengming]

I removed the Svelte Devtools and solved.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed as it was previously marked as stale and saw no subsequent activity.

[NsdHSO]

I removed the Svelte Devtools and solved.

But we need the svelte devtools. how to proceed to stop getting this error.