jeff
04/16/2024, 10:38 PMwindow.onerror
isn't being triggered, even if I do something like null!!
. I do see an error message in the js console, with a kotlin-js stack trace, but maybe kotlin isn't propagating it all the way up?
Anyone run into this? Any suggestions?David Herman
04/16/2024, 10:54 PMDavid Herman
04/16/2024, 11:07 PMwindow.onerror
listener and added this fake crash:
TextInput(name, onTextChanged = { name = it; error("onTextChanged") })
and that got handled.
Then, in the same page, I added a LaunchedEffect crash:
...
LaunchedEffect(Unit) { error("LaunchedEffect") }
var name by remember { mutableStateOf("") }
TextInput(name, onTextChanged = { name = it; error("onTextChanged") })
...
and in that case, both crashes were uncaught and NOT handled by window.onerror
. I don't know what's going on.David Herman
04/16/2024, 11:09 PMconsole.log
call: https://stackoverflow.com/questions/9216441/intercept-calls-to-console-log-in-chrome
I wonder if you can intercept console.error
messages this way...David Herman
04/16/2024, 11:09 PMjeff
04/16/2024, 11:17 PMCLOVIS
04/17/2024, 7:41 AM