AND-100: Add annotations (blocking calls).

In this case what I say about not losing the original cause of the exception is more clear.

Imagine that the client receives this exception.
How could I distinguish if I should show a "No connection" or a "Something went wrong" toast?
The only way is string matching, and hoping that error messages will be the same across platforms.

Please, pass the original Exception as the cause, and an optional message if you want. But the clients DO need to know the cause of the issue.