Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-25329] iOS CLI: No profile for team '6E5M3DGMBX' - where the team is the bundle identifier

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionDuplicate
Resolution Date2017-09-22T11:47:23.000+0000
Affected Version/sRelease 6.2.1
Fix Version/sn/a
ComponentsiOS
Labelsn/a
ReporterAlberto Marcone
AssigneeChris Barber
Created2017-09-21T11:03:29.000+0000
Updated2018-08-06T17:41:10.000+0000

Description

Just updated to Xcode 9 and TiSDK 6.2.1, and everything broke all together when I try to Package to ad hoc. This is the error I get: [TRACE] : Code Signing Error: No profile for team '6E5M3DGMBX' matching 'my cert adhoc' found: Xcode couldn't find any provisioning profiles matching '6E5M3DGMBX/my cert adhoc'. 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. [TRACE] : Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 11.0' (This was working fine until the update, so the certificates and the private keys are correctly imported) EDITED: The problem is that the project.pbxproj is created with the DEVELOPMENT_TEAM value set as the *bundle* identifier instead of the *Team* identifier. If you open the xcode project and then fix it from the General menu, the DEVELOPMENT_TEAM value will be eventually right.

Comments

  1. Chris Barber 2017-09-21

    The DEVELOPMENT_TEAM is set to the appPrefix from the selected provisioning profile which is the same thing as the team id. It should not be setting the bundle identifier. "6E5M3DGMBX" looks like a team id, not a bundle identifier. FWIW, I had the same problem and I simply need to recreate my provisioning profiles and things started working again. Furthermore, I submitted a PR yesterday for TIMOB-25318 which improves the provisioning profile validation to ensure that the selected developer/distribution cert is assigned to the selected provisioning profile. The goal is to fail as soon as possible. If you would please try recreating your provisioning profile and try again, then report back your results. If it works, then we can resolve this ticket. Thank you!
  2. Alberto Marcone 2017-09-22

    I did what you suggested but I get the same error. 6E5M3DGMBX is the appPrefix !https://imgur.com/zttL0li.png! but the team identifier is written right in the provisioning: TeamIdentifier 4V676W935X TeamName Company SRL TimeToLive 60 UUID 237a354d-XXX Version 1 If I open the Xcode project it's marked as an error: !https://imgur.com/hgHzHMl.png! and when I select the right provisioning it looks fixed: !https://imgur.com/bxGjlWO.png!
  3. Alberto Marcone 2017-09-22

    updating to 6.3.0.v20170921125635 didn't fix it. The ticket you linked seems the same error, I will watch it too!
  4. Hans Knöchel 2017-09-22

    Resolving as duplicate of TIMOB-25318. You can try out the 6_3_X branch today by using {{appc ti sdk install -b 6_3_X) or patch the SDK manually by using the pull-request referenced in the linked ticket. Thanks!
  5. Cameron 2017-09-23

    Ok I had the same exact problems as everyone else. Upgraded to 6.3.x as noted above by Hans. Problem is NOT solved. Still the same problem. I copied my project to a new folder and did a fresh import The freshly imported one doesn't even recognize my certificates and won't allow any kind of build what-so-ever (project can be built from Xcode but I have to manually select the certificates) Trying to archive directly in Xcode is no good since it doesn't package images or app.js for that matter. Stuck in a loop here
  6. Eric Merriman 2018-08-06

    Closing as a duplicate. If this is in error, please reopen.

JSON Source