Fixed
Status Update
Comments
ra...@google.com <ra...@google.com>
ra...@google.com <ra...@google.com> #2
Thank you for the report. We will try to fix this soon. In the meantime, could you please start the emulator from the console (see the commands below), open the camera app to crash it and attach the output, it might help to figure out what the problem is:
cd /Users/YOUR_USERNAME/Library/Android/sdk/emulator
./emulator -list-avds
./emulator -verbose -avd YOUR_AVD_FROM_PREVIOUS_STEP
if there is a crash report to send, please send it and attach the report id.
ap...@google.com <ap...@google.com> #3
We got a crash report (thanks JP): 872e3b20bc34905b. It says EXC_BAD_INSTRUCTION / 0x00000001
and the console also says "Illegal hardware instruction". I suspect the new MacOS brought a new hypervizor which causes this behavior. Haitao, could you please take a look?
Description
android.arch.work:work-runtime-ktx:1.0.0-alpha06
Version used:
Theme used: N/A
Devices/Android versions reproduced on: All
- Relevant code to trigger the issue.
class SomeWorker: Worker() {
fun doWork() {
val input = inputData.getIntArray("key")
if( input == null || input.isEmpty() ) {
// work
}
}
}
there is a lint warning on "input == null" saying it is always false. This is because the return type is annotated with @NonNull. The javadoc and code clearly say/show that null can be returned.
The same holds true for getBooleanArray(String)
- A screenrecord or screenshots showing the issue (if UI related).
N/A