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

Darryl Pogue commented on CB-11803:
-----------------------------------

Ugh, this is one of the reasons that I want to separate prepare and restore, 
because there are all these cases that aren't captured in tests or 
documentation anywhere and trying to fix anything results in breaking 
expectations.

However, I thought this particular case was already fixed by CB-11698?

> Plugin features don't get written to iOS-specific config.xml
> ------------------------------------------------------------
>
>                 Key: CB-11803
>                 URL: https://issues.apache.org/jira/browse/CB-11803
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI, iOS, Plugins
>    Affects Versions: 6.3.1
>            Reporter: Matus Koprda
>            Priority: Critical
>
> When running `cordova prepare` or `cordova platform add ios` after adding 
> plugins, the platform-specific config.xml file for iOS 
> (`platforms/ios/NAME/config.xml`) doesn't have `<feature>` tags, which 
> effectively prevents any installed plugin from working.
> The tags *do* get added when installing plugins *after* the iOS platform was 
> created.
> How to reproduce - this creates a working config.xml:
> {code}
>       cordova create test
>       cd test
>       cordova platform add ios
>       cordova plugin add cordova-plugin-device --save
> {code}
> This creates a broken config.xml (resulting in `Plugin 'Device' not found, or 
> is not a CDVPlugin.` error when running on a an iPhone):
> {code}
>       cordova create test
>       cd test
>       cordova plugin add cordova-plugin-device --save
>       cordova platform add ios
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to