Closed seanmalone-redibs closed 2 years ago
One additional note: I had to include build_configuration_name
; otherwise, scheme
was ignored and all schemes are updated. Not sure if this intentional? If so, it seems a bit misleading. If build_configuration_name
is required when scheme
is provided, can it throw an error instead of falling through to all?
Hey @seanmalone-redibs - sorry for a lengthy response. I spent some time looking into this, and was wondering if this 'myapp' / 'Development' input was for a fresh, mostly out-of-the-box xcodeproject or not? I setup a small test locally with the closest thing I could guess was your project (renaming Debug -> Development, same project name), and had the same crash, until I manually set the build and project version by hand through Xcode's UI. After that, everything worked swimmingly. If this is the same for you - I'll make sure to add to the readme so other people aren't caught by this gotcha.
@seanmalone-redibs - did this help you with your issue?
@jdouglas-nz Thanks for the reply and sorry for the delayed response. Are you saying that if we need to manually set the build and project version once and then the plugin will update properly from that point on?
@seanmalone-redibs it worked for me at least! I don't think I didn't something other that that to get it working. Please give it a go !
Thanks! It works now. I guess I didn't have a default set.
When running with the following parameters:
I get the following error:
Looking at the source code for
set_build_number_using_scheme
it has this line:project.build_settings["CURRENT_PROJECT_VERSION"] = next_build_number
It looks like
project.build_settings
is a getter that returns the value for a given key. Unfortunately, it's not a setter for the build settings.Please advise and thank you for putting this plugin together.