Xcode signing issues due to Facebook Team ID being used by default in npm release

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Environment: OS: macOS High Sierra 10.13.1 Node: 9.2.0 Yarn: 1.3.2 npm: 5.5.1 Watchman: Not Found Xcode: Xcode 9.1 Build version 9B55 Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed) react: 16.0.0-beta.5 => 16.0.0-beta.5 react-native: ^0.49.5 => 0.49.5

Steps to Reproduce

1. Bootstrap a project using react-native init.
2. Build the project
3. Go to the issues navigator and observe all of the Update Signing issues.

Note: You will most likely have to do this with a version of Xcode that does not have access to Facebooks developer team as the issue will only be present for instances of Xcode that are not linked with Facebooks

Alternately

1. Bootstrap a project using react-native init
2. Navigate to node_modules/react-native/React/React.xcodeproj
3. Open project.pbxproj with your favorite editor and navigat eto lines 3420 - 3450 and note the lines with DevelopmentTeam = V9WTTPBFK9;

Expected Behavior

A new project does not have update signing errors

Actual Behavior

Because Facebooks DevelopmentTeam identifier is being published to npm there are tons of errors the editor reports which can be really difficult to track down. If the Developer ID lines were removed before publishing to npm Xcode would use what ever Developer ID is default for the user and they would not have to track down all the stray ID’s and fix them.

Reproducible Demo

Follow the Building Project with Native Code section.

Open the project with a version of Xcode that is not linked to Facebook’s Developer ID.

Navigate to the issues section and observe the update signing issues.

[Rojuinex]

It’s an error; the error won’t go away until you remove the DeveloperID from the Xcode project file.

And they just keep stacking up:

But after performing the aforementioned sed command it stops generating new errors.

[hammadzz]

If you see this error and can’t figure out what the hell is going on:

1. Delete all provisioning profiles in here

cd ~/Library/MobileDevice/Provisioning\ Profiles/
rm -rf *

1. Redownload provisioning profiles Xcode > Preferences > Accounts (select yours) > Download Manual Profiles

2. Celebrate