[Android]timestamp in gesture event different from iOS

[ldn0x7dc]

Two problems:

1. Android is using 'timeStamp' while iOS is using 'timestamp'; (Seems an old issue)
2. Android is using nano seconds while iOS is using milliseconds.(Brought in by this commit)

Those problems force us to check the platform when using the timestamp, which could be avoided.

[satya164]

It would be awesome if you can send a PR by changing both to timeStamp and fix android to use milliseconds.

[christopherdro]

Related #4627

[0rland0]

The timestamp accuracy will be fixed with this pull request #8199
Is anyone working on renaming 'timestamp' to 'timeStamp' in iOS already?

[satya164]

@0rland0 There was a PR, but I don't think it's active. Send a new PR please :)

[0rland0]

Ok I will try to do that.
@ldn0x7dc Would it be possible to upload the code where you used the gesture so I can directly test on that?

[0rland0]

Does this issue really still exist? I just did some debugging on the PanResponderExample which uses touch events. On Android AND iOS I could access the timestamp of the touch event with
e.timeStamp. Calling e.timestamp gave me on both platforms an 'undefined'.
I tested it with setting a breakpoint in different methods in the PanResponderExample e.g. in th _handlePanResponderMove method. So seems to work on both platforms now with the same command.

[ldn0x7dc]

@0rland0
I've just tested with RN 0.28 and on android it's 'timeStamp' while on iOS it's 'timestamp'.
You can check file TouchesHelper, which assign 'timeStamp' to TIMESTAMP_KEY.

My test code snippets:

 onResponderGrant: (evt) => {
        const {timestamp, timeStamp} = evt.nativeEvent;
        console.log('onResponderGrant...' + JSON.stringify({timestamp, timeStamp}));
      },

output:
android: onResponderGrant...{"timeStamp":1305172663942}
iOs: onResponderGrant...{"timestamp":850859171.5499631}

[sharnik]

The naming on Android has been changed to timestamp (iOS style) in this commit: 8aeeb4d

It's already on master.