Hi everyone, have any of you experienced a high delay when throwing an exception using compose multi...

# compose-ios

[Javier RG]

Hi everyone, have any of you experienced a high delay when throwing an exception using compose multiplatform on iOS target?

[Javier RG]

To give some context, I have created a backend with ktor and I have some custom exceptions, although the same thing happens with a 404 for example. If a call to an endpoint fails, for whatever reason, I display a generic error bottom sheet.

This works perfectly on Android, for example, in case of receiving a 404, Ktor returns a ClientRequestException and the bottom sheet appears instantly.

But in iOS it is different, in the same case, from the time the exception is thrown until the bottom sheet is displayed, it can take up to 20 seconds.

[Javier RG]

I see that the request has failed in the firebase performance logs, but I don't see the stack trace in the logs until after several seconds (which is when the bottom sheet appears).

[Javier RG]

I'm using coroutines + runCatching approach, in case it helps

[Gerardo Rodriguez]

I think I saw that as well. I thought it was the timeout of making the request

[Javier RG]

I opened a YouTrack issue for this and they're able to reproduce it, so I guess it's a common issue

[Gerardo Rodriguez]

Great @Javier RG

[Javier RG]

BTW, I've noticed that it only happens when running the app in a simulator, so I guess physical devices are safe

[Tepes Lucian Victor]

I've also experienced this and though my setup was wrong. After the first exception everything gets back to normal.