@radhya/mach 2.2.0 → 2.2.2
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.
- package/README.md +2 -0
- package/dist/chunk-EOCEKS22.js +441 -0
- package/dist/{credentials-BMX37TIA.js → credentials-EFMCWAD4.js} +1 -1
- package/dist/index.js +84 -84
- package/package.json +1 -1
- package/dist/chunk-6OEZPCKM.js +0 -441
package/README.md
CHANGED
|
@@ -338,6 +338,8 @@ For iOS credentials, Mach asks for your Apple ID and then lists the Apple Develo
|
|
|
338
338
|
|
|
339
339
|
Mach saves the selected Team ID to the Dashboard for credential storage. It also asks whether to write the Team ID into `mach.config.json` for the selected profile. Accepting the prompt writes only `submit.<profile>.ios.appleTeamId`; production defaults to yes, while development and staging default to no so local config is not cluttered unless you want profile-specific signing.
|
|
340
340
|
|
|
341
|
+
If Apple has reached its active Distribution-certificate limit, Mach looks for compatible Apple Distribution `.p12` certificates already stored in the Mach projects you administer. You can explicitly select one by project and expiry date. Mach downloads it only for the current setup, creates a new profile for the current bundle ID, and stores the resulting credentials in the target project. It never revokes a certificate automatically.
|
|
342
|
+
|
|
341
343
|
### Multiple Bundle IDs
|
|
342
344
|
|
|
343
345
|
One project can have multiple bundle identifiers (e.g. `com.example.app`, `com.example.app.staging`, `com.example.app.dev`). Each bundle ID has its own independent set of credentials per distribution type. Select or add a bundle ID at the start of `mach credentials` — or skip the prompt with the `--bundle-id` flag for CI:
|