We released a new version ( 1.0.0 ) of iOS Auto Provision step. Changes: support iOS projects with Xcode’s Automatically manage signing option

@MattCheetham it seems the step is able to determine your scheme target’s bundle id. Then the step tries to ensure the app-store and development type Provisioning Profile for this target. The development target’s Profile seems to be existing on Developer Portal and it downloads successfully, but …

@matthias.buchetics it seems you did not upload any development type codesign identity, thats why the step can not ensure the existence of your development profile and xcode missis this file: Xcode couldn't find any iOS App Development provisioning profiles matching 'your.bundle.id'. Please upload…

We are also having an issue with the latest version of auto-provision step not being able to find the bundle id. Before today this was working fine. The project had the client bundle identifier, and “automatically manage signing” checked, and the team set to the client. Then we use the “Replaces Xc…

I’ll try generating it again today and see if it resolves it. Is this a new requirement with this version? It has been building fine for as long as I remember but as soon as we switched to v1.0 it broke. That would be an odd coincidence.

Exporting via xcode then running a rebuild has fixed it. Thanks! I guess by chance the profile must have expired at the exact same time as you releasing the update.

Hi, sorry for the inconveniences! Could you please write us a message on bitrise.io on-site-chat? I would need to have a look on your .xcodeproj file to debug the issue.

@MattCheetham , thanks for your debugging ad for sharing your experiences. Before 1.0.0 the step does not cared if the project uses Xcode managed signing or not. It picked the target bundle ids which needs to be signed and ensure both the app and the profile for the targets then it modified your pr…

I continue to have problems since 1.0. Projects that build fine using 0.9.7 fail: :x: error: Provisioning profile “iOS Team Provisioning Profile: xxx” doesn’t include signing certificate “iPhone Developer: xxx”. (in target ‘xxx’) [image] Bitrise - Mobile Continuous Integration and Delive…

Hi @matthias.buchetics , please have a look on the auto-provision step’s log: Provided an older version of iPhone Developer: XYZ certificate (serial: OLD_SERIAL expire: 2018-11-17 08:08:57 UTC), please download the most recent version from the Apple Developer Portal (serial: LATEST_SERIAL expire: 2…

iOS Auto Provision v1.0.0

Changelog

godreikrisztian March 29, 2018, 3:27pm 26

Hi, we released a new version of the step, please have a look on it and let us know how does it work for you: iOS Auto Provision v1.0.1

Topic		Replies	Views
iOS Auto Provision v1.0.1 Changelog step	5	6735	May 11, 2018
IOS/XCode: Wrong provision profile selection by iOS Auto Provision for Same export type and Team, but different bundleID Builds ios-auto-provision	14	9256	September 16, 2018
Ios-auto-provision 1.3.1 Failed to find ad-hoc Xcode managed provisioning profile for bundle id: com.mindoula.royals.mmr.staging Builds	12	2071	November 14, 2019
iOS Auto Provision v1.1.0 Changelog step	0	4009	May 11, 2018
Enable automatic signing Builds ios	8	3228	October 21, 2021

iOS Auto Provision v1.0.0

Related topics