@radhya/mach 2.6.4 → 2.6.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +1 -1
  2. package/dist/index.js +119 -117
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -341,7 +341,7 @@ mach deeplink setup \
341
341
  --output public
342
342
  ```
343
343
 
344
- `setup` writes compact `deepLinks` settings into `mach.config.json`, generates Apple AASA and Android `assetlinks.json` files, wires an Expo config plugin for Expo projects, and safely patches Flutter's Android manifest plus iOS entitlements/URL scheme. Re-running it is idempotent. The interactive flow can also enable iOS Web Credentials for HTTPS OAuth callbacks and Android Login Credentials for website password and passkey sharing; both remain disabled by default. For Expo apps, Mach prefers `@radhya/mach/expo-plugin`; interactive setup offers to install `@radhya/mach` locally, and `--yes` or `--install-plugin` installs it automatically. Use `--no-install-plugin` to skip package installation; if the package is missing, Mach generates a local `./plugins/withMachDeepLinks` fallback. See [Deep Links](docs/deep-links.md).
344
+ `setup` writes compact `deepLinks` settings into `mach.config.json`, generates Apple AASA and Android `assetlinks.json` files, wires an Expo config plugin for Expo projects, and safely patches Flutter's Android manifest plus iOS entitlements/URL scheme. When the project is linked and has a Mach-managed Android keystore, setup reads its public SHA-256 signing fingerprint automatically; the temporary keystore file is removed immediately. It then offers an optional Google Play App Signing SHA-256 field, defaulting to No. The field accepts comma-separated fingerprints and `assetlinks.json` supports more than one, so debug, direct-distribution, and Google Play builds can coexist. Developers can also add the Google Play value later with a repeatable `--android-fingerprint` flag or `deepLinks.android.sha256CertFingerprints`; it must remain the Play certificate rather than the upload-key certificate. Re-running setup is idempotent. The interactive flow can also enable iOS Web Credentials for HTTPS OAuth callbacks and Android Login Credentials for website password and passkey sharing; both remain disabled by default. For Expo apps, Mach prefers `@radhya/mach/expo-plugin`; interactive setup offers to install `@radhya/mach` locally, and `--yes` or `--install-plugin` installs it automatically. Use `--no-install-plugin` to skip package installation; if the package is missing, Mach generates a local `./plugins/withMachDeepLinks` fallback. See [Deep Links](docs/deep-links.md).
345
345
 
346
346
  ## Local Device Agent
347
347