"xcodebuild exportArchive -exportPath" does not write what it's documented to write
Originator: | irons | ||
Number: | rdar://22890779 | Date Originated: | 28-Sep-2015 06:41 PM |
Status: | Open | Resolved: | |
Product: | Developer Tools | Product Version: | 7.0.1 7A1001 |
Classification: | Serious Bug | Reproducible: | Always |
Summary: In Xcode 6.x, the `xcodebuild exportArchive -exportPath` argument specified the full path of the IPA being written to disk, including the filename. In Xcode 7, the argument to -exportPath only specifies the directory path. The xcodebuild 7.0 and 7.0.1 manpages still claim that exportPath “[s]pecifies the destination for the exported product, including the name of the exported file.” This is no longer true, though I wish it was, and I hope it will be again. Steps to Reproduce: 1. Create an xcarchive 2. Export it thusly: xcodebuild -exportArchive -exportPath path/to/app-build-17-production.ipa -archivePath /path/to/app-build-17-production.xcarchive -exportOptionsPlist adhoc.plist Expected Results: The exported IPA should reside at path/to/app-build-17-production.ipa. Actual Results: The exported IPA resides at path/to/app-build-17-production.ipa/name-of-app-target.ipa Regression: This is a change from Xcode 6.4. It’s also a regression in that it forces build managers to take an extra step to put differentiating context back into the app’s filename, commonly including a build number, and/or a choice of server endpoints.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
No fix in 8.0
I've verified that this bug still exists in XCode 8.0.