IssueTracker

As a workaround, you can use the following instead of startActivityAndWait(), which is what we previously used, though it does have the downside of taking much longer to finish, 5 seconds in most cases:

    context.startActivity(intent)
    check(device.wait(
        Until.hasObject(By.pkg(packageName).depth(0)),
        30_000
    )) { "package did not display in 30 seconds!" }

Now that we have a more robust implementation of launch completion detection within macrobench, we should be able to switch back to context.startActivity() in startActivityAndWait, without having to wait so long for UiAutomator to detect the package.

Note if device.wait doesn't work reliably, or the delay is too long, you can either use Thread.sleep, or copy the macrobench waiting impl.