dlo · February 2, 2024 02:18 · Jul 16, 2016 · Jul 16, 2016 · Jul 16, 2016 · Jul 16, 2016
diff --git a/README.md b/README.md
@@ -10,7 +10,7 @@ Yes, yes, I know you can do this completely via fastlane, but I'm somewhat sadis
 
 To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](#file-post_action-sh), replacing "[email protected]" with your iTunes Connect username.
 
-Lastly, place [iTunesExportOptions.plist](#file-itunesexportoptions-plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
+Lastly, place [iTunesExportOptions.plist](#file-itunesexportoptions-plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to make some tweaks. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
 
 ## Dependencies
 

diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 This script will automatically upload your app to iTunes Connect after a successful Xcode archive action.
 
-After doing this about a million times by hand (i.e., "Window > Organizer", then clicking on "Upload to App Store", waiting for teams to load, etc.), I decided I'd had enough. Now, I just go to "Product" > "Archive", sip my margherita, and kick up my feet while the world marvels at my genius, while my app gets distributed to my testers without lifting but a finger. Or...I just take a bathroom break. Either way, it's pretty awesome.
+After doing this about a million times by hand (i.e., opening the Organizer, clicking on "Upload to App Store", waiting for teams to load, etc.), I decided I'd had enough. Now, I just go to "Product" > "Archive", sip my margherita, and kick up my feet while the world marvels at my genius, while my app gets distributed to my testers without lifting but a finger. Or...I just take a bathroom break. Either way, it's pretty awesome.
 
 Yes, yes, I know you can do this completely via fastlane, but I'm somewhat sadistic and prefer to do my archiving completely within Xcode.
 

diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 This script will automatically upload your app to iTunes Connect after a successful Xcode archive action.
 
-After doing this about a million times by hand (i.e., clicking on "Upload to App Store", waiting for teams to load, etc.), I decided I'd had enough. Now, I just go to "Product" > "Archive", sip my margherita, and kick up my feet while the world marvels at my genius, while my app gets distributed to my testers without lifting but a finger. Or...I just take a bathroom break. Either way, it's pretty awesome.
+After doing this about a million times by hand (i.e., "Window > Organizer", then clicking on "Upload to App Store", waiting for teams to load, etc.), I decided I'd had enough. Now, I just go to "Product" > "Archive", sip my margherita, and kick up my feet while the world marvels at my genius, while my app gets distributed to my testers without lifting but a finger. Or...I just take a bathroom break. Either way, it's pretty awesome.
 
 Yes, yes, I know you can do this completely via fastlane, but I'm somewhat sadistic and prefer to do my archiving completely within Xcode.
 

diff --git a/README.md b/README.md
@@ -20,4 +20,4 @@ Lastly, place [iTunesExportOptions.plist](#file-itunesexportoptions-plist) in yo
 gem install pilot
 ```
 
-You may want to use it one time interactively on the command line so that your credentials are saved for future pushes.
+You may want to run pilot at least one time prior, interactively on the command line, so that your credentials are saved for future use.
diff --git a/README.md b/README.md
@@ -4,7 +4,7 @@ This script will automatically upload your app to iTunes Connect after a success
 
 After doing this about a million times by hand (i.e., clicking on "Upload to App Store", waiting for teams to load, etc.), I decided I'd had enough. Now, I just go to "Product" > "Archive", sip my margherita, and kick up my feet while the world marvels at my genius, while my app gets distributed to my testers without lifting but a finger. Or...I just take a bathroom break. Either way, it's pretty awesome.
 
-Yes, yes, I know you can do this completely via fastlane, but I'm somewhat sadistic and prefer to do my archiving within Xcode.
+Yes, yes, I know you can do this completely via fastlane, but I'm somewhat sadistic and prefer to do my archiving completely within Xcode.
 
 ## Instructions
 

diff --git a/README.md b/README.md
@@ -2,7 +2,9 @@
 
 This script will automatically upload your app to iTunes Connect after a successful Xcode archive action.
 
-After doing this about a million times by hand (i.e., clicking on "Upload to App Store", waiting for teams to load, etc.), I decided I'd had enough. Now, I just hit "Archive", sip my margherita, and kick up my feet while the world marvels at my genius, while my app gets distributed to my testers without lifting but a finger. Or...I just take a bathroom break. Either way, it's pretty awesome.
+After doing this about a million times by hand (i.e., clicking on "Upload to App Store", waiting for teams to load, etc.), I decided I'd had enough. Now, I just go to "Product" > "Archive", sip my margherita, and kick up my feet while the world marvels at my genius, while my app gets distributed to my testers without lifting but a finger. Or...I just take a bathroom break. Either way, it's pretty awesome.
+
+Yes, yes, I know you can do this completely via fastlane, but I'm somewhat sadistic and prefer to do my archiving within Xcode.
 
 ## Instructions
 

diff --git a/README.md b/README.md
@@ -1,8 +1,8 @@
 ## Summary
 
-This script will automatically upload your app to iTunes Connect after a successful archive.
+This script will automatically upload your app to iTunes Connect after a successful Xcode archive action.
 
-After doing this about a million times manually, clicking on "Upload to App Store", waiting for teams to load, etc., I decided I'd had enough. Now, I just hit "Archive", sip my margherita, and kick up my feet while the world marvels at my genius. Or I'll take the dog out. Either way, it's pretty awesome.
+After doing this about a million times by hand (i.e., clicking on "Upload to App Store", waiting for teams to load, etc.), I decided I'd had enough. Now, I just hit "Archive", sip my margherita, and kick up my feet while the world marvels at my genius, while my app gets distributed to my testers without lifting but a finger. Or...I just take a bathroom break. Either way, it's pretty awesome.
 
 ## Instructions
 

diff --git a/README.md b/README.md
@@ -6,7 +6,7 @@ After doing this about a million times manually, clicking on "Upload to App Stor
 
 ## Instructions
 
-To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](#file-post-action-plist), replacing "[email protected]" with your iTunes Connect username.
+To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](#file-post_action-sh), replacing "[email protected]" with your iTunes Connect username.
 
 Lastly, place [iTunesExportOptions.plist](#file-itunesexportoptions-plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
 

diff --git a/README.md b/README.md
@@ -6,9 +6,9 @@ After doing this about a million times manually, clicking on "Upload to App Stor
 
 ## Instructions
 
-To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](/post_action.sh), replacing "[email protected]" with your iTunes Connect username.
+To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](#file-post-action-plist), replacing "[email protected]" with your iTunes Connect username.
 
-Lastly, place [iTunesExportOptions.plist](/iTunesExportOptions.plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
+Lastly, place [iTunesExportOptions.plist](#file-itunesexportoptions-plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
 
 ## Dependencies
 

diff --git a/README.md b/README.md
@@ -6,9 +6,9 @@ After doing this about a million times manually, clicking on "Upload to App Stor
 
 ## Instructions
 
-To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](post_action.sh), replacing "[email protected]" with your iTunes Connect username.
+To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](/post_action.sh), replacing "[email protected]" with your iTunes Connect username.
 
-Lastly, place [iTunesExportOptions.plist](iTunesExportOptions.plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
+Lastly, place [iTunesExportOptions.plist](/iTunesExportOptions.plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
 
 ## Dependencies
 

diff --git a/README.md b/README.md
@@ -1,6 +1,10 @@
-## Description
+## Summary
 
-This script will automatically upload Xcode archives to iTunes Connect after a successful build. After doing this about a million times manually, clicking on "Upload to App Store", waiting for teams to load, etc., I decided I'd had enough. Now, I just hit "Archive", sip my margherita, and kick up my feet while the world marvels at my genius. Or I'll take the dog out. Either way, it's pretty awesome.
+This script will automatically upload your app to iTunes Connect after a successful archive.
+
+After doing this about a million times manually, clicking on "Upload to App Store", waiting for teams to load, etc., I decided I'd had enough. Now, I just hit "Archive", sip my margherita, and kick up my feet while the world marvels at my genius. Or I'll take the dog out. Either way, it's pretty awesome.
+
+## Instructions
 
 To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](post_action.sh), replacing "[email protected]" with your iTunes Connect username.
 

diff --git a/README.md b/README.md
@@ -1,12 +1,12 @@
-## Xcode Script to Auto-Submit To App Store/TestFlight after Archive
+## Description
 
 This script will automatically upload Xcode archives to iTunes Connect after a successful build. After doing this about a million times manually, clicking on "Upload to App Store", waiting for teams to load, etc., I decided I'd had enough. Now, I just hit "Archive", sip my margherita, and kick up my feet while the world marvels at my genius. Or I'll take the dog out. Either way, it's pretty awesome.
 
 To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](post_action.sh), replacing "[email protected]" with your iTunes Connect username.
 
 Lastly, place [iTunesExportOptions.plist](iTunesExportOptions.plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
 
-## Dependences
+## Dependencies
 
 [pilot](https://github.com/fastlane/fastlane/tree/master/pilot) from [fastlane](https://github.com/fastlane/fastlane).
 

diff --git a/README.md b/README.md
@@ -1,10 +1,12 @@
+## Xcode Script to Auto-Submit To App Store/TestFlight after Archive
+
 This script will automatically upload Xcode archives to iTunes Connect after a successful build. After doing this about a million times manually, clicking on "Upload to App Store", waiting for teams to load, etc., I decided I'd had enough. Now, I just hit "Archive", sip my margherita, and kick up my feet while the world marvels at my genius. Or I'll take the dog out. Either way, it's pretty awesome.
 
 To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](post_action.sh), replacing "[email protected]" with your iTunes Connect username.
 
 Lastly, place [iTunesExportOptions.plist](iTunesExportOptions.plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
 
-### Dependences
+## Dependences
 
 [pilot](https://github.com/fastlane/fastlane/tree/master/pilot) from [fastlane](https://github.com/fastlane/fastlane).
 

diff --git a/README.md b/README.md
@@ -1 +1,15 @@
-This 
+This script will automatically upload Xcode archives to iTunes Connect after a successful build. After doing this about a million times manually, clicking on "Upload to App Store", waiting for teams to load, etc., I decided I'd had enough. Now, I just hit "Archive", sip my margherita, and kick up my feet while the world marvels at my genius. Or I'll take the dog out. Either way, it's pretty awesome.
+
+To make this work, open up the build scheme you use to submit your App Store builds, go to "Archive", and then "Post-actions". Click the "+" and "Add Run Script Action". Then, paste in the contents of [post_action.sh](post_action.sh), replacing "[email protected]" with your iTunes Connect username.
+
+Lastly, place [iTunesExportOptions.plist](iTunesExportOptions.plist) in your project directory. Depending on your needs (e.g., if you want to distribute enterprise builds) you may need to tweak it. See `xcodebuild -help` for more details. By default, it assumes you just want to submit the build to the App Store / TestFlight.
+
+### Dependences
+
+[pilot](https://github.com/fastlane/fastlane/tree/master/pilot) from [fastlane](https://github.com/fastlane/fastlane).
+
+```sh
+gem install pilot
+```
+
+You may want to use it one time interactively on the command line so that your credentials are saved for future pushes.
diff --git a/iTunesExportOptions.plist b/iTunesExportOptions.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/post_action.sh b/post_action.sh
@@ -1,4 +1,5 @@
 IPA_EXPORT_DIR=$(mktemp -d)
 ITUNES_USERNAME="[email protected]"
-cd "${PROJECT_DIR}"; xcodebuild -exportArchive -exportOptionsPlist iTunesExportOptions.plist -archivePath "${ARCHIVE_PATH}" -exportPath "${IPA_EXPORT_DIR}"
+
+xcodebuild -exportArchive -exportOptionsPlist "${PROJECT_DIR}/iTunesExportOptions.plist" -archivePath "${ARCHIVE_PATH}" -exportPath "${IPA_EXPORT_DIR}"
 pilot upload --skip_waiting_for_build_processing --username $ITUNES_USERNAME -i "${IPA_EXPORT_DIR}/${PRODUCT_NAME}.ipa"
diff --git a/README.md b/README.md
@@ -0,0 +1 @@
+This 
diff --git a/post_action.sh b/post_action.sh
@@ -1,3 +1,4 @@
 IPA_EXPORT_DIR=$(mktemp -d)
+ITUNES_USERNAME="[email protected]"
 cd "${PROJECT_DIR}"; xcodebuild -exportArchive -exportOptionsPlist iTunesExportOptions.plist -archivePath "${ARCHIVE_PATH}" -exportPath "${IPA_EXPORT_DIR}"
-pilot upload --skip_waiting_for_build_processing --username [email protected] -i "${IPA_EXPORT_DIR}/${PRODUCT_NAME}.ipa"
+pilot upload --skip_waiting_for_build_processing --username $ITUNES_USERNAME -i "${IPA_EXPORT_DIR}/${PRODUCT_NAME}.ipa"
diff --git a/post_action.sh b/post_action.sh
@@ -0,0 +1,3 @@
+IPA_EXPORT_DIR=$(mktemp -d)
+cd "${PROJECT_DIR}"; xcodebuild -exportArchive -exportOptionsPlist iTunesExportOptions.plist -archivePath "${ARCHIVE_PATH}" -exportPath "${IPA_EXPORT_DIR}"
+pilot upload --skip_waiting_for_build_processing --username [email protected] -i "${IPA_EXPORT_DIR}/${PRODUCT_NAME}.ipa"
No results found