Developer teams must have the same name (enterprise and business) so it's hard to distinguish between them

Originator:inbox
Number:rdar://15132786 Date Originated:02-Oct-2013 18:38
Status:Closed Resolved:
Product:Developer portal Product Version:
Classification:Serious bug Reproducible:Always
 
Summary:
Since each team must be registered from a DUNS number, both the names are exactly the same because the team name will take the company name from the DUNS account.

This makes it impossible to distinguish from the two teams when logging into the developer portal.

It also makes it really difficult when producing builds, since you have two certificates with the same name for each account. I often have to go into the keychain and delete one (by looking up the team ID). This certificate is often re-added back to the keychain by Xcode and doesn't always work.

"Code Sign error: Certificate identity 'iPhone Distribution: Company LTD' appears more than once in the keychain. The codesign tool requires there only be one."

Steps to Reproduce:
1. Create a developer team with a business account from a DUNS number
2. Create a secondary team for an enterprise account from the same DUNS number
3. Log into the Apple ID which is associated with these two teams.
4. You are taken to a "Select Your Team" screen at https://developer.apple.com/devcenter/selectTeam.action (see attached screenshot).

Expected Results:
Potentially naming the enterprise one "Company (Enterprise)" or providing some way to differentiate between them.

Actual Results:
Both teams have the exact same name, so you do not know which one is which.

Notes:
Please see the teams on the account "[redacted]".

Attachments:
'Screen Shot 2013-10-02 at 18.30.32.png' was successfully uploaded.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!