You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requirement:
For Android, many third-party SDKs are integrated into the project development, and they also use OKHTTP internally. When there are some error message Toasts, users will give us feedback。
For example: Too many follow up requests: 21, HTTP 404, etc
Interceptor is designed for the new okhttpclient instance.
However, due to their internally initialized okhttpclient, we are unable to add an Interceptor or determine which SDK it belongs to based on Toast prompts. Therefore, there is a requirement for a global static error callback
Like RxJava: RxJavaPlugins.setErrorHandler(throwable -> { });
Or is there currently a solution?
Thanks。
The text was updated successfully, but these errors were encountered:
But I'm not sure we want to take this control away from SDK developers. Maybe it's a secure call and another library might snoop on those.
Yes, there may be some kind of concern.
It is reasonable to provide a unified callback to expose the content of the error and the host where the error occurred, without returning the complete request.
Requirement:
For Android, many third-party SDKs are integrated into the project development, and they also use OKHTTP internally. When there are some error message Toasts, users will give us feedback。
For example: Too many follow up requests: 21, HTTP 404, etc
Interceptor is designed for the new okhttpclient instance.
However, due to their internally initialized okhttpclient, we are unable to add an Interceptor or determine which SDK it belongs to based on Toast prompts. Therefore, there is a requirement for a global static error callback
Like RxJava:
RxJavaPlugins.setErrorHandler(throwable -> { });
Or is there currently a solution?
Thanks。
The text was updated successfully, but these errors were encountered: