xcode 9 beta export options not working #9589
Comments
|
It seems like this issue might be related to code signing 🚫 Have you seen our new Code Signing Troubleshooting Guide? It will help you resolve the most common code signing issues 👍 |
|
@fastlane-bot NO, I DO NOT. |
jetersen
changed the title
|
Project is running automatic signing with iPhone Developer. |
|
Oh it might be the fact that we switched to workspace since I last tested it. |
|
@Casz I can see that your export expects certain profiles to be on the disk. The error is very clear, it simply can't find the profiles. I also see that your fastlane script is using But the documentation says For manual signing only, while you say that you use automatic signing. Maybe that's the reason. What is the exact fastlane action that you use to create and export IPA? |
|
Check the fastfile included in fastlane environment. The provision profiles is auto generated when using xcode 9 and latest fastlane This is run locally, not on Jenkins. |
|
Yes running xcodebuild -help does show that provisioningProfiles is only for manual signing. After switching to manual signing I still get the same error shown in the issue. |
|
When switching to manual signing, do you have your You are not passing those to Also, the "com.widex.app" needs to be the specifier of the provisioning profile, aka name, but not the name of the file or not the bundle ID. For example, this is how it looks inside the profile: Your logs seem to be using Ad-Hoc distribution type, which means If your development profile has com.wides.app specifier, then I think ad-hoc profile can't have the same specifier. If I understand it correctly, identifiers need to be unique. (Don't take my word for it :), I'm not so sure about names being unique, would have to check). It's not just failing to find a provisioning profile, it fails to find a profile for Ad Hoc distribution in particular. |
|
This PR #9432 is part of the new xcode 9 feature where we should be able to avoid using PROVISIONING_PROFILE_SPECIFIER. fastlane/fastlane/lib/fastlane/actions/gym.rb Lines 22 to 30 in fa8ab8f As mentioned build was successful ie. match was successful. |
|
@KrauseFx Am I completely mistaken? |
|
To put more context, our project builds with Xcode 8 and manuel signing swap on our |
|
Disclaimer I am not at all familiar with how fastlane works. From Xcode 9 beta release notes (emphasis mine)
So it might be just a case of passing the -allowProvisioningUpdates flag when using xcodebuild -exportArchive if there is a way in fastlane to do so. |
|
Hey folks! In trying to reproduce this issue, I have run into another set of Xcode 9 bugs. I am wondering if you all are still seeing this issue or if anything new has cropped up? Let us know if its still going on! 🚀 |
|
@ohayon I am also getting this problem, the issue i have is i try to do this in my fastlane fastfile: When i manually run that command with the additional |
|
I have the exact same issue. Xcode 9 beta, automatic signing. Feels like this is quite urgent as XCode 9 is about to go public. |
|
Same issue here |
|
I use Xcode 9 beta and manually upload to Store, it stated that only non-beta version is allowed. Is that the reason for this problem? |
|
Everyone, please read the complete output. Only one person here shared their output, and it clearly explains the error please read the output, or share it here, so we can help |
|
Also, this does not seem like it's an issue with fastlane |
|
Strange, as i managed to get the app to upload via Xcode from the same machine and it worked. |
|
|
This issue also affects my project. One tip, I use "Automatically manage signing" option, maybe in new xcodebuild it's required to pass -allowProvisioningUpdates to achieve same thing, so maybe there should be an option to pass it with fastlane? |
|
@Reedyuk Instead of |
|
where do i use export_xcargs? |
|
Actually, i can confirm that has done the trick. |
|
|
|
Had the same issue, adding |
…ds to iTunes Connect per fastlane/fastlane#9589.
|
thanks @thebugcode |
|
@thebugcode Not sure if this applies to your setup, but in my case I only needed to add signingStyle manual to my export options. It's not very well documented (AFAIK), but you can actually pass a hash as export_options that gym will add to the generated exportOptions.plist, so in my case I just had to add it like this: |
|
The trick with allowProvisioningUpdates flag works perfect locally but not when the lane is executed from Jenkins. The same fastfile, the same lane. |
|
@VIPLORD with |
I wonder if anybody here has figured out how to do this programmatically? |
|
@sander-m Does XCode archive your build manually without problems? If yes then try @thebugcode solution or this one |
|
Just wonder when this fix will be available? thanks |
|
@Jun711 latest release 2.62.1 includes the manuel style fix at least 👍 |
|
@Casz Is manual style fix what @thebugcode suggested? I got this error with fastlane 2.62.1 without any fix |
|
@Jun711 Are you using match or sigh? |
|
@Casz match Will it be enough if I add this to my gym section? |
|
match should already expose the certificates, unless you call them separately. You need to have a lane that calls your certificates lane and calls gym that way match should expose the values to gym 👍 lane :build do
certificates # calls the certificates lane so match can expose the app ids
gym(
export_method: "app-store"
)
end |
|
@Casz After trying what you suggested, match lane ran properly but I got this error instead ERROR [2017-10-23 13:11:37.99]: fastlane finished with errors |
|
obviously typo on my end 🗡 |
|
@Casz yea, I can push to test flight now, thanks! |
|
I explain here my situation, so maybe is useful for somebody: I have automatic signing enabled. I was getting the error because sigh was configured to When the signing process was happening, xCode was looking for certificate "A" in my machine, it was not finding it and it was failing. Removing Note: the -allowProvisioningUpdates worked, but was asking for access to the keychain all the time. |
|
Issue is resolved |
|
So what's the best solution? Using a plist that you pass to |
|
if you are not using sigh or match, then passing the plist to gym is the next best. |
|
This is our current build lane: lane :build do |options|
xcversion version: '~> 9'
scheme = options[:scheme] || ENV['GYM_SCHEME']
configuration = options[:configuration] || 'Debug'
type = options[:type] || 'development'
app_identifier = options[:app_identifier] || ENV['APP_IDENTIFIER']
git_branch = options[:git_branch] || ENV['MATCH_GIT_BRANCH']
export_method = options[:export_method] || 'development'
if is_jenkins
setup_jenkins
configuration = 'Release'
FileUtils.rm_rf('../output')
ENV['FL_BUILDLOG_PATH'] = 'fastlane/logs'
bump_build_number
app_identifiers = [
app_identifier,
"#{app_identifier}.watchkitapp",
"#{app_identifier}.watchkitapp.watchkitextension"
]
update_project_team
match(
type: type,
readonly: true,
git_branch: git_branch,
app_identifier: app_identifiers
)
export_method = Actions.lane_context[SharedValues::SIGH_PROFILE_TYPE]
end
pods
xcargs = [
"APP_IDENTIFIER=#{app_identifier}",
'-allowProvisioningUpdates',
options[:xcarg]
]
gym(
scheme: scheme,
configuration: configuration,
xcargs: xcargs.join(' '),
export_method: export_method
)
end |
|
And if I use |
|
@revolter if you disable automatic signing ya. |
|
I'm using Here's my current lane: |
|
with Match in hand, you should not need to specify export_method or export_options. Match will set the proper options for export |
|
I'll lock this issue for now as the original problem was resolved - if you're running into the same problem please submit a new issue, so we can help you 👍 |
and others
New Issue Checklist
Issue Description
Extension of #9458
Project builds but come export for ad-hoc or release. I get the following output
Same error on xcode 9 beta 2.
Complete output when running fastlane, including the stack trace and command used
Run locally and pretending I am Jenkins to run match.
JENKINS_HOME=a fastlane betaFastlane failed to capture output, below output is enough, imho.
Environment
🚫 fastlane environment 🚫
Stack
System Locale
fastlane files:
`./fastlane/Fastfile`
`./fastlane/Appfile`
fastlane gems
Loaded fastlane plugins:
No plugins Loaded
Loaded gems
generated on: 2017-06-27
The text was updated successfully, but these errors were encountered: