-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Throwing exceptions inside coroutines generates warnings on Android 9 devices #822
Comments
We are happy to use an official API, could you please point to the legal ways to handle an exception? |
To be honest, I have no solution. I think best bet is to Create ticket about this on Google's tracker and see what they think about it. |
cc @adamp ☝️ |
The issue tracker link above is the right place to propagate this question for now. In the meantime iirc you should only see the warning once during the reflection lookup, subsequent invocations should be quiet. I can try to take a look in some more detail next week. |
…Pie runtime ensures that uncaught exception is always logged Fixes #822
…Pie runtime ensures that uncaught exception is always logged Fixes #822
@qwwdfsad Thanks for the fix. Is this available in a release? |
Running this code on Android 9 device/emulator:
will result in a
Accessing hidden method Ljava/lang/Thread;->getUncaughtExceptionPreHandler()Ljava/lang/Thread$UncaughtExceptionHandler; (light greylist, reflection)
warning printed into Logcat.Android 9 includes crackdown on developers using non-public stuff via reflection, and looks like coroutines got caught in this.
The text was updated successfully, but these errors were encountered: