Marc Reichelt
03/25/2026, 5:48 PMsetContent 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!Andrei Salavei
03/26/2026, 9:47 AMMarc Reichelt
03/26/2026, 2:20 PMAndrei Salavei
03/26/2026, 4:16 PMMarc Reichelt
03/26/2026, 4:17 PMMarc Reichelt
03/27/2026, 11:22 AMAndrei Salavei
03/27/2026, 1:11 PMMarc Reichelt
03/27/2026, 1:13 PMAndrei Salavei
03/27/2026, 1:17 PMReportUnhandledExceptionHook provides exception and message can be tracked as well as complete and correct crashlog right before the crash.Marc Reichelt
03/27/2026, 1:18 PMAndrei Salavei
03/27/2026, 1:19 PMReportUnhandledExceptionHook with crashlog separately from the crash itself?Marc Reichelt
03/27/2026, 1:20 PMAndrei Salavei
03/27/2026, 1:32 PMMarc Reichelt
03/27/2026, 1:33 PM