@craft-native/ios 0.0.91 → 0.0.94

package/README.md

@@ -159,14 +159,17 @@ window.addEventListener('craftReady', (e) => {
   console.log('Capabilities:', e.detail.capabilities);
 });
 
-// Haptic feedback
-window.craft.haptic('light');   // light, medium, heavy
-window.craft.haptic('success'); // success, warning, error
-window.craft.haptic('selection');
-
-// Speech recognition
-window.craft.startListening();
-window.craft.stopListening();
+// Haptic feedback. Resolves true, and rejects with CAPABILITY_DISABLED when
+// enableHaptics is off.
+await window.craft.haptic('light');   // light, medium, heavy
+await window.craft.haptic('success'); // success, warning, error
+await window.craft.haptic('selection');
+
+// Speech recognition. startListening resolves true once the request is
+// taken; whether listening actually began arrives as the events below
+// (craftSpeechError for a declined prompt or no recognizer).
+await window.craft.startListening();
+await window.craft.stopListening();
 
 // Listen for speech events
 window.addEventListener('craftSpeechStart', () => { /* recording started */ });
@@ -620,10 +623,21 @@ On macOS with Xcode and XcodeGen installed, run `bun run test:templates` from
 `packages/ios`. It generates a minimal app, a capability-heavy iOS app, and the
 same capability-heavy app with a Watch companion. It builds iOS, Live Activity,
 Watch extension, and Watch app targets against device SDKs with code signing
-disabled. The Watch-enabled iOS target is not built because Xcode requires a
-watchOS runtime to resolve its embedded-app graph; its identical Swift source
-is built in the sibling capability fixture. This checks the actual generated
-Swift and Xcode projects; `bun test` checks the builder's behavior separately.
+disabled.
+
+The Watch-enabled app is also built the way Xcode builds it for a person, with
+the Watch app embedded. The script checks that the bundle carries
+`Watch/<App>Watch.app` with `WKWatchKitApp` and its WatchKit extension, then
+installs the app on an iOS simulator. That needs a watchOS simulator runtime
+matching the selected Xcode (`xcodebuild -downloadPlatform watchOS`), and the
+script fails without one rather than skipping.
+
+Finally, a push-enabled app is built for the simulator in Debug and Release with
+ad-hoc signing. The script reads the `aps-environment` Xcode actually signed
+into each: `development` for Debug, `production` for Release.
+
+This checks the actual generated Swift and Xcode projects; `bun test` checks the
+builder's behavior separately.
 Temporary projects are removed after the run. Pass `--keep` to retain them for
 debugging.