Yuke started a roll a few days ago. There were some context menu failures that we're looking into. Thanks!

Basically, what I did is to open context menu by long pressing some url link, and then click on one of the items. The context menu is opened successfully, but clicking on the items failed to execute and hangs there for 30 seconds because one of the idling resources: GREYAppStateTracker is busy, and the detailed error message is as follows: 

"" UserInfo={NSLocalizedDescription=Failed to execute block because the following IdlingResources are busy: ['GREYAppStateTracker'] Busy resource description:
  GREYAppStateTracker : Waiting for gesture recognizer to detect or fail a recently started gesture."

This issue is reproducible in the newest version but it didn't happen in the version associated with commit number: 090aa5fa68d4c422af4ee84912d30bc89a3e8820.

I debugged a little bit and find out that the GREYAppStateTracker is busy because TapAndAHalfRecognizer, a private class, is fired up to detect actions during runtime and tracked by GREYAppStateTracker, but somehow, the recognition process never finishes, and thus GREYAppStateTracker never un-tracks it. By the way, diff shows that there is no major change in file UIGestureRecognizer+GREYAdditions and GREYAppStateTracker, so I suspect that this bug is caused by some timing issues.

Some update: not only the issue can be reproduced consistently, the failure reason is always the same: UITapAndAHalfGestureRecognizer is fired up twice while only shut down once, which results in an inconsistent state.