Conversation
Wow, this looks really good. Does that mean, you didn't have to change anything for uploading the Some users experienced the same problem when using deliver: fastlane-old/deliver#42 Thanks for sharing your solution @sinoru 👍 |
@KrauseFx I just added last process that add Previous
After adding
After that, uploading this ipa to iTunes Connect, and it success. But, I only found SwiftSupport folder in Xcode Archive. |
@sinoru Could you please merge master into this branch? I'm trying to test your changes in my app by referencing your fork/branch in my Gemfile, but then other dependencies complain because you don't have latest version in .gemspec. Thanks! |
@DarthMike The latest released version is Only @mattt can merge pull requests into master |
I merged new 0.10.3 master to my branch. It might give some helps. I think. |
Thanks! |
JFYI: I'm working on a patch that works in a different way, is less slightly less intrusive than this one, works transparently regardless of whether or not the developer is building a Swift project and, most importantly, doesn't change the way the .ipa gets built. I'll submit a pull request as soon as I confirm that it works fine for iTunes uploads. |
@lvillani Looking forward to it, thanks for working on a fix 👍 |
Hi!
This tool is really nice that can distribute to many places or iTunes Connect directly.
BUT, It doesn't support when swift codes are in.
I really want to use iTunes Connect distribution with this tool even though using Swift.
So I'm looking into it.
I found that Xcode Command Line tools doesn't contains SwiftSupport folder when PackageApplication it.
And, SwiftSupport folder is located in Xcode Archive.
So this commits make shenzhen will do archive action and embed SwiftSupport folder directly.
With this, I uploaded app to iTunes Connect successfully, and can distribute it through TestFlight by Apple.
Thanks!