I figured it out... apparently, kotlinx.serialization was hitting the iOS stack size limit (1mb), an...

# ios

[Brian Guertin]

I figured it out... apparently, kotlinx.serialization was hitting the iOS stack size limit (1mb), and increasing the stack size (via linker flags: -Wl,-stack_size,0x800000) solved the issue. Sharing in case anyone else has EXC_BAD_ACCESS issues.

[Nikolay Kasyanov]

Thanks for sharing the workaround! Do you think it’d make sense to report the stack exhaustion issue to kotlinx.serialization?

[Brian Guertin]

https://youtrack.jetbrains.com/issue/KT-50870

[louiscad]

Can the very long logs and stacktraces be removed from the issue and its comments? It makes Chrome for Android freeze each time 😞

[louiscad]

You can attach files instead.

[Paul Woitaschek]

@Brian Guertin
How did this error age? Do you still have the workaround in place? We face a similar issue, only that it’s not even a nested json