@craft-native/ios 0.0.90 → 0.0.92

package/README.md

@@ -143,6 +143,11 @@ Edit `craft.config.json` in your iOS project:
 }
 ```
 
+When push notifications are enabled, generated Debug builds use the APNs
+development environment and Release builds use the production environment.
+The generated entitlements select the correct value from the active Xcode
+build configuration automatically.
+
 ## JavaScript Bridge
 
 Once Craft is initialized, the `window.craft` object is available:
@@ -154,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');
+// 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
-window.craft.startListening();
-window.craft.stopListening();
+// 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 */ });
@@ -586,6 +594,14 @@ Add to your Info.plist as needed:
 <string>This app accesses your calendar.</string>
 ```
 
+## Runtime Validation
+
+The Zig-native bridge rejects malformed values and overlapping interactive
+requests that the legacy Swift dispatcher could silently truncate, coerce, or
+abandon. See the
+[mobile runtime compatibility guide](../../docs/api/mobile/runtime-compatibility.md)
+for the affected input classes and migration guidance.
+
 ## Development Mode
 
 For hot-reload during development:
@@ -601,6 +617,30 @@ craft ios open
 
 The app will load from your dev server instead of bundled HTML.
 
+## Template compiler gate
+
+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 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.
+
 ## Publishing
 
 Build for App Store:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@craft-native/ios",
-  "version": "0.0.90",
+  "version": "0.0.92",
   "homepage": "https://github.com/craft-native/craft/tree/main/packages/ios#readme",
   "repository": {
     "type": "git",
@@ -23,7 +23,8 @@
   },
   "scripts": {
     "build": "bun build.ts",
-    "dev": "bun --watch src/cli.ts"
+    "dev": "bun --watch src/cli.ts",
+    "test:templates": "bun scripts/compile-templates.ts"
   },
   "files": [
     "dist",