[ 
https://issues.apache.org/jira/browse/CB-13981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

jcesarmobile closed CB-13981.
-----------------------------
    Resolution: Invalid

Some plugin is trying to write on the old location of config.xml. The 
config.xml is now in another location.
Check if you have some hook trying to write there. The new location is 
platforms/android/app/src/main/res/xml/config.xml 


This also happens when a plugin uses source-file tag for copying resources like 
images. In that case you should update the plugins

> cp: copyFileSync: could not write to dest file (code=ENOENT)
> ------------------------------------------------------------
>
>                 Key: CB-13981
>                 URL: https://issues.apache.org/jira/browse/CB-13981
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-android
>    Affects Versions: cordova-android-7.0.0
>         Environment: cordova -v
> 8.0.0
> [email protected]
> Mac
>            Reporter: Arch
>            Assignee: Joe Bowser
>            Priority: Major
>
> I am seeing following error since the latest upgrade:
> >cordova build android
> cp: copyFileSync: could not write to dest file 
> (code=ENOENT):/Users/vkeepe/Dev/github/Keeper/platforms/android/res/xml/config.xml
>  Parsing /Users/vkeepe/Dev/github/Keeper/platforms/android/res/xml/config.xml 
> failed
> (node:56652) UnhandledPromiseRejectionWarning: Unhandled promise rejection 
> (rejection id: 1): Error: ENOENT: no such file or directory, open 
> '/Users/vkeepe/Dev/github/Keeper/platforms/android/res/xml/config.xml'
> (node:56652) [DEP0018] DeprecationWarning: Unhandled promise rejections are 
> deprecated. In the future, promise rejections that are not handled will 
> terminate the Node.js process with a non-zero exit code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to