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

Filip Maj commented on CB-4373:
-------------------------------

The ref counting or whatever you want to call it for config changes (xml / 
plist) already happen in prepare step. Extending that to support frameworks 
would happen in the same phase too.

If the user is already modifying the native project code then it doesn't matter 
when we do it: they'll have to do modifications manually anyways (whether we do 
the uninstall-all-frameworks-then-reinstall or the refcounting way).
                
> iOS .framework files need to be reference-counted
> -------------------------------------------------
>
>                 Key: CB-4373
>                 URL: https://issues.apache.org/jira/browse/CB-4373
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS, Plugman
>    Affects Versions: 3.0.0
>            Reporter: lmnbeyond
>            Assignee: Shazron Abdullah
>            Priority: Critical
>             Fix For: 3.1.0
>
>
> Steps to reproduce it:
> $ cordova create "HelloCordova"
> $ cd HelloCordova/
> $ cordova platform add ios
> $ cordova plugin add 
> https://git-wip-us.apache.org/repos/asf/cordova-plugin-splashscreen.git
> $ cordova emulate
> $ cordova plugin rm 'org.apache.cordova.core.splashscreen'
> $ cordova emulate
> [Error: An error occurred while emulating/deploying the ios project ....
> Undefined symbols for architecture i386:
>   "_CGRectZero", referenced from:
>       +[CDVUserAgentUtil originalUserAgent] in 
> libCordova.a(CDVUserAgentUtil.o)
> ld: symbol(s) not found for architecture i386
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> ** BUILD FAILED **
> The following build commands failed:
>       Ld build/HelloCordova.app/HelloCordova normal i386
> (1 failure)
> ]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to