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

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")

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 15 (4 by maintainers)

Commits related to this issue

v0.15.0 - added a "play" and "stop" button * added a "play" and "stop" button, to launch the task, and to stop tracking it * these buttons are necessary in order to be able to tell if the task is cur... — committed to DegradingGracefully/prototype-simple-time-tracker-client by deleted user 4 years ago

Most upvoted comments

I removed the Svelte Devtools and solved.

+14

jiangfengming on May 21, 2021

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 on Sep 11, 2020

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 on Aug 23, 2020