@radhya/mach 2.2.2 → 2.2.5

package/README.md

@@ -332,13 +332,19 @@ Mach walks you through each step: choosing a bundle ID, picking a distribution t
 
 For iOS development and ad-hoc profiles, Mach also asks which registered devices should be included. After registering the selected devices with Apple, Mach refreshes the provisioning profile so the uploaded profile includes those devices instead of reusing an older cached profile.
 
+The credential type selected in the interactive picker is authoritative. It is not replaced by the selected build profile's `distribution` field. For non-interactive or custom-profile setup, use an explicit signing override:
+
+```bash
+mach credentials:setup --platform ios --profile debug --credential-type development
+```
+
 ### Apple Developer Team Selection
 
 For iOS credentials, Mach asks for your Apple ID and then lists the Apple Developer teams connected to that account through `@expo/apple-utils`. If the account has multiple teams, choose the team to use for signing; if Apple cannot return the list, Mach falls back to manual Team ID entry. Fastlane is still used later for the certificate/profile sync, but it is no longer required just to display the team picker.
 
 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.
 
-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.
+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. Mach first tries the encrypted password stored with the credential and the legacy empty-password format; it prompts only when an older or externally uploaded P12 is protected but has no saved password. It never revokes a certificate automatically.
 
 ### Multiple Bundle IDs