mark 'force' as optional property of PressEvent object

[Simek]

Summary

Refs:

• https://github.com/facebook/react-native/blob/master/React/Fabric/RCTSurfaceTouchHandler.mm#L93
• https://github.com/facebook/react-native/blob/master/RNTester/js/examples/Pressable/PressableExample.js#L25

According to the current implementation force will be returned only on iOS platform, only on the devices which have a hardware 3D touch capabilities.

Changelog

[General] [Fixed] - mark force as an optional property of the PressEvent object

Test Plan

Go CI!

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	10,721,696	9,912,128

Base commit: 92160f3

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	6,764,616	22
android	hermes	armeabi-v7a	6,426,372	22
android	hermes	x86	7,149,370	24
android	hermes	x86_64	7,039,909	17
android	jsc	arm64-v8a	8,933,111	34
android	jsc	armeabi-v7a	8,587,252	42
android	jsc	x86	8,760,966	22
android	jsc	x86_64	9,337,150	11

Base commit: 92160f3

[elicwhite]

Thanks for working on this. Can you verify at runtime that this key doesn't exist on Android? The code you linked to isn't really definitive. For example, I could imagine Android is currently providing the force key, but it always being 1.

I'd recommend getting the event and console logging the keys on iOS showing that it includes force, and then running the same code on Android and showing that it does not include the key. That's what I'd expect to see in your test plan.

[Simek]

@TheSavior As I were writing earlier this key is not even present on iOS, on the devices without hardware 3D Touch support, so I don't think that screenshots from Android are necessary.

This information was validated earlier, in more extensive tests during the work on the "PressEvent" and help on the "Pressable" React Native website pages.

I have also bring it up to your attention earlier:
facebook/react-native-website#1933 (comment)

iPhone SE 2nd (no force)

iPhone 11 Pro (no force)

iPhone 8 (force)

[elicwhite]

Thanks for those screenshots, that's great and makes it really clear what is happening.

[facebook-github-bot]

@TheSavior has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[facebook-github-bot]

@TheSavior merged this pull request in ad2f98d.