Potential flakiness issue with detox "should scroll for a small amount in direction" - travis failed

[talkol]

Travis build failed without any change:
https://travis-ci.org/wix/detox/builds/185523378

The test that failed is should scroll for a small amount in direction

This is a potential flakiness issue that we should take very seriously

1)  "after each" hook for "should scroll for a small amount in direction":
     Error: Assertion 'assertWithMatcher: matcherForSufficientlyVisible(>=0.750000)' failed.
Element matcher: ((respondsToSelector(isAccessibilityElement) && isAccessibilityElement) && accessibilityLabel("Text4"))
Complete Error: Error Domain=com.google.earlgrey.ElementInteractionErrorDomain Code=2 "Assertion with matcher 'matcherForSufficientlyVisible(>=0.750000)' failed: UI element '<RCTText: 0x7fff44c6fbf0; reactTag: 49; text: Text4 frame = (10 160; 392 30); opaque = NO; layer = <CALayer: 0x600000429520>>' failed to match matcherForSufficientlyVisible(>=0.750000)" UserInfo={NSLocalizedDescription=Assertion with matcher 'matcherForSufficientlyVisible(>=0.750000)' failed: UI element '<RCTText: 0x7fff44c6fbf0; reactTag: 49; text: Text4 frame = (10 160; 392 30); opaque = NO; layer = <CALayer: 0x600000429520>>' failed to match matcherForSufficientlyVisible(>=0.750000)}
      at handleAction (node_modules/detox/lib/websocket.js:74:15)
      at WebSocket.<anonymous> (node_modules/detox/lib/websocket.js:36:1)
      at Receiver.ontext (node_modules/ws/lib/WebSocket.js:841:10)
      at node_modules/ws/lib/Receiver.js:536:18
      at node_modules/ws/lib/Receiver.js:368:7
      at node_modules/ws/lib/PerMessageDeflate.js:249:5
      at afterWrite (_stream_writable.js:388:3)
      at onwrite (_stream_writable.js:379:7)
      at WritableState.onwrite (_stream_writable.js:90:5)
      at afterTransform (_stream_transform.js:79:3)
      at TransformState.afterTransform (_stream_transform.js:54:12)
      at Zlib.callback (zlib.js:624:5)

[LeoNatan]

So it seems both scrolling and swiping is affected by this flakiness. We saw with @DanielZlotin that sometimes the swipe to refresh at least once failed to actually reach the threshold of refreshing (but it does most of the time). I think this is an issue with Earl Grey in general.

[LeoNatan]

No longer an issue.