also looking at this
fix(ios): hand the page the answers native was already sending
#222
18 files
+597
-164
| @@ -2,6 +2,13 @@ | ||
| 2 | 2 | |
| 3 | 3 | Provide tactile feedback through device vibrations. |
| 4 | 4 | |
| 5 | Haptics are feedback, so these methods never stop a flow for a capability the | |
| 6 | app left off. On iOS, with `enableHaptics` off in `craft.config.json`, they | |
| 7 | resolve without playing anything, the way the web fallback does on a device | |
| 8 | with no vibration motor. They reject only when the native call itself fails. | |
| 9 | The raw `window.craft.haptic()` is different: it rejects with | |
| 10 | `CAPABILITY_DISABLED`, for code that needs to know. | |
| 11 | ||
| 5 | 12 | ## Import |
| 6 | 13 | |
| 7 | 14 | ```typescript |