Fixed
Status Update
Comments
ra...@google.com <ra...@google.com>
ap...@google.com <ap...@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.
ga...@gmail.com <ga...@gmail.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
Version used: 2.0.1 and 2.1.0-alpha02
Currently workmanager-runtime has a dependency on androidx.lifecycle:lifecycle-extensions. The only two classes in that artifact are ViewModelProviders and ViewModelStores which both aren't used by WorkManager. It would be great if you could change the dependency to what you actually need, for example androidx.lifecycle:lifecycle-livedata-core or androidx.lifecycle:lifecycle-livedata.