@radhya/mach 2.2.5 → 2.3.2

package/docs/deep-links.md

@@ -95,6 +95,29 @@ When `--output` is not provided, Mach uses `public` if that folder exists; other
 }
 ```
 
+## OAuth and Credential Sharing
+
+When the selected platform includes iOS, interactive setup asks whether to enable **iOS Web Credentials for HTTPS OAuth callbacks**. Enable it when an OAuth flow returns to an HTTPS URL through `expo-web-browser` or a similar browser-based callback. Mach then writes the `webcredentials` section to the Apple App Site Association file and, for Expo, adds `webcredentials:<domain>` to `ios.associatedDomains`.
+
+When the selected platform includes Android, setup also offers **Android Login Credentials for website password and passkey sharing**. Enable it only when the Android app and website intentionally share credentials. Mach adds `delegate_permission/common.get_login_creds` to `assetlinks.json` alongside the normal App Links relation.
+
+Both options are disabled by default. When enabled, they are persisted only as the following explicit opt-ins:
+
+```json
+{
+  "deepLinks": {
+    "ios": {
+      "webCredentials": true
+    },
+    "android": {
+      "loginCredentials": true
+    }
+  }
+}
+```
+
+`mach deeplink setup --yes` does not enable either feature automatically. It preserves an existing setting or keeps the default disabled.
+
 ## Expo Projects
 
 For Expo projects, Mach wires a config plugin that applies:

package/docs/frameworks/expo.md

@@ -145,6 +145,41 @@ Mach applies the resolved value after Expo prebuild, so `app.json` or `app.confi
 
 This updates native build numbers only. Apple also requires the marketing version to increase when a released version train is closed. In Expo projects, that is usually `expo.version` in `app.json` or `app.config.*`.
 
+## iOS app extensions
+
+For Expo CNG projects, declare app extensions in the EAS-compatible Expo field:
+
+```json
+{
+  "expo": {
+    "extra": {
+      "eas": {
+        "build": {
+          "experimental": {
+            "ios": {
+              "appExtensions": [
+                {
+                  "targetName": "ShareExtension",
+                  "bundleIdentifier": "com.example.app.share"
+                }
+              ]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+Mach reads this field before prebuild, resolves a separate saved provisioning
+profile for the main app and each extension, then applies the profiles to the
+generated Xcode targets. If an Expo project commits its native `ios/` directory,
+Mach can also detect extension targets from Xcode. `ios.appExtensions` in
+`mach.config.json` is available as an explicit override.
+
+Single-target Expo projects continue to use the existing single-profile path.
+
 ## Common Commands
 
 ```bash

package/docs/frameworks/react-native.md

@@ -119,6 +119,39 @@ For store builds, upload iOS signing credentials and App Store Connect credentia
 
 `ios.buildNumber: "auto"` allocates the next scoped Dashboard value. An explicit value is used exactly as configured. Mach applies the resolved value to the app and extension targets, then verifies the final IPA before upload.
 
+### iOS app extensions
+
+Mach detects committed Xcode app-extension targets and resolves one provisioning
+profile for each exact bundle identifier. The same compatible Apple signing
+certificate is reused across the targets. Upload a profile for the main app and
+for every extension under the same Mach project.
+
+Automatic Xcode detection is the default. For generated or unusual projects,
+declare the targets explicitly:
+
+```json
+{
+  "ios": {
+    "bundleIdentifier": "com.example.app",
+    "iosScheme": "Example",
+    "appExtensions": [
+      {
+        "targetName": "ShareExtension",
+        "bundleIdentifier": "com.example.app.share"
+      },
+      {
+        "targetName": "CallerDirectoryExtension",
+        "bundleIdentifier": "com.example.app.callerid"
+      }
+    ]
+  }
+}
+```
+
+Mach installs every profile, applies it only to the matching Xcode target, and
+writes all bundle-to-profile mappings to `ExportOptions.plist`. Projects with no
+extensions continue through the original single-profile signing path.
+
 ## Android Notes
 
 Mach runs Gradle from `android/gradlew` when present. Production builds default to `bundleRelease`; internal builds default to `assembleRelease`; development-client style builds default to `assembleDebug`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@radhya/mach",
-  "version": "2.2.5",
+  "version": "2.3.2",
   "description": "Mach CLI: Cloud Build Orchestrator for React Native & Expo",
   "main": "dist/index.js",
   "type": "module",