> I believe when you generate a project using Cordova it uses the static > library, so the framework issues will not appear in the typical workflow.
Yeah... I poked at the Cordova-ios.xcworkspace stuff last night, and by the end of it my changes looked almost identical to what you've got in #408. I was poking around at old JIRA issues last night and noticed [CB-13043](https://issues.apache.org/jira/browse/CB-13043) which suggests we might want to move to using Cordova.framework in all cases, but I'm a little bit concerned about the potential impact of that sort of change on 3rd party plugins and their header includes. @sgoldberg-sfdc I'll try to get what I did last night into a fully working state and push the changes here (and I'll attribute them to you, since they're basically identical to the work you already did), and then maybe look at adding a preference for an app to switch between the static and framework versions. [ Full content available at: https://github.com/apache/cordova-ios/pull/409 ] This message was relayed via gitbox.apache.org for [email protected]
