[ 
https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620037#comment-14620037
 ] 

Shazron Abdullah commented on CB-9273:
--------------------------------------

Regarding my last comment, this will *not* work anymore as soon as you install 
Xcode 7 beta 3. From the Release Notes:
{code}
Build System
• The Xcode build system no longer automatically inherits the environment used 
to launch the app when running in the IDE. This prevents unnecessary rebuilds 
when Xcode.app is opened from the command line. If necessary, users can opt-in 
to the old behavior by entering this command in Terminal:
      defaults write com.apple.dt.Xcode UseSanitizedBuildSystemEnvironment -bool
     NO
NOTE: For compatibility reasons, this behavior is not the default when running 
builds via xcodebuild. However, users who wish to interchange between building 
Xcode and building using xcodebuild can add the following argument:
       -UseSanitizedBuildSystemEnvironment=YES
on the command line to also use a sanitized environment in xcodebuild. 
(20668232)
{code}

Even if you load the project in Xcode 6.4, the above note still applies if you 
ever launched Xcode 7 even once. 

We *need* to find a solution for this asap.

> "Copy www build phase" node is not found
> ----------------------------------------
>
>                 Key: CB-9273
>                 URL: https://issues.apache.org/jira/browse/CB-9273
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>         Environment: cordova-ios 4.x
>            Reporter: Shazron Abdullah
>         Attachments: xcode-build-phase-node.png
>
>
> I have node installed using nvm, and the build phase cannot find node.
> The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's 
> environment variables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to