Skip to content

Build with own configuration in wrong Build/Products folder #17650

Description

@lukaszgoworko

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment:

OS: macOS High Sierra 10.13.2
Node: 9.3.0
Yarn: 1.3.2
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 2.3 AI-162.3764568

Packages: (wanted => installed)

react: 16.0.0 => 16.0.0
react-native: 0.50.3 => 0.50.3

dependencies
"apisauce": "^0.14.1",
"babel-core": "^6.26.0",
"babel-plugin-transform-builtin-extend": "^1.1.2",
"hoist-non-react-statics": "^2.3.1",
"immutability-helper": "^2.4.0",
"lodash": "^4.17.4",
"moment": "^2.19.1",
"prop-types": "^15.6.0",
"react": "16.0.0",
"react-native": "0.50.3",
"react-native-config": "^0.10.0",
"react-native-device-info": "^0.12.1",
"react-native-elements": "^0.16.0",
"react-native-fetch-blob": "^0.10.8",
"react-native-fs": "^2.9.6",
"react-native-html-to-pdf": "^0.4.0",
"react-native-icon-badge": "^1.1.3",
"react-native-message-bar": "^2.0.1",
"react-native-offline": "^3.2.0",
"react-native-print": "^0.3.0",
"react-native-radio-buttons": "^1.0.0",
"react-native-router-flux": "4.0.0-beta.24",
"react-native-sha256": "^1.1.1",
"react-native-vector-icons": "^4.4.0",
"react-navigation": "^1.0.0-beta.15",
"react-redux": "^5.0.5",
"redux": "^3.7.0",
"redux-persist": "^5.2.0",
"redux-thunk": "^2.2.0",
"tcomb-form-native": "^0.6.8",
"uuid": "^3.1.0"
devDependencies
"babel-eslint": "^8.0.1",
"babel-jest": "21.2.0",
"babel-preset-react-native": "4.0.0",
"eslint": "^4.9.0",
"eslint-config-airbnb": "^16.1.0",
"eslint-plugin-flowtype": "^2.39.0",
"eslint-plugin-import": "^2.8.0",
"eslint-plugin-jsx-a11y": "^6.0.2",
"eslint-plugin-react": "^7.4.0",
"flow-bin": "^0.56.0",
"jest": "21.2.1",
"nock": "^9.0.14",
"react-test-renderer": "16.0.0-beta.5",
"redux-devtools": "^3.4.0",
"redux-mock-store": "^1.3.0"

Target Platform: iOS (8.0)

Steps to Reproduce

Creating new configuration and scheme in Xcode with own icons, name, and app-ID. Change debug configuration.

(Write your steps here:)

  1. Dublicate Configuration "Release" => Named Staging
  2. Add new IconsSets => AppIconStaging and AppIconDebug
  3. Change Target Build Settings
    1. ASSETCATALOG_COMPILER_APPICON_NAME
      • Debug: AppIconDebug
      • Staging: AppIconStaging
      • Release: AppIconRelease
    2. PRODUCT_BUNDLE_IDENTIFIER
      • different for every configuration
    3. PRODUCT_NAME
      • different for every configuration
  4. Dublicate Scheme => named: ProjectDebug and ProjectStaging
  5. Edit Schemes
    1. Set Build Settings for Run, Profile and Archive
      • ProjectDebug => Debug
      • ProjectStaging => Staging

At this Point trying to run ProjectStaging on Simulator fails because the build fails.
I have noticed, that when building ProjectStaging with Staging configuration on an fresh git clone of my project, some files are build in ios/build/Build/Products/Release-iphonesimulator.

Because of this files the build fails, they can't be found in the Staging-iphonesimulator folder.

There are some links to solutions by changing some build settings for Staging configuration

Changing: Header Search Paths, Framework Search Paths, Library Search Paths and User Header Search Paths to
$(BUILD_DIR)/Release$(EFFECTIVE_PLATFORM_NAME)

Now all scheme builds failing when trying to run from Xcode:
/Volumes/Workspace/Projects/Project/ios/ProjectTests/ProjectTests.m:11:9: 'XCTest/XCTest.h' file not found

Running from console:
node node_modules/react-native/local-cli/cli.js run-ios --device --scheme ProjectStaging --configuration Staging
Build fails because of same issue, but App is installed and running well (cant find any errors for now)

Building archive always working

Expected Behavior

Project files for a configuration are in their own folder, so the build is always ok.

Actual Behavior

Correct Build with all files in the right place

Metadata

Metadata

Assignees

No one assigned

    Labels

    Ran CommandsOne of our bots successfully processed a command.Resolution: LockedThis issue was locked by the bot.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions