expo-invoke 1.0.0 → 1.1.0

package/README.md

@@ -10,6 +10,9 @@ The complete native-surface-to-JS bridge for Expo. Define one intent in `app.jso
 
 - [Requirements](#requirements)
 - [Installation](#installation)
+  - [Local build](#local-build)
+  - [EAS Build (cloud)](#eas-build-cloud)
+  - [EAS Build local](#eas-build-local)
 - [Quick Start](#quick-start)
 - [useInvoke() — Full API](#useinvoke--full-api)
 - [Hooks](#hooks)
@@ -59,14 +62,69 @@ The complete native-surface-to-JS bridge for Expo. Define one intent in `app.jso
 npx expo install expo-invoke
 ```
 
-Then rebuild your native app:
+Then rebuild your native app. Choose the workflow that fits your project:
+
+### Local build
 
 ```bash
-npx expo prebuild
-npx expo run:ios
+npx expo prebuild          # generates native code from your app.json
+npx expo run:ios           # build + run on simulator or device
 npx expo run:android
 ```
 
+### EAS Build (cloud)
+
+expo-invoke works fully with [EAS Build](https://docs.expo.dev/build/introduction/). EAS automatically runs `expo prebuild` before each build, so the config plugin generates all Swift and Kotlin code in the cloud — no local Xcode or Android Studio required.
+
+```bash
+# Install EAS CLI
+npm install -g eas-cli
+
+# Configure your project (first time only)
+eas build:configure
+
+# Build for both platforms
+eas build --platform all
+
+# Or build for a specific platform
+eas build --platform ios
+eas build --platform android
+```
+
+A minimal `eas.json` to get started:
+
+```json
+{
+  "cli": {
+    "version": ">= 10.0.0"
+  },
+  "build": {
+    "development": {
+      "developmentClient": true,
+      "distribution": "internal"
+    },
+    "preview": {
+      "distribution": "internal"
+    },
+    "production": {}
+  },
+  "submit": {
+    "production": {}
+  }
+}
+```
+
+> **Development builds:** For the fastest iteration loop during development, use `eas build --profile development` to create a [development build](https://docs.expo.dev/develop/development-builds/introduction/) — a custom Expo Go that includes your native modules including expo-invoke.
+
+### EAS Build local
+
+Run the EAS build pipeline locally (requires Xcode / Android Studio):
+
+```bash
+eas build --platform ios --local
+eas build --platform android --local
+```
+
 ---
 
 ## Quick Start

package/app.plugin.js

@@ -0,0 +1,2 @@
+const mod = require('./build/plugin/src/withInvoke');
+module.exports = mod.default ?? mod;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "expo-invoke",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "The complete native-surface-to-JS bridge for Expo. One intent config → Siri, Google Assistant, home screen widgets, Dynamic Island, app icon menus, notification actions, NFC, QR, deep links and more — all through a single useInvoke() hook.",
   "main": "build/src/index.js",
   "module": "build/src/index.js",
@@ -10,12 +10,15 @@
       "require": "./build/src/index.js",
       "import": "./build/src/index.js",
       "types": "./build/src/index.d.ts"
-    }
+    },
+    "./app.plugin": "./app.plugin.js",
+    "./app.plugin.js": "./app.plugin.js"
   },
   "expo": {
     "plugin": "./build/plugin/src/withInvoke"
   },
   "files": [
+    "app.plugin.js",
     "build",
     "ios",
     "android/src",

package/MIGRATION.md

@@ -1,125 +0,0 @@
-# Migration Guide
-
-## From `expo-errands-assistant`
-
-The `expo-errands-assistant` local module was hardcoded for a single Siri action with no parameters, no Android support, and no reusability. `expo-invoke` replaces it entirely.
-
-### Step 1 — Replace the import
-
-```diff
-- import { useErrandsAssistant } from '../modules/expo-errands-assistant';
-+ import { useInvokeInit, useInvoke } from 'expo-invoke';
-```
-
-### Step 2 — Replace the root-level init
-
-```diff
-// app/_layout.tsx
-- useErrandsAssistant(); // old
-+ useInvokeInit();       // new — same cold/warm start behaviour
-```
-
-### Step 3 — Replace the intent listener
-
-```diff
-// Before
-- const { action } = useErrandsAssistant();
-- if (action === 'CreateErrand') { router.push('/create'); }
-
-// After
-+ const { intent } = useInvoke({ intentId: 'create_errand' });
-+ useEffect(() => { if (intent) router.push('/create'); }, [intent]);
-```
-
-### Step 4 — Move the native intent to app.json
-
-Delete the hardcoded Swift intent file. The config plugin generates it:
-
-```json
-// app.json
-{
-  "plugins": [["expo-invoke", {
-    "intents": [{
-      "id": "create_errand",
-      "title": "Create an Errand",
-      "phrases": ["Create an errand in ${applicationName}"]
-    }]
-  }]]
-}
-```
-
----
-
-## From `react-native-siri-shortcut`
-
-### Install expo-invoke
-
-```bash
-npx expo install expo-invoke
-npx expo uninstall react-native-siri-shortcut
-```
-
-### Replace donation calls
-
-```diff
-- import SiriShortcuts from 'react-native-siri-shortcut';
-- SiriShortcuts.donateShortcut({ identifier: 'create', title: 'Create', userInfo: {} });
-
-+ import { useDonation } from 'expo-invoke';
-+ const { donate } = useDonation();
-+ donate({ intentId: 'create_errand', title: 'Create an Errand' });
-```
-
-### Replace the shortcut listener
-
-```diff
-- import { ShortcutListener } from 'react-native-siri-shortcut';
-- <ShortcutListener onShortcutReceived={({ identifier }) => { ... }} />
-
-+ import { useInvoke } from 'expo-invoke';
-+ const { intent } = useInvoke();
-+ // intent.intentId === 'create_errand' when fired
-```
-
----
-
-## From `expo-siri-shortcut`
-
-### Install expo-invoke
-
-```bash
-npx expo install expo-invoke
-npx expo uninstall expo-siri-shortcut
-```
-
-### Replace the shortcut button
-
-```diff
-- import { SiriShortcutButton } from 'expo-siri-shortcut';
-- <SiriShortcutButton shortcut={{ activityType: 'create', title: 'Create' }} />
-
-+ import { AddToSiriButton } from 'expo-invoke';
-+ <AddToSiriButton intentId="create_errand" />
-```
-
-### Replace the activity listener
-
-The old `expo-siri-shortcut` used `NSUserActivity`. `expo-invoke` uses the modern App Intents API. Replace the app delegate hook with `useInvokeInit()` and receive via `useInvoke()`.
-
----
-
-## Key Behavioural Differences
-
-| Behaviour | Old packages | expo-invoke |
-|---|---|---|
-| iOS API | SiriKit (deprecated) | App Intents (iOS 16+) |
-| Android | None | Google App Actions BII |
-| Multi-intent | No | Yes — unlimited |
-| Parameters | None / manual | 8 typed parameter types |
-| Widget bridge | No | Yes — WidgetKit + AppWidgetProvider |
-| Dynamic Island | No | Yes |
-| Cold start TTL | None | 30s default, configurable |
-| Intent deduplication | No | Yes (2s window) |
-| Source attribution | No | 20 surfaces |
-| Testing utilities | No | mockInvoke, simulateColdStart |
-| CLI | No | validate, generate, test |

package/SECURITY.md

@@ -1,35 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-| Version | Supported |
-|---|---|
-| 1.x (current) | ✓ |
-
-## Reporting a Vulnerability
-
-**Do not open a public GitHub issue for security vulnerabilities.**
-
-Email: security@smarthivelabs.dev
-
-Please include:
-- Description of the vulnerability
-- Steps to reproduce
-- Affected versions
-- Potential impact
-
-We will acknowledge your report within 48 hours and aim to release a fix within 14 days for critical issues.
-
-## Security Considerations for Users
-
-### Intent ID exposure
-Intent IDs defined in `app.json` are visible in the compiled binary. Do not use intent IDs as security boundaries. Treat them as public routing tokens.
-
-### Deep link → intent mapping
-Deep links that map to intents (`deepLinkPatterns` in config) process user-supplied URLs. Validate any parameters extracted from deep links before acting on them in your app.
-
-### Widget / shared storage
-`useWidgetData()` stores values in a shared App Group container (iOS) or SharedPreferences (Android). Do not store sensitive data (tokens, PII) using this API.
-
-### Notification action intents
-Notification action buttons trigger intents based on category IDs in the push payload. Ensure your push notification server validates recipient identity before sending notifications with action categories.