Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provisioning Profile "com.company.app AppStore" doesn't include signing certificate iPhone... #13079

Closed
4 tasks done
meehanman opened this issue Aug 10, 2018 · 7 comments
Closed
4 tasks done

Comments

@meehanman
Copy link

meehanman commented Aug 10, 2018

Question Checklist

Question Subject

I'm having codesigning issues when using gym for an iOS app; in particular the codesigning_identity (Signing Certificate) is not being set by the build_app command.

Question Description

I expect cert and sigh to check certificates and provisioning profiles and then be able to set these profiles in my XCode project using build_app (gym), but the following Factfile returns the error. Code Signing Error: Provisioning profile "com.CompanyName.myCompanyName AppStore" doesn't include signing certificate "iPhone Distribution: Company Name (XZXZXZXZXZX)".

default_platform(:ios)

platform :ios do
  desc "Push a new beta build to TestFlight"
  lane :beta do |options|
	  build_number = increment_build_number(
		  build_number: latest_testflight_build_number + 1
	  )
	  version_number = increment_version_number(
		version_number: options[:version_number]
	  )
	  automatic_code_signing(use_automatic_signing: false, team_id: "XZXZXZXZXZX")

	  sh(
		  "echo ##teamcity[buildNumber '#{version_number}(#{build_number})']"
	  )
	  cert
	  uuid = sigh(
		force: true,
		filename: "CompanyName.mobileprovision"
	  )
	  update_project_provisioning(
		target_filter: "CompanyName",
		profile: "CompanyName.mobileprovision",
		build_configuration: options[:configuration]
	  )
	  
	  build_app(
		  scheme: "CompanyName",
		  configuration: options[:configuration],
		  clean: true,
		  silent: true,
		  output_directory: "/usr/local/Repos/OLS/artifacts/",
		  output_name: "CompanyName.ipa",
		  export_method: "app-store",
		  codesigning_identity: "iPhone Distribution: Company Name (XZXZXZXZXZX)",
		  export_options: {
			  provisioningProfiles: {
				  "com.CompanyName.myCompanyName" => "com.CompanyName.myCompanyName AppStore",
				  "com.CompanyName.myCompanyName" => "com.CompanyName.myCompanyName Development"
			  }
		  }
	  )

	  if options[:pushToStore]
		  upload_to_testflight(
			  ipa: "/usr/local/Repos/OLS/artifacts/CompanyName.ipa",
		  )
	  end
  end
end

After running fastlane and recieving the error. I'm left with an XCode project that states:
Code Signing Error: Provisioning profile "com.CompanyName.myCompanyName AppStore" doesn't include signing certificate "iPhone Developer: Company Name (XYXYXYXYXYX)".


If I manually then reselect the Provisioing Profile for the "Signing (Release)" back to the same one that was set. The Signing Certificate then changes to the one specified iPhone Distribution: Company Name (XZXZXZXZXZX)

I'm aware this is a code signing issue, and maybe not a Fastlane issue, but any help is appriciated to narrow down this issue.

Thank you
Dean Meehan

@fastlane-bot
Copy link

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
Copy link

It seems like you have not included the output of fastlane env

To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

@LasseSLambertsen
Copy link

Got the same problem, I can sign fine using Xcode directly, but not through fastlane

@meehanman
Copy link
Author

meehanman commented Aug 11, 2018 via email

@LasseSLambertsen
Copy link

Managed to finally fix my problem. It was a permission problem, somehow I had corrupted some... Fixed it by running:

diskutil resetUserPermissions / id -u

In a terminal

@fastlane-bot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@fastlane-bot
Copy link

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

@fastlane fastlane locked and limited conversation to collaborators Nov 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants