[jira] [Commented] (CB-12582) Plugin's Cocoapods don't persist if another plugin is added after it
[ https://issues.apache.org/jira/browse/CB-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603217#comment-16603217 ] Matthias commented on CB-12582: --- Hmm, interesting, didn't check the source. Still running into an issue with pods not found for linking with cordova-ios@4.5.5 Yeah, probably a different issue with cocoapod dependencies then. In my case a plugin actually installs a pod which itself has additional pods as dependencies which are not found for linking in the end. > Plugin's Cocoapods don't persist if another plugin is added after it > > > Key: CB-12582 > URL: https://issues.apache.org/jira/browse/CB-12582 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios >Affects Versions: cordova-ios@4.3.1, 6.5.0 >Reporter: Kyle Kirbatski >Assignee: Shazron Abdullah >Priority: Major > Labels: backlog > Fix For: cordova-ios@4.5.5 > > Attachments: 0001-exec-purgeProjectFileCache-when-pod-install.patch > > > I was trying to use the urbanairship-cordova plugin but was unable to because > the frameworks added by Cocoapods (referenced from the plugin's xml) were not > being found for linking. After some investigation it appears that if a plugin > is added after a plugin that uses cocoapods then the changes made by > cocoapods are removed by cordova. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12582) Plugin's Cocoapods don't persist if another plugin is added after it
[ https://issues.apache.org/jira/browse/CB-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603184#comment-16603184 ] Matthias commented on CB-12582: --- Since the change has been [reverted|https://github.com/apache/cordova-ios/commit/15246c9d627a633847a2e62dce14190ac443f390], can the issue be reopened? > Plugin's Cocoapods don't persist if another plugin is added after it > > > Key: CB-12582 > URL: https://issues.apache.org/jira/browse/CB-12582 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios >Affects Versions: cordova-ios@4.3.1, 6.5.0 >Reporter: Kyle Kirbatski >Assignee: Shazron Abdullah >Priority: Major > Labels: backlog > Fix For: cordova-ios@4.5.5 > > Attachments: 0001-exec-purgeProjectFileCache-when-pod-install.patch > > > I was trying to use the urbanairship-cordova plugin but was unable to because > the frameworks added by Cocoapods (referenced from the plugin's xml) were not > being found for linking. After some investigation it appears that if a plugin > is added after a plugin that uses cocoapods then the changes made by > cocoapods are removed by cordova. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12492) plugin.xml edit-config not working for attributes on manifest/application
Matthias created CB-12492:
-
Summary: plugin.xml edit-config not working for attributes on
manifest/application
Key: CB-12492
URL: https://issues.apache.org/jira/browse/CB-12492
Project: Apache Cordova
Issue Type: Bug
Components: Android, CordovaCommon
Affects Versions: 2.0.0
Reporter: Matthias
h3. Environment
Cordova: 6.5.0
CordovaCommon: 2.0.0
CordovaAndroid: 6.1.2
h3. Description
Using the edit-config in a plugin.xml to add an additional attribute on the
manifest or application tag in AndroidManifest.xml does not work.
h3. Steps to reproduce
- Create new cordova project with android platform
- (Copy initial AndroidManifest.xml for comparison)
- Add cordova plugin which uses the edit-config setting to add a new attribute
to manifest or application tag
- Compare updated AndroidManifist.xml and see attribute was not added
h3. Expectation
Edit-config setting in plugin.xml allows to add/alter as well attributes on
manifest/application/... level in AndroidManifest.xml
h3. Example
This will work
{code:xml}
{code}
This will *NOT* work
{code:xml}
http://schemas.android.com/tools";>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
