I am seeking for advice, best practice to handle e...

# multiplatform

[niqo01]

I am seeking for advice, best practice to handle exceptions where the logic to handle exceptions is in common code and the exceptions are thrown by SDKs implemented in each platforms. I would like to have logic like if an exception is of one type then do X otherwise do Y.

[Sam]

Can you declare your exceptions in common code? Then your platform code can just throw them as needed.

[niqo01]

Is the practice of declaring exception in common code and mapping the SDK generated ones into those the recommended approach? I should look into what ktor is doing

[Sam]

Maybe a more concrete example of a problem you're trying to solve would be helpful.

[niqo01]

I have several use cases.
One of them is a presenter in common code which execute various tasks with one of them being an API call.
On the jvm various exception can be returned extending <http://java.io|java.io>.IOException or not. I could catch the specific IOException related to no connectivity and ask the user to check their network settings, I could also catch the IOException related to network issues and ask the user to retry and just re-throw if this is not an IOException.

Another use case is about the Firestore database which offers and SDK for each platform. Requesting cache data which does not exist return FirebaseException with a specific property which I would like to capture and run different logic based on the cause.

I actually don't see any other ways than creating my own common code exception and map each platform one to the common one.

[Gabriel Feo]

Yeah, I think you'll have to map an actual typealias to the java.io.IOException