cocoaNib · July 3, 2025 09:38 · Mar 4, 2016 · Mar 3, 2016
diff --git a/exportOptionsAdHoc.plist b/exportOptionsAdHoc.plist
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>method</key>
+	<string>ad-hoc</string>
+</dict>
+</plist>
diff --git a/exportOptionsRelease.plist b/exportOptionsRelease.plist
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>method</key>
+	<string>app-store</string>
+</dict>
+</plist>
diff --git a/exportOptionsPlist → xcodebuild -exportArchive b/exportOptionsPlist → xcodebuild -exportArchive
@@ -1,4 +1,20 @@
-Available keys for -exportOptionsPlist:
+AdHoc
+xcodebuild -exportArchive -archivePath ~/Desktop/build/AdHoc/AdHoc.xcarchive -exportPath ~/Desktop/build/AdHoc -exportOptionsPlist ~/Desktop/build/AdHoc/exportOptionsAdHoc.plist
+
+Release
+xcodebuild -exportArchive -archivePath ~/Desktop/build/Release/Release.xcarchive -exportPath ~/Desktop/build/Release -exportOptionsPlist ~/Desktop/build/Release/exportOptionsRelease.plist
+
+Folders and Files on my desktop:
+build
+  AdHoc
+    AdHoc.xcarchive
+    exportOptionsAdHoc.plist
+  Release
+   exportOptionsRelease.plist
+   Release.xcarchive
+
+
+All Available keys for -exportOptionsPlist:
 
 	compileBitcode : Bool
 

diff --git a/exportOptionsPlist b/exportOptionsPlist
@@ -0,0 +1,41 @@
+Available keys for -exportOptionsPlist:
+
+	compileBitcode : Bool
+
+		For non-App Store exports, should Xcode re-compile the app from bitcode? Defaults to YES.
+
+	embedOnDemandResourcesAssetPacksInBundle : Bool
+
+		For non-App Store exports, if the app uses On Demand Resources and this is YES, asset packs are embedded in the app bundle so that the app can be tested without a server to host asset packs. Defaults to YES unless onDemandResourcesAssetPacksBaseURL is specified.
+
+	iCloudContainerEnvironment
+
+		For non-App Store exports, if the app is using CloudKit, this configures the "com.apple.developer.icloud-container-environment" entitlement. Available options: Development and Production. Defaults to Development.
+
+	manifest : Dictionary
+
+		For non-App Store exports, users can download your app over the web by opening your distribution manifest file in a web browser. To generate a distribution manifest, the value of this key should be a dictionary with three sub-keys: appURL, displayImageURL, fullSizeImageURL. The additional sub-key assetPackManifestURL is required when using on demand resources.
+
+	method : String
+
+		Describes how Xcode should export the archive. Available options: app-store, ad-hoc, package, enterprise, development, and developer-id. The list of options varies based on the type of archive. Defaults to development.
+
+	onDemandResourcesAssetPacksBaseURL : String
+
+		For non-App Store exports, if the app uses On Demand Resources and embedOnDemandResourcesAssetPacksInBundle isn't YES, this should be a base URL specifying where asset packs are going to be hosted. This configures the app to download asset packs from the specified URL.
+
+	teamID : String
+
+		The Developer Portal team to use for this export. Defaults to the team used to build the archive.
+
+	thinning : String
+
+		For non-App Store exports, should Xcode thin the package for one or more device variants? Available options: <none> (Xcode produces a non-thinned universal app), <thin-for-all-variants> (Xcode produces a universal app and all available thinned variants), or a model identifier for a specific device (e.g. "iPhone7,1"). Defaults to <none>.
+
+	uploadBitcode : Bool
+
+		For App Store exports, should the package include bitcode? Defaults to YES.
+
+	uploadSymbols : Bool
+
+		For App Store exports, should the package include symbols? Defaults to YES.