Hi! We’re using Compose Multiplatform 1.10.2 and o...
# compose-ios
m
Hi! We’re using Compose Multiplatform 1.10.2 and observe some crashes on iOS where we can’t get much out of the stacktrace. In the trace we can see that
setContent
is calling
postponeInvalidation
, which calls
trace
, which ultimately calls our code in
setContent
, but crashes. But we can’t see the actual cause of the crash. Even more weird, the code seems to fail the first time, but works on the 2nd and 3rd attempt running it. Is anyone observing a similar issue? And: what best practices are you using to capture the actual exceptions from within
setContent
on iOS? Thank you!
a
Hi ! It sounds like the issue which we fixed recently. The stacktrace will help to understand your problem.
👀 1
m
Thanks, we’ll look into it! What do you mean by ‘the stacktrace will help to understand your problem’? Do you mean that moving to a new CMP version will allow us to see the actual stacktrace, or do you mean that we should already understand the problem using the current stacktrace we have now with 1.10.2?
a
I mean: could you please send me the stack trace of the crash?
m
I’m on the run now, but will provide it likely tomorrow 👍
👍 1
@Andrei Salavei Here is the crash (anonymized)
a
Thank you. Do you have the exception message as well?
m
That's exactly why I'm asking: we set up a crash handler and called the setUnhandledExceptionHook, but this is all we get. We're currently checking if our crash handler is not set up correctly for some reason, but for some other Kotlin crashes we do get the full info, including the name of the Kotlin exception.
a
The
ReportUnhandledExceptionHook
provides exception and message can be tracked as well as complete and correct crashlog right before the crash.
m
That's what we're using. We still don't see the inner details of this crash in prod. Any other hints or tips?
a
Do you track Throwable from the
ReportUnhandledExceptionHook
with crashlog separately from the crash itself?
m
yes. And for other crashes it works.
a
No idea, tbh. Could you try the latest version of CMP? If it doesn't help please file an issue in our YouTrack.
m
Ok! We'll make sure to doublecheck everything on our side, and try out the latest CMP version as well. If we can't fix it we'll file an issue 👍