How to "Select a development team in the project editor" in ionic-archive steps?

step
ionic
ios
#1

I build the ionic project with steps:

steps:
- script@1.1.5:
title: ios build
- certificate-and-profile-installer@1.9.2: {}

- generate-cordova-build-configuration@0.9.3:
    inputs:
    - code_sign_identity: '....'
    - provisioning_profile: MyApp
    - package_type: development
    - development_team: ....
- certificate-and-profile-installer: {}
- ionic-archive@1.2.2:
    inputs:
    - platform: "ios"
    - target: device
- deploy-to-bitrise-io@1.3.10: {}

I receive the error:
Check dependencies
Code Signing Error: Signing for “MyApp” requires a development team. Select a development team in the project editor.
Code Signing Error: Code signing is required for product type ‘Application’ in SDK ‘iOS 11.3’

How to “Select a development team in the project editor” in ionic-archive steps?

Thanks.

0 Likes

Ionic-Archive step code-signing Error
#2

Hi @tvanh,
could you please attach your build url?

0 Likes

#3

Hi @godreikrisztian,

I have just resolved the error above, but I receive the new error:
=== BUILD TARGET MyApp OF PROJECT MyApp WITH CONFIGURATION Debug ===
Check dependencies
Code Signing Error: No profile for team ‘734586564N’ matching ‘MyApp_Dev’ found: Xcode couldn’t find any provisioning profiles matching ‘734586564N/MyApp_Dev’. 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.
Code Signing Error: Code signing is required for product type ‘Application’ in SDK ‘iOS 11.3’
** ARCHIVE FAILED **

Could you please help me with this case?

Thanks.

0 Likes

#4

Hi,
the value of the Provisioning Profile input, should be: GUID of the provisioning profile to be used for signing, example: c5be4123-1234-4f9d-9843-0d9be985a068

0 Likes

#5

I resolved this issue. Thank you so much. :slight_smile:

1 Like

#6

What did you do to solve this issue? I’m facing the same thing!

0 Likes

iOS error signing requires a development team
#7

Hi @alastairmcfarlane,
This is the solution:
the value of the Provisioning Profile input should be: GUID of the provisioning profile to be used for signing,

example: c5be4123-1234-4f9d-9843-0d9be985a068.

You should use the GUID of the provisioning profile instead of name.

1 Like

closed #8

This topic was automatically closed after 14 days. New replies are no longer allowed.

0 Likes