also looking at this
fix(ios): hand the page the answers native was already sending
#222
18 files
+597
-164
| @@ -20,9 +20,9 @@ const objc = objc_runtime.objc; | ||
| 20 | 20 | /// `{success:true, browser:true}` and made "the bridge worked" and "there is no |
| 21 | 21 | /// bridge" identical to the caller. |
| 22 | 22 | /// |
| 23 | /// `haptic` would have been the obvious first pick and is the wrong one: it is | |
| 24 | /// fire-and-forget, so it exercises no reply path, and Core Haptics is a silent | |
| 25 | /// no-op on the simulator — it would have passed while doing nothing. | |
| 23 | /// `haptic` would have been the obvious first pick and is the wrong one: Core | |
| 24 | /// Haptics is a silent no-op on the simulator, so its `true` says only that | |
| 25 | /// UIKit took the call — it would have passed while doing nothing. | |
| 26 | 26 | pub const A = struct { |
| 27 | 27 | pub const get_device_info = "getDeviceInfo"; |
| 28 | 28 | }; |