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

Alex Buijs commented on CB-12191:
---------------------------------

You are right, I'm sorry, the problem is related to a plugin messing with the 
CODE_SIGN_ENTITLEMENTS variable... This issue can be closed.

> Entitlements.plist missing from resources resources
> ---------------------------------------------------
>
>                 Key: CB-12191
>                 URL: https://issues.apache.org/jira/browse/CB-12191
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>            Reporter: Alex Buijs
>              Labels: ios10
>
> Since CB-11854, my builds fail. Specifically, xcodebuild fails to find the 
> Entitlements-Release.plist file in the resources directory. This is the error 
> message I am getting:
> {code}
> CopyPlistFile 
> Build/Intermediates/ArchiveIntermediates/App/InstallationBuildProductsLocation/Applications/App.app/Entitlements-Release.plist
>  App/Resources/Entitlements-Release.plist
>     cd platforms/ios
>     builtin-copyPlist --convert binary1 --outdir 
> /Users/buijs/Library/Developer/Xcode/DerivedData/App-gkrrnbcilhcownetcuuhlwrvlwwd/Build/Intermediates/ArchiveIntermediates/App/InstallationBuildProductsLocation/Applications/App.app
>  -- App/Resources/Entitlements-Release.plist
> App/Resources/Entitlements-Release.plist:0: error: reading data: The file 
> “Entitlements-Release.plist” couldn’t be opened because there is no such file.
> {code}
> Is there a copy step missing from the build proces?
> The entitlements file is correctly generated at 
> $(PROJECT_DIR)/$(PROJECT_NAME)/Entitlements-$(CONFIGURATION).plist, but 
> xcodebuild expects it's path to be: 
> $(PROJECT_DIR)/$(PROJECT_NAME)/Resources/Entitlements-$(CONFIGURATION).plist



--
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