Provisioning profile not getting set while building Xcode project using Jenkins - ios

I am connecting to gitlab to pull source code and build the app through Jenkins. At build time, i am changing the bundle ID, certificate and provisioning profile for the App. But for some reason, the provisioning profile is not getting set while the former two works perfectly. I have added the profiles in KISS plugin and also provided the path to the profile in the Xcode plugin.
I have configured as below
I am getting the following error while building the App
App requires a provisioning profile. Select a provisioning profile for the "Release" build configuration in the project editor.
Code signing is required for product type 'Application' in SDK 'iOS 10.0'
Attaching the console screenshot

Related

How can I Solve this error when iOS build in Flutter

How can I solve this error?
Error (Xcode): No profiles for 'com.school.wcc2' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.school.wcc2'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild.
It appears that there was a problem signing your application prior to installation on the device.
Verify that the Bundle Identifier in your project is your signing id in Xcode
open ios/Runner.xcworkspace
Also try selecting 'Product > Build' to fix the problem:
Encountered error while building for device.
Go to project folder, open the iOS project in Xcode. On the left hand side, select the root, navigate to signing and capability
It would loo something like this.
In order to deploy your app in iPhone, you would need development provisioning profile. If you manage your developer account you can go for "Automatically manage signing" and Xcode would do all the needful.
Else, you would need to request the provisioning certificate from your team.
After creating the profile, restart your IDEs.

debug version of react-native IOS app builds successfully. Release version fails.

I've been able to successfully build the Debug version of this IOS app. However, I'd like to create an IPA to make sure it works on various iphones. The first thing I did was go product->scheme->edit scheme. I then switched from Debug to Release. After cleaning, and attempting to build the release version of the app. I immediately get an error: "MYapp has conflicting provisioning settings. MYapp is automatically signed, but provisioning profile MYApp Distribution has been manually specified. Set the provisioning profile value to "automatic" in the build settings editor, or switch to manual signing in the project editor(in target MYapp).
The first thing I tried was switching Code Signing Style to manual in build settings. This resulted in a new error:
error: Provisioning profile "MYApp Distribution" doesn't include signing certificate "iPhone Developer: Name here (XXXXXXXX)". (in target 'MYApp')
I went back to the General tab in Targets and clicked on "automatically manage signing". I tried to rebuild and got the same error the first time I tried to build.
I'm not sure where the conflict is coming from. This post indicated that simply clicking the automatic signing would do the trick.
I'm quite new to using Xcode and understanding provisioning profiles.
You simply can not build a release edition. The process of giving a release version is quite different. It goes from Xcode(local) to App Store(testFlight for testing) and then into App Store(Official Release).
I found this link and can relate to this situation.
Your provisioning profile isn't valid. It doesn't have a valid distribution certificate. You have to go to apple developer and it to certificates and profiles. Create it there and install it via keychain on your macbook. Othervise you can't build an ipa. More info here

Jenkins, Xcode 8.2.1 can not find the provisioning profile though it exists

I am running an iOS build on Jenkins locally. Using Xcode 8.2.1. Using manual signing (i.e. provisioning profile, Team and Signing Certificate correctly selected in Target-> General section.). When I build the app through Xcode, the app builds and archives fine using my ad-hoc distribution certificates. However, when I try building using Jenkins, I get the following error (I am using my own build script to build the app and not using the Jenkins Xcode build plugin)-
Check dependencies
[BCEROR]No profile matching 'xxx' found: Xcode couldn't find a profile matching 'xxx'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the General tab of the target editor.
Btw, I already tried the following but those did not help-
copying the provisioning profile in question to the /Users/Shared/Jenkins/Library/MobileDevice/Provisioning Profiles location.

Attempting to install the Release version on my device gets conflict profiles

I am trying to install the Release version of my app on my device to test it.
When I select the Edit > Scheme and under RUN I choose "Release" for Build Configuration
But I get the error:
My App has conflicting provisioning settings. My App is automatically
signed for development, but a conflicting code signing identity iPhone
Distribution has been manually specified. Set the code signing
identity value to "iPhone Developer" in the build settings editor, or
switch to manual signing in the project editor. Code signing is
required for product type 'Application' in SDK 'iOS 10.2'
I have gone to Code Signing and Ensured that my release is my iOS Distribution
I have deleted all my profile, certs and re-imported. I have cleaned the build. I have removed my account.
When I switch to Manual Signing I get the error:
No signing certificate "iOS Distribution" found
No "iOS Distribution" signing certificate matching team ID "XXXXXXXXXX" with a private key was found.
But it is in my KeyChain.
I'm so frustrated. Has anyone else solved this?
You're supposed to use the iOS developer profile when running builds on your device. You can build in release mode still. However you can't install distribution signed binaries through Xcode.
You can create an ad-hoc profile to test push notification for the release build. It is same as the distribution build.

TeamCity 8 xcode 5 agent code sign error

I am trying to run Xcode using TeamCity but I am getting a Code Sign error. Even though the provision profile and certificate exists on my machine. I can build it on my iPhone. This is the error I am getting:
Step 1/1: Xcode Project [09:36:16][Step 1/1] PRAnalytics (CLEAN)
[09:36:16][PRAnalytics (CLEAN)] [BEROR]Code Sign error: No matching
provisioning profile found: Your build settings specify a provisioning
profile with the UUID “8A7A8B79-####-####-####-C39537A6A156”, however,
no such provisioning profile was found.
[09:36:16][PRAnalytics (CLEAN)] [BEROR]CodeSign error: code signing is
required for product type 'Application' in SDK 'iOS 7.1'
[09:36:16][Step 1/1] Code Sign error: No matching provisioning profile
found: Your build settings specify a provisioning profile with the
UUID “8A7A8B79-####-####-####-C39537A6A156”, however, no such
provisioning profile was found.
[09:36:16][Step 1/1] CodeSign error: code signing is required for
product type 'Application' in SDK 'iOS 7.1'
[09:36:16][Step 1/1] Step Xcode Project failed
I was able to solve this issue, which was due to two main reasons, Xcode when invoked from teamcity looks its resources from the System & not the user, so to fix at least get sure that you did the following:-
1-Ensure the project is building successfully from Xcode to real target.
-In KeyChain
2-Copy all the development certificates & credentials form your user folder to the system folder
3-Copy all the Provisioning profiles existing in
Users//Library/MobileDevice/Provisioning Profiles
to
System/Library/MobileDevice/Provisioning Profiles
Create the missing folders if they don’t exist below 'Library'
Finally figured out. My agent was in HD/AGENT. When i moved it to HD/USER/DESKTOP/AGENT, it began to work. Seems like Agent should be in the USER directory.
Have you checked build settings properly. Check your plist for identifier. And provisioning profile and code signing settings in Build settings. Make sure you are setting right provisioning and certificate.

Resources