Remote Debugger breaks onPress on Touchable Components

React Native version: 0.61.2

Steps To Reproduce

1. Enable the remote debugger
2. Tap a TouchableOpacity with onPress and onLongPress parameters
3. Note that onLongPress is fired and not onPress even on short taps
4. Works correctly if not in remote debugging

Describe what you expected to happen:

Upon a quick tap the component onLongPress fires, expected onPress to fire.

Minimal example

import React, { Component } from 'react';
import { Alert, Text, TouchableOpacity, View } from 'react-native';

class ExampleComponent extends Component<Props> {
  public render() {
    return (
      <View>
        <TouchableOpacity
          onPress={() => Alert.alert('Press')}
          onLongPress={() => Alert.alert('Long Press')}>
         <Text>Hello World</Text>
        </TouchableOpacity>
      </View>
    );
  }
}

When in remote debugging onLongPress always fires.

[alexciarlillo]

I believe I ended up tracking this down to an issue with there being a time difference between the host and device. Since the time is off, the calculation for whether it was a short press or long press is broken (or something like that). You can verify this by running adb shell "date" && date to see if the times are off. I think I was usually able to fix this by going into the device settings, disabling automatic time resolution, and then re-enabling it. I think there was also a way to do this via an adb command but can’t recall what it is.

[Jlexyc]

I have 1 second difference that I can’t fix. And app doesn’t trigger onPress. Nice to see that this issue isn’t fixed from Oct 25.