Status Update
Comments
gg...@google.com <gg...@google.com> #2
The attached Build Scan log shows that the emulator process crashed unexpectedly. Could you rerun your task with --info
and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
to get more information about the emualtor process logs?
al...@gmail.com <al...@gmail.com> #4
No idea why the scan does not contain log information, here you are:
ra...@google.com <ra...@google.com>
pa...@google.com <pa...@google.com>
tn...@google.com <tn...@google.com> #5
The link in --info
and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
, the emulator process output its kernel logging to stdout. Do you see any stacktrace or segfault in the log?
an...@google.com <an...@google.com> #6
That's strange, the repo and the build is public... But I attached the logs as file
Description
kotlin always let ()->Unit as Runnable. But android Handler cannot removeCallbacks. Ex:
Above code will be compiled into:
The ()->Unit function has be wrapped by diff lambda, it's not same one. So, the android Handler can't removeCallback.
We have to replace with Runnable statement.
Could you please add some warning message just like SharedPreferences' commit() to removeCallback when using kotlin?