Skip to content
This repository has been archived by the owner on Nov 19, 2018. It is now read-only.

Initial support for Mac apps submission #545

Merged
merged 1 commit into from
Jan 20, 2016
Merged

Initial support for Mac apps submission #545

merged 1 commit into from
Jan 20, 2016

Conversation

olegoid
Copy link
Contributor

@olegoid olegoid commented Jan 19, 2016

WARNING: this PR requires conflicting options functionality from another pull request to fastlane_core

This PR adds initial support for OS X apps submission. With this patch users of deliver should be able to upload signed pkg files using --pkg key or it's short version -c(You may be wondering why c? Well it's mostly because p, k and g are occupied already. If you have better idea of naming please let me know).

Feedback and comments are greatly appreciated!

)
elsif options[:pkg]
package_path = FastlaneCore::PkgUploadPackageBuilder.new.generate(
app_id: options[:app].apple_id,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indent the first parameter one step more than the start of the previous line.

@KrauseFx
Copy link
Collaborator

This looks great already, thanks for all your amazing contribution 👍

@olegoid olegoid changed the title [WIP] Initial support for Mac apps submission Initial support for Mac apps submission Jan 19, 2016
@olegoid
Copy link
Contributor Author

olegoid commented Jan 19, 2016

Hey @KrauseFx, thanks for your comments! Actually I think this PR is ready for review.

@@ -36,7 +36,8 @@ def run
c.action do |args, options|
options = FastlaneCore::Configuration.create(Deliver::Options.available_options, options.__hash__)
loaded = options.load_configuration_file("Deliverfile")
loaded = true if options[:description] || options[:ipa] # do we have *anything* here?
options.verify_conflicts
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think there is a good way to change this so that you don't have to call this method manually? Maybe we could check it whenever we access a value? On the other hand I can see how this might cause problems when setting values on the run time.
I'm okay with leaving it like this, just want to your thought on this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @KrauseFx, I think that this verification should be implemented on fastlane_core level and verify_conflicts should be called each time we load options values(from CLI, config file or setting defaults).
I added a few updates to conflicting options PR wrt this.

Thanks again for highlighting it!

@KrauseFx
Copy link
Collaborator

Looks great, let's wait until the fastlane_core PR is done, then we can merge and release this, thanks for your contribution 🚀

Update readme with instructions about pkg files submission

Update Deliverfile.md

Update Deliverfile.md again

Add options conflict verification after reading from Deliveryfile

Improve options conflict error messages

Fix code formatting issue

Update README.md - prefix OS X with Mac

Now options verified automatically in fastlane_core module
KrauseFx added a commit that referenced this pull request Jan 20, 2016
Initial support for Mac apps submission
@KrauseFx KrauseFx merged commit 59ca2f5 into fastlane-old:master Jan 20, 2016
@KrauseFx
Copy link
Collaborator

Perfect, thank you so much 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants