Does anyone else have difficulty to see crash logs when deve

Question

Does anyone else have difficulty to see crash logs when developing for and on mac Whenever there is a runtime exception the app just crashes and disappears without anything in the logs I ve tried to set default uncaught exception handlers but those don t seem to trigger

olonho · Answer

could you please elaborate what did you try also did you check if JVM crashed i e if files like hs err pidXXXX log are present in the working dir

kevindmoore · Answer

Did you try the Console app

remco · Answer

Yeah also doesn t work I think I m found a repro that s relatively simple

remco · Answer

I don t see any JVM crash logs in the working dir

remco · Answer

One example I have is that I have this ```val state by produceState lt State gt null value = loadState ``` `loadState ` is a suspending function it throws any exception all my compose windows are destroyed JVM actually doesn t seem to crash because the process is still alive

remco · Answer

And there are zero logs to indicate what the crash was

remco · Answer

If I wrap it like this I do see the exception in the logs ```val state by produceState lt State gt null try value = loadState service github playApi catch e Exception e printStackTrace ```

kevindmoore · Answer

Since it is a Mac app you can always run it from the command line Go to Applications lt app name gt Contents MacOS and run it from there

remco · Answer

I m not running the native distribution btw

remco · Answer

It is just from Intellij

remco · Answer

I see all the other logs

kevindmoore · Answer

Oh It doesn t show from Intellij Strange Are you using println or some sort of logging util

remco · Answer

Using println

olonho · Answer

exception handling in composable functions is generally may be somewhat fragile < jim> what is recommended way to catch all exceptions in such cases

jim · Answer

No exception handling is non existent in Compose at the moment that is an exception thrown across composable functions has entirely undefined results We do intend to fix this in a future version of Compose but it is much much harder than it would appear at first glance The only advice at the moment is to avoid throwing exceptions from within composable functions or catch them before they cross a composable function s scope

jim · Answer

With that said I wouldn t have expected us to be swallowing exceptions Do you have a minimal repro