You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `release-react` command is a React Native-specific version of the "vanilla" [`release`](#releasing-app-updates) command, which supports all of the same parameters (e.g. `--mandatory`, `--description`), yet simplifies the process of releasing updates by performing the following additional behavior:
@@ -549,6 +552,24 @@ Private key path which is used for code signing.
549
552
550
553
_NOTE: This parameter can be set using either --privateKeyPath or -k_
551
554
555
+
#### Xcode project file parameter
556
+
557
+
Path to the Xcode project or project.pbxproj file.
558
+
559
+
_NOTE: This parameter can be set using either --xcodeProjectFile or -xp_
560
+
561
+
#### Xcode target name parameter
562
+
563
+
Name of target (PBXNativeTarget) which specifies the binary version you want to target this release at (iOS only).
564
+
565
+
_NOTE: This parameter can be set using either --xcodeTargetName or -xt_
566
+
567
+
#### Build configuration name parameter
568
+
569
+
Name of build configuration which specifies the binary version you want to target this release at. For example, 'Debug' or 'Release' (iOS only).
570
+
571
+
_NOTE: This parameter can be set using either --buildConfigurationName or -c_
572
+
552
573
## Debugging CodePush Integration
553
574
554
575
Once you've released an update, React Native plugin has been integrated into your app, it can be helpful to diagnose how the plugin is behaving, especially if you run into an issue and want to understand why. In order to debug the CodePush update discovery experience, you can run the following command in order to easily view the diagnostic logs produced by the CodePush plugin within your app:
@@ -914,9 +907,13 @@ function getReactNativeProjectAppVersion(command: cli.IReleaseReactCommand, proj
914
907
log(`Using the target binary version value "${parsedPlist.CFBundleShortVersionString}" from "${resolvedPlistFile}".\n`);
915
908
returnQ(parsedPlist.CFBundleShortVersionString);
916
909
}else{
917
-
thrownewError(
918
-
`The "CFBundleShortVersionString" key in the "${resolvedPlistFile}" file needs to specify a valid semver string, containing both a major and minor version (e.g. 1.3.2, 1.1).`
`The "CFBundleShortVersionString" key in the "${resolvedPlistFile}" file needs to specify a valid semver string, containing both a major and minor version (e.g. 1.3.2, 1.1).`
`The "MARKETING_VERSION" key in the "${resolvedPbxprojFile}" file needs to specify a valid semver string, containing both a major and minor version (e.g. 1.3.2, 1.1).`
1092
+
);
1093
+
}
1094
+
console.log(`Using the target binary version value "${marketingVersion}" from "${resolvedPbxprojFile}".\n`);
Copy file name to clipboardExpand all lines: cli/script/command-parser.ts
+24Lines changed: 24 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -804,6 +804,27 @@ yargs
804
804
description: "Path to private key used for code signing.",
805
805
type: "string",
806
806
})
807
+
.option("xcodeProjectFile",{
808
+
alias: "xp",
809
+
default: null,
810
+
demand: false,
811
+
description: "Path to the Xcode project or project.pbxproj file",
812
+
type: "string",
813
+
})
814
+
.option("xcodeTargetName",{
815
+
alias: "xt",
816
+
default: undefined,
817
+
demand: false,
818
+
description: "Name of target (PBXNativeTarget) which specifies the binary version you want to target this release at (iOS only)",
819
+
type: "string",
820
+
})
821
+
.option("buildConfigurationName",{
822
+
alias: "c",
823
+
default: undefined,
824
+
demand: false,
825
+
description: "Name of build configuration which specifies the binary version you want to target this release at. For example, 'Debug' or 'Release' (iOS only)",
0 commit comments