Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XCode11 can not find "Build Location -> Per-configuration Build Products Path -> Staging " #1782

Closed
whereiscode opened this issue Feb 5, 2020 · 10 comments
Assignees
Labels

Comments

@whereiscode
Copy link

XCode11 can not find "Build Location -> Per-configuration Build Products Path -> Staging "

Environment

  • react-native-code-push version:6.0.0
  • react-native version:0.61.5
  • iOS/Android/Windows version:IOS
  • Does this reproduce on a debug build or release build? debug
  • Does this reproduce on a simulator, or only on a physical device? simulator
@hemith
Copy link

hemith commented Feb 10, 2020

Same here. "Build Location -> Per-configuration Build Products Path" is not exist (xcode 11.3.1)

@hemith
Copy link

hemith commented Feb 10, 2020

It works.

Basically, follow this doc.
https://github.com/microsoft/react-native-code-push/blob/master/docs/multi-deployment-testing-ios.md
1.
2.
3.
4.
5.
6.
7. Add CONFIGURATION_BUILD_DIR using "Add User-Defined Setting" in Build Settings
instead of Per-configuration Build Products Path
8.
9.
10.
11. pod install
12. set post install - #426

in Xcode Help Document (Xcode Help in xcode menu)

Per-configuration Build Products Path (CONFIGURATION_BUILD_DIR)
The base path where build products will be placed during a build for a given configuration. By default, this is set to $(BUILD_DIR)/$(CONFIGURATION).

@andreidubov andreidubov self-assigned this Feb 11, 2020
@andreidubov andreidubov removed their assignment Feb 11, 2020
@yuri-kulikov yuri-kulikov self-assigned this Feb 11, 2020
@yuri-kulikov
Copy link
Contributor

Hey @whereiscode,
Sorry for the delay.

I hope @hemith answere helped you, so I'll close the issue for now, but if you still have any questions, feel free to reopen it.

@MutableLoss
Copy link

Are there plans to revise the multi-deployment documentation to mention this update for XCode 11?

@sinn1
Copy link

sinn1 commented Mar 29, 2020

Had to add the values for Debug, Release and Staging before setting the name to 'CONFIGURATION_BUILD_DIR' otherwise XCode would crash. I think it didn't like empty values.

Debug + Release: $(BUILD_DIR)/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)

As per docs:
Staging: $(BUILD_DIR)/Release$(EFFECTIVE_PLATFORM_NAME)

@natuanorg
Copy link

@sinn1 thank you

@erez-guesty
Copy link

@hemith
About step 12. set post install - #426
inside this PR (#426 ) they instruct to add a snippet to Podfile
with the config key CONFIGURATION_TEMP_DIR
But i don't see any related to this key in the Build Settings...
Should it be added??

@hemith
Copy link

hemith commented May 20, 2020

@erez-guesty
Skip Step 12. It is not necessary.

@walterwing
Copy link

For people who also need to update Pod dependencies but couldn't use pod install for whatever reason, have a try to update PODS_CONFIGURATION_BUILD_DIR under "Build Settings" -> "User-Defined".

Similar like what you did for CONFIGURATION_BUILD_DIR , update the value for your new config as: ${PODS_BUILD_DIR}/Release$(EFFECTIVE_PLATFORM_NAME)

@ghost
Copy link

ghost commented Jun 30, 2020

Had to add the values for Debug, Release and Staging before setting the name to 'CONFIGURATION_BUILD_DIR' otherwise XCode would crash. I think it didn't like empty values.

Debug + Release: $(BUILD_DIR)/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)

As per docs:
Staging: $(BUILD_DIR)/Release$(EFFECTIVE_PLATFORM_NAME)

Our project wasn't crashing, but it was having some build issues. Specifically this error: Library not found for -lPods-App, this fixed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants