5211b26903
* update deps * update patches * fix new arch optout * build from source, disable new arch * update to preview.14 * upgrade off of preview to release * fix lockfile lint * update patches * add back expo-location * downgrade reanimated * downgrade pagerview * use expo-file-system/legacy * try and upgrade types/react-dom * fix type of uint8array * rm @types/react resolution from bad rebase * more type errors * fix mock * bump rn-compressor * add patch of https://github.com/bluesky-social/react-native-paste-input/pull/5 * delete NativeDropdown & remove Zeego * `import React` in expo modules * bump cocoapods * rm unused picker lib * add speculative react-native-mmkv patch * revert patch, add temp debug info to error * bring back speculative patch, patch built JS code instead of source * revert patch, just do debugging part * dep update * update resolutions, dynamic-app-icon * bump node version in eas.json * update build instructions * rm atob from docs * Delete react-native-mmkv+2.12.2.patch * bump expo which might include fix * update expo patch version * bump expo patch version * wrong version oops * update expo to latest * update react-native-compressor, rm patch
12 lines
955 B
Markdown
12 lines
955 B
Markdown
# Expo Haptics Patch
|
|
|
|
Whenever we migrated to Expo Haptics, there was a difference between how the previous and new libraries handled the
|
|
Android implementation of an iOS "light" haptic. The previous library used the `Vibration` API solely, which does not
|
|
have any configuration for intensity of vibration. The `Vibration` API has also been deprecated since SDK 26. See:
|
|
https://github.com/mkuczera/react-native-haptic-feedback/blob/master/android/src/main/java/com/mkuczera/vibrateFactory/VibrateWithDuration.java
|
|
|
|
Expo Haptics is using `VibrationManager` API on SDK >= 31. See: https://github.com/expo/expo/blob/main/packages/expo-haptics/android/src/main/java/expo/modules/haptics/HapticsModule.kt#L19
|
|
The timing and intensity of their haptic configurations though differs greatly from the original implementation. This
|
|
patch uses the new `VibrationManager` API to create the same vibration that would have been seen in the deprecated
|
|
`Vibration` API.
|