Test devices are not being added to new provisioning profile on 1.2.3 about steps-ios-auto-provision

[vdmtrv]

@Javi this could be related to the adhoc bug that was introduced in fastlane 2.111.0. If that's the case then the #52 PR should resolve it.

[godrei]

Hi @Javi , we have released a new version: 1.3.0, could you please check if it solves your issue?

[Javi]

Still doesn't seem to work, can you repro it?

[fehersanyi-bitrise]

Hello there!

We realised that it is not working as intended, and reviewing the new version.
until then the workaround is to delete the bitrise managed profiles from the dev portal when a new UDID is added, so the step will generate a new profile that includes the test device.

[Alex-Mason-RocketInsights]

Has this been fixed? I am working with a client and do not have access to the Apple Developer portal and a new device has been added.

[fehersanyi-bitrise]

Hy @Alex-Mason-RocketInsights , there was a new release 1.3.1 24 days ago, did you check it with that one?

[Alex-Mason-RocketInsights]

Yes I did, however it does not appear to A) Create a profile that has Push Notifications Capability or B) Add said profile to the export options plist. I opened a full issue here: https://discuss.bitrise.io/t/ios-autoprovision-does-not-work-for-provisioning-profile-that-requires-push-notifications-capability/8477

[ethan021021]

Would love to see a fix for this, just tried to add a test users device UDID to the apple developer portal and the Bitrise test device portal and the step said it found the UDID registered in both. But I had to manually delete my provisioning files on my Mac so Xcode could regenerate them. After I did that the step started working again.

[bitce]

Hi @ethan021021!

This problem shouldn't really be present anymore. Can you please contact us on-site with your builds details so we can investigate?

[kzietek]

Hi!

I'm using "iOS Auto Provision" v1.5.2 and the problem still persists. I'm using a workaround to regenerate the team provisioning profile:

• Archive selected target locally (probably optional if you already have an archive)
• Make an ipa from archived target. Use automatic signing so XCode changes something invisible on Apple's side.

Probably to fix this permanently it is needed to alter the "XCode Archive & Export for iOS" step.

[bitce]

Hi @kzietek, can you please send us a report about this so we can investigate?

What we'd need is:

• A URL to a build where this issue is happening
• A UDID for a device that is registered on Bitrise (we'd need a screenshot)
• Support Access for the app which you can turn on in the Settings.

Thanks!

[github-actions]

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant.
This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

[github-actions]

I'll close this issue as it doesn't seem to be relevant anymore.
We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.