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

Kelvin Dart updated CB-12106:
-----------------------------
    Description: 
Android resources are not copied correctly when specified in config.xml

Info:
I have created a basic app to illustrate the issue, if you clone the following 
URL and follow the instructions below, you will see: 
https://github.com/kelvindart/CordovaAndroidResources

Issue:
Running `cordova prepare` or `cordova build` does not seem to move the 
specified resources correctly, and removes them to the root of the project, not 
within the android project.

Expecting:
`resources` to be merged in `platforms/android/res/` after running one of the 
above two commands.

Steps to reproduce:

#Clone the following Git repo: 
https://github.com/kelvindart/CordovaAndroidResources
#Run `cordova prepare`.
#Observe a newly created folder in `./` named `res` - inside here are android 
folders for the various screen sizes, containing your resources specified in 
`config.xml`
#Further note, in `./platforms/android/res/` the old resources are still 
present.

(N.b. I am unable to add the relevant [email protected] tags.)

  was:
Android resources are not copied correctly when specified in config.xml

Info:
I have created a basic app to illustrate the issue, if you clone the following 
URL and follow the instructions below, you will see: 
https://github.com/kelvindart/CordovaAndroidResources

Issue:
Running `cordova prepare` or `cordova build` does not seem to move the 
specified resources correctly, and removes them to the root of the project, not 
within the android project.

Expecting:
`resources` to be merged in `platforms/android/res/` after running one of the 
above two commands.

Steps to reproduce

1. Clone the following Git repo: 
https://github.com/kelvindart/CordovaAndroidResources
2. Run `cordova prepare`.
3. Observe a newly created folder in `./` named `res` - inside here are android 
folders for the various screen sizes, containing your resources specified in 
`config.xml`
4. Further note, in `./platforms/android/res/` the old resources are still 
present.

(N.b. I am unable to add the relevant [email protected] tags.)


> Android resources not copied correctly when specified in config.xml
> -------------------------------------------------------------------
>
>                 Key: CB-12106
>                 URL: https://issues.apache.org/jira/browse/CB-12106
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android, CLI
>    Affects Versions: [email protected]
>         Environment: Cordova CLI: 6.4.0
> OS: Mac OS X Sierra
> Node Version: v7.0.0
> Cordova Android: 6.0.0
>            Reporter: Kelvin Dart
>              Labels: android, cordova-android-osx, cordova-cli
>
> Android resources are not copied correctly when specified in config.xml
> Info:
> I have created a basic app to illustrate the issue, if you clone the 
> following URL and follow the instructions below, you will see: 
> https://github.com/kelvindart/CordovaAndroidResources
> Issue:
> Running `cordova prepare` or `cordova build` does not seem to move the 
> specified resources correctly, and removes them to the root of the project, 
> not within the android project.
> Expecting:
> `resources` to be merged in `platforms/android/res/` after running one of the 
> above two commands.
> Steps to reproduce:
> #Clone the following Git repo: 
> https://github.com/kelvindart/CordovaAndroidResources
> #Run `cordova prepare`.
> #Observe a newly created folder in `./` named `res` - inside here are android 
> folders for the various screen sizes, containing your resources specified in 
> `config.xml`
> #Further note, in `./platforms/android/res/` the old resources are still 
> present.
> (N.b. I am unable to add the relevant [email protected] tags.)



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