Fixed
Status Update
Comments
cc...@google.com <cc...@google.com> #2
Could you a sample project?
ml...@gmail.com <ml...@gmail.com> #3
This is repo with very basic project
https://github.com/ThinkDeeper/leanback_crash_test
which contains our extension of GuidedStepSupportFragment and two more dummy fragments as its extension.
Steps to reproduce is pretty simple:
from fragment1 navigate to fragment2 (sometimes back to fragment1) using buttons on right pane and then hit hardware back which results in crash mentioned above.
which contains our extension of GuidedStepSupportFragment and two more dummy fragments as its extension.
Steps to reproduce is pretty simple:
from fragment1 navigate to fragment2 (sometimes back to fragment1) using buttons on right pane and then hit hardware back which results in crash mentioned above.
ap...@google.com <ap...@google.com> #4
I ran the project in android studio with 28 and 29 TV emulator, cannot reproduce it.
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
packageName
inMacrobenchmarkScope
public? Devs wouldn't need to defineTARGET_PACKAGE
constant, since it's needed to pass intomeasureRepeated
(the same as we do withdevice
)Also, it can be helpful to add
currentIteration
to 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.