Fixed
Status Update
No update yet.
Comments
cc...@google.com
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
ml...@gmail.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
Description
Component used: androidx.benchmark:benchmark-macro
Version used: 1.1.0-alpha12
Since most of the UI interactions will happen in target package, developers need to specify it when manipulating the UI, e.g.:
device.findObject(By.res(TARGET_PACKAGE, "some_id"))Can we make the
packageNameinMacrobenchmarkScopepublic? Devs wouldn't need to defineTARGET_PACKAGEconstant, since it's needed to pass intomeasureRepeated(the same as we do withdevice)Also, it can be helpful to add
currentIterationto the scope, so it's as well accessible when running the test. Let's say for example, each iteration opening different item from a list. Or simply logging which iteration is running.This can be done manually, but again, the information is there, just to add it to the scope.