I have a custom content provider in my Android app that works reasonably well. I expect other apps to also access my content provider. I would like some clean way to communicate exceptions and errors, but as far as I can tell the Android content provider framework doesn't provide any way to propagate exceptions across processes.
How should I indicate an exception state to my caller? Do I have to somehow encode it into my returned data and rely on clients to check for it? Is there any alternative? If encoding into the ordinary return data is it, what's the best way? (I can see a number of alternatives for the Cursor returned by a query call, but what about the Uri returned by insert, or the int returned by update or delete?)
There is a short list of RuntimeException subclasses which, if thrown in the provider, will be re-thrown in a client app. These include:
IllegalStateExceptionIllegalArgumentExceptionNullPointerExceptionSecurityExceptionBadParcelableException
A more recent update to the Parcel.writeException documentation added
UnsupportedOperationExceptionNetworkOnMainThreadException
Source: Creating Content Providers mentions IAE and NPE; I guessed that the others would work based on the Javadoc for Parcel.writeException.
The client app will only get the detail message, not a stack trace or the cause stack. For exceptional state which can be encoded into a String (the detail message), this is a reasonable choice.
I'm still interested in other solutions, too.
来源：https://stackoverflow.com/questions/11976611/dealing-with-cross-process-exceptions-in-android-custom-content-provider