Incorrect platform provisioning profile

[yonaskolb]

If there are multiple provisioning profiles with the same bundleID (for example for iOS and tvOS), the auto provision step sometimes downloads the incorrect provisioning profile. This causes signing to fail later. It should check the type for the correct platform

Here you can see it downloads the correct development profile, but incorrect distribution profile:

Analyzing project
project codesign identity: iPhone Developer
project team id: 3PU2FX2MA5
uses xcode managed signing: true
target #0: Axis_iOS (co.massive.axis.demo) with 0 services
Matching project codesign identity with the uploaded certificates
using: iPhone Developer: Yonas Kolb (XY7TEP9H45) [2904252714206315985]
using: iPhone Distribution: Massive Interactive Pty Ltd (3PU2FX2MA5) [9139218735286723938]
Ensure Provisioning Profiles on Developer Portal
checking xcode managed development profile for target: Axis_iOS (co.massive.axis.demo) with 0 services on developer portal
downloading development profile: iOS Team Provisioning Profile: co.massive.axis.demo
checking xcode managed app-store profile for target: Axis_iOS (co.massive.axis.demo) with 0 services on developer portal
downloading app-store profile: tvOS Team Store Provisioning Profile: co.massive.axis.demo

This then creates an error in the Xcode Archive step

error: exportArchive: No "iOS App Store" profiles for team '3PU2FX2MA5' matching 'tvOS Team Store Provisioning Profile: co.massive.axis.demo' are installed.

[viktorbenei]

Thanks for reporting @yonaskolb , we'll fix this ASAP! :)

[godrei]

Hi @yonaskolb ,
we released a new version (1.0.2), which fixes this issue.

I'll close this issue, but if you need more info/help just let us know and we'll reopen it!

[yonaskolb]

Fantastic, thanks guys! 🎉

[viktorbenei]

Thanks for reporting @yonaskolb ! ;)

[wqz-leo]

Hey guys, I'm using version 1.1.3 but still have some issues with auto provision step when setting generate_profiles to yes.

The first issue is about duplicated provisioning profile name: In my repository, both iOS and tvOS targets are sharing the same code base, so both of them are having the same bundle identifier. iOS auto provisioning work fine, but when I generating profiles for tvOS, it fails due to duplicated provisioning profile name. Maybe we could have another configuration for provisioning profile name?

The second issue is about incorrect platform provisioning profile which generated by auto provision step. This step always generates iOS Development or iOS Distribution profiles. Is there a way to generate tvOS profiles in this step (maybe it's better to have a different name so it solves previous issue)?

[trapacska]

Hey @wangqingzhouleo !

Thanks for reporting. Just scheduled to check+fix it. When it has some progress we'll notify you here.

[wqz-leo]

Hi @trapacska, any progress on this issue?

[trapacska]

@wangqingzhouleo still not there. Sorry about that. Will try our best 🙂

[trapacska]

The new release is out, please let us know if the issue is still persist.

https://github.com/bitrise-steplib/steps-ios-auto-provision/releases/1.2.1

[wqz-leo]

Hi @trapacska,
Thanks for the fix! It can generate profiles for correct platform!
However, just noticed another minor issue for this step: it does not describe the platform in profile name.
Currently I have 2 Bitrise projects using the same bundle ID, one for iOS and one for tvOS. Both of them sharing the same app in iTunes Connect. When I trying to use auto generate profile for both projects, it only generates profile for the project which builds first. The later project will encounter an error Multiple profiles found with the name xxx. Please remove the duplicate profiles and try again .

Shall we add platform in the profile name?

Many thanks,

[lpusok]

Hi @wangqingzhouleo,
Thanks for the report, created an internal bug ticket.

[emirandm]

@lpusok Do you have an update on this issue? Issue still occurs in v1.4.2

[Roland-Bak]

Hi there @emirandm!

Just wanted to update you that this is still on the way, but once we are done with the finishing touches, we'll let you know! 😉

[lszucs]

Hi @yonaskolb,

CC: @wqz-leo @emirandm

This issue should be resolved by now, please try the latest step release if the issue still persists in your builds.

@emirandm: thanks for the contribution! :)

I will close this thread for now, feel free to reopen if issue seems to persist with latest version.