Skip to content

Exception handling and transport of exceptions #213

Open
@joseffilzmaier

Description

Hey there, thank you for the library, it's looking really neat!

Client target: Android
Server target: JVM

I am using the default RPC implementation (i think it's called kRPC) and have have a few remarks/questions regarding exceptions/error handling:
Right now, if i make a request from the client and the server throws an exception, the whole whole exception, stacktrace inclusive, is being transferred to the client.

I have a few issues with this approach:

  • I would like to not send the whole stack trace if an exception occurs. Is there any way currently or planned so that i can customize what happens in case of an exception?
  • The exception handling client side does not work as expected on my end: If i wrap the suspending function call with a try/catch i cannot catch it - It still crashes my whole app. I am currently not sure where the exception is thrown, but i believe it to be in some kind of background coroutine that has no Exception Handler set. It would be nice if i would simply be able to catch the exception client side somehow.

Are there any plans on improving remote exception handling, or am i missing some information here?

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions