[jira] [Commented] (CB-14045) iOS 11.3 - app freeze/sleep
[ https://issues.apache.org/jira/browse/CB-14045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575079#comment-16575079 ] Doug Davies commented on CB-14045: -- Did this make it into cordova-ios@4.5.5? > iOS 11.3 - app freeze/sleep > --- > > Key: CB-14045 > URL: https://issues.apache.org/jira/browse/CB-14045 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios >Affects Versions: cordova@7.1.0, cordova-ios@4.5.4 >Reporter: Robert >Priority: Blocker > Labels: ios, ios11, lock, performance, sleep > > Users with iOS 11.3 can’t use the app when device is locked for more than 10 > minutes. > Event onResume not firing. > Steps to Reproduce: > Install Fitatu app. > Open app on any view. > Lock the device for more than 10 minutes. > After 10 minutes, unlock device. > Expected Results: > App wakes up and the UI is responding (e.g. user is able to click buttons) > Actual Results: > App wakes up and the UI is blocked (user is not able to click buttons) -- 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-12922) [iOS] In-app browser does not cede control after actions on certain pages
[ https://issues.apache.org/jira/browse/CB-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525490#comment-16525490 ] Doug Davies commented on CB-12922: -- Ya, I hate to go back to an earlier version. We needed some of the stuff in 3.0.0. We used 1.6.x for quite a while but recently upgraded. I'd like to figure out what changed. > [iOS] In-app browser does not cede control after actions on certain pages > - > > Key: CB-12922 > URL: https://issues.apache.org/jira/browse/CB-12922 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-inappbrowser >Reporter: Ben Williams >Priority: Critical > Attachments: nest_iab.zip > > > This issue only occurs on the iOS version of inappbrowser. > When opening the Nest login (https://home.nest.com/login/) page in the > inappbrowser, clicking Sign In (with or without valid credentials) and > subsequently closing the browser, the main cordova page becomes unresponsive, > receiving no touch events whatsoever. > I have created a barebones application which exhibits the issue, which I will > attach. > Thank you. -- 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-12922) [iOS] In-app browser does not cede control after actions on certain pages
[ https://issues.apache.org/jira/browse/CB-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525483#comment-16525483 ] Doug Davies commented on CB-12922: -- This one is biting me as well. > [iOS] In-app browser does not cede control after actions on certain pages > - > > Key: CB-12922 > URL: https://issues.apache.org/jira/browse/CB-12922 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-inappbrowser >Reporter: Ben Williams >Priority: Critical > Attachments: nest_iab.zip > > > This issue only occurs on the iOS version of inappbrowser. > When opening the Nest login (https://home.nest.com/login/) page in the > inappbrowser, clicking Sign In (with or without valid credentials) and > subsequently closing the browser, the main cordova page becomes unresponsive, > receiving no touch events whatsoever. > I have created a barebones application which exhibits the issue, which I will > attach. > Thank you. -- 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-11665) Navigation to Fragment locations within Webview are parsed as an error
[ https://issues.apache.org/jira/browse/CB-11665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525456#comment-16525456 ] Doug Davies commented on CB-11665: -- I'm having this same issue, but it is affecting cordova-plugin-inappbrowser of all places. Seems like progress on this has stalled? > Navigation to Fragment locations within Webview are parsed as an error > -- > > Key: CB-11665 > URL: https://issues.apache.org/jira/browse/CB-11665 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios > Environment: cordova-ios >Reporter: Brian Anderson >Priority: Major > Labels: easyfix > Original Estimate: 1h > Remaining Estimate: 1h > > In the CDVUIWebviewDelegate if a fragment is loaded on a url the > shouldStartLoadWithRequest gets called and sets the _state to > STATE_WAITING_FOR_LOAD_START. Being that when a fragment is loaded the > didStartLoading and didFinishLoading callbacks are not called, the next time > a link is clicked within our WebView the _state doesn't match any cases, > falls into the default case which then handles the request as an error by > explicitly calling didFailLoadWithError. I am curious if this is by design as > I do notice that STATE_IOS5_POLLING_FOR_LOAD_START is handled in > shouldStartLoadWithRequest. Is there a specific case that we would actually > want to throw an error? > My suggestion for fixing this would be to add STATE_WAITING_FOR_LOAD_START to > the same fall through case as STATE_IDLE, STATE_IOS5_POLLING_FOR_LOAD_START, > STATE_CANCELLED. Which would basically just reset the state and loadCount > seeing as we have essentially 'cancelled' that pending request from the eyes > of cordova. > Hoping to get more information about these decisions. -- 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-14093) Setting a viewport scale factor causes page to be draggable
[
https://issues.apache.org/jira/browse/CB-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478470#comment-16478470
]
Doug Davies commented on CB-14093:
--
Hmmm... ok I'll play around some more with this. Thanks for the
explanation. It is strange though that 1.14 would differ from 1.13. I would
think both would cause the viewport to extend past the device width.
> Setting a viewport scale factor causes page to be draggable
> ---
>
> Key: CB-14093
> URL: https://issues.apache.org/jira/browse/CB-14093
> Project: Apache Cordova
> Issue Type: Bug
>Reporter: Doug Davies
>Priority: Major
>
> I'm using Cordova 8.0.0. When I set the following viewport meta tag
>
> The screen is draggable (at least on Android). If I change to 1.14, then it
> is not. It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13,
> 1.15, 1.16 don’t.
> You can reproduce this as follows:
> {code:java}
> cordova create demo
> cd demo
> cordova add platform android@7.1.0
> change viewport in index.html to
>
> cordova run android
> {code}
> My real app does this dynamically so that tablets scale the UI up
> appropriately. I swear this has been working until recently, but I can't say
> for sure. On iOS the viewport-fit=cover seems to be taking care of this,
> although I didn't add that until I needed iPhone X support.
> Copying [~wtrocki] as instructed.
> I tried this on iOS and without that it also scrolled around. So not sure in
> what component the problem lies.
> I've tried this on a stand-alone (non-cordova page) and it ALWAYS seems to be
> scrolling. So Cordova must be intervening and helping at least some of the
> time.
> Here's the pages I was attempting
> [http://funkyvisions.github.io/index1.html]
> [http://funkyvisions.github.io/index1.13.html]
> [http://funkyvisions.github.io/index1.14.html]
> [http://funkyvisions.github.io/index2.0.html]
>
--
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] [Updated] (CB-14093) Setting a viewport scale factor causes page to be draggable
[
https://issues.apache.org/jira/browse/CB-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Davies updated CB-14093:
-
Description:
I'm using Cordova 8.0.0. When I set the following viewport meta tag
The screen is draggable (at least on Android). If I change to 1.14, then it is
not. It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13,
1.15, 1.16 don’t.
You can reproduce this as follows:
{code:java}
cordova create demo
cd demo
cordova add platform android@7.1.0
change viewport in index.html to
cordova run android
{code}
My real app does this dynamically so that tablets scale the UI up
appropriately. I swear this has been working until recently, but I can't say
for sure. On iOS the viewport-fit=cover seems to be taking care of this,
although I didn't add that until I needed iPhone X support.
Copying [~wtrocki] as instructed.
I tried this on iOS and without that it also scrolled around. So not sure in
what component the problem lies.
I've tried this on a stand-alone (non-cordova page) and it ALWAYS seems to be
scrolling. So Cordova must be intervening and helping at least some of the
time.
Here's the pages I was attempting
[http://funkyvisions.github.io/index1.html]
[http://funkyvisions.github.io/index1.13.html]
[http://funkyvisions.github.io/index1.14.html]
[http://funkyvisions.github.io/index2.0.html]
was:
I'm using Cordova 8.0.0. When I set the following viewport meta tag
The screen is draggable (at least on Android). If I change to 1.14, then it is
not. It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13,
1.15, 1.16 don’t.
You can reproduce this as follows:
{code:java}
cordova create demo
cd demo
cordova add platform android@7.1.0
change viewport in index.html to
cordova run android
{code}
My real app does this dynamically so that tablets scale the UI up
appropriately. I swear this has been working until recently, but I can't say
for sure. On iOS the viewport-fit=cover seems to be taking care of this,
although I didn't add that until I needed iPhone X support.
Copying [~wtrocki] as instructed.
I tried this on iOS and without that it also scrolled around. So not sure in
what component the problem lies.
I've tried this on a stand-alone (non-cordovan page) and it ALWAYS seems to be
scrolling. So Cordova must be intervening and helping at least some of the
time.
> Setting a viewport scale factor causes page to be draggable
> ---
>
> Key: CB-14093
> URL: https://issues.apache.org/jira/browse/CB-14093
> Project: Apache Cordova
> Issue Type: Bug
>Reporter: Doug Davies
>Priority: Major
>
> I'm using Cordova 8.0.0. When I set the following viewport meta tag
>
> The screen is draggable (at least on Android). If I change to 1.14, then it
> is not. It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13,
> 1.15, 1.16 don’t.
> You can reproduce this as follows:
> {code:java}
> cordova create demo
> cd demo
> cordova add platform android@7.1.0
> change viewport in index.html to
>
> cordova run android
> {code}
> My real app does this dynamically so that tablets scale the UI up
> appropriately. I swear this has been working until recently, but I can't say
> for sure. On iOS the viewport-fit=cover seems to be taking care of this,
> although I didn't add that until I needed iPhone X support.
> Copying [~wtrocki] as instructed.
> I tried this on iOS and without that it also scrolled around. So not sure in
> what component the problem lies.
> I've tried this on a stand-alone (non-cordova page) and it ALWAYS seems to be
> scrolling. So Cordova must be intervening and helping at least some of the
> time.
> Here's the pages I was attempting
> [http://funkyvisions.github.io/index1.html]
> [http://funkyvisions.github.io/index1.13.html]
> [http://funkyvisions.github.io/index1.14.html]
> [http://funkyvisions.github.io/index2.0.html]
>
--
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] [Updated] (CB-14093) Setting a viewport scale factor causes page to be draggable
[
https://issues.apache.org/jira/browse/CB-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Davies updated CB-14093:
-
Description:
I'm using Cordova 8.0.0. When I set the following viewport meta tag
The screen is draggable (at least on Android). If I change to 1.14, then it is
not. It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13,
1.15, 1.16 don’t.
You can reproduce this as follows:
{code:java}
cordova create demo
cd demo
cordova add platform android@7.1.0
change viewport in index.html to
cordova run android
{code}
My real app does this dynamically so that tablets scale the UI up
appropriately. I swear this has been working until recently, but I can't say
for sure. On iOS the viewport-fit=cover seems to be taking care of this,
although I didn't add that until I needed iPhone X support.
Copying [~wtrocki] as instructed.
I tried this on iOS and without that it also scrolled around. So not sure in
what component the problem lies.
I've tried this on a stand-alone (non-cordovan page) and it ALWAYS seems to be
scrolling. So Cordova must be intervening and helping at least some of the
time.
was:
I'm using Cordova 7.1.0. When I set the following viewport meta tag
The screen is draggable. If I change to 1.14, then it is not.
You can reproduce this as follows:
{code:java}
cordova create demo
cd demo
cordova add platform android@7.1.0
change viewport in index.html to
cordova run android
{code}
My real app does this dynamically so that tablets scale the UI up
appropriately. I swear this has been working until recently, but I can't say
for sure. On iOS the viewport-fit=cover seems to be taking care of this,
although I didn't add that until I needed iPhone X support.
Copying [~wtrocki] as instructed.
I tried this on iOS and without that it also scrolled around. So not sure in
what component the problem lies.
It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13, 1.15, 1.16
don’t
I've tried this on a stand-alone (non-cordovan page) and it ALWAYS seems to be
scrolling. So Cordova must be intervening and helping at least some of the
time.
> Setting a viewport scale factor causes page to be draggable
> ---
>
> Key: CB-14093
> URL: https://issues.apache.org/jira/browse/CB-14093
> Project: Apache Cordova
> Issue Type: Bug
>Reporter: Doug Davies
>Priority: Major
>
> I'm using Cordova 8.0.0. When I set the following viewport meta tag
>
> The screen is draggable (at least on Android). If I change to 1.14, then it
> is not. It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13,
> 1.15, 1.16 don’t.
> You can reproduce this as follows:
> {code:java}
> cordova create demo
> cd demo
> cordova add platform android@7.1.0
> change viewport in index.html to
>
> cordova run android
> {code}
> My real app does this dynamically so that tablets scale the UI up
> appropriately. I swear this has been working until recently, but I can't say
> for sure. On iOS the viewport-fit=cover seems to be taking care of this,
> although I didn't add that until I needed iPhone X support.
> Copying [~wtrocki] as instructed.
> I tried this on iOS and without that it also scrolled around. So not sure in
> what component the problem lies.
> I've tried this on a stand-alone (non-cordovan page) and it ALWAYS seems to
> be scrolling. So Cordova must be intervening and helping at least some of
> the time.
--
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] [Updated] (CB-14093) Setting a viewport scale factor causes page to be draggable
[
https://issues.apache.org/jira/browse/CB-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Davies updated CB-14093:
-
Summary: Setting a viewport scale factor causes page to be draggable (was:
Setting a viewport scale factor on Android causes issues)
> Setting a viewport scale factor causes page to be draggable
> ---
>
> Key: CB-14093
> URL: https://issues.apache.org/jira/browse/CB-14093
> Project: Apache Cordova
> Issue Type: Bug
>Reporter: Doug Davies
>Priority: Major
>
> I'm using Cordova 7.1.0. When I set the following viewport meta tag
>
> The screen is draggable. If I change to 1.14, then it is not.
> You can reproduce this as follows:
> {code:java}
> cordova create demo
> cd demo
> cordova add platform android@7.1.0
> change viewport in index.html to
>
> cordova run android
> {code}
> My real app does this dynamically so that tablets scale the UI up
> appropriately. I swear this has been working until recently, but I can't say
> for sure. On iOS the viewport-fit=cover seems to be taking care of this,
> although I didn't add that until I needed iPhone X support.
> Copying [~wtrocki] as instructed.
> I tried this on iOS and without that it also scrolled around. So not sure in
> what component the problem lies.
> It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13, 1.15,
> 1.16 don’t
> I've tried this on a stand-alone (non-cordovan page) and it ALWAYS seems to
> be scrolling. So Cordova must be intervening and helping at least some of
> the time.
--
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] [Updated] (CB-14093) Setting a viewport scale factor on Android causes issues
[
https://issues.apache.org/jira/browse/CB-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Davies updated CB-14093:
-
Description:
I'm using Cordova 7.1.0. When I set the following viewport meta tag
The screen is draggable. If I change to 1.14, then it is not.
You can reproduce this as follows:
{code:java}
cordova create demo
cd demo
cordova add platform android@7.1.0
change viewport in index.html to
cordova run android
{code}
My real app does this dynamically so that tablets scale the UI up
appropriately. I swear this has been working until recently, but I can't say
for sure. On iOS the viewport-fit=cover seems to be taking care of this,
although I didn't add that until I needed iPhone X support.
Copying [~wtrocki] as instructed.
I tried this on iOS and without that it also scrolled around. So not sure in
what component the problem lies.
It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13, 1.15, 1.16
don’t
I've tried this on a stand-alone (non-cordovan page) and it ALWAYS seems to be
scrolling. So Cordova must be intervening and helping at least some of the
time.
was:
I'm using Cordova 7.1.0. When I set the following viewport meta tag
The screen is draggable. If I change to 1.14, then it is not.
You can reproduce this as follows:
{code:java}
cordova create demo
cd demo
cordova add platform android@7.1.0
change viewport in index.html to
cordova run android
{code}
My real app does this dynamically so that tablets scale the UI up
appropriately. I swear this has been working until recently, but I can't say
for sure. On iOS the viewport-fit=cover seems to be taking care of this,
although I didn't add that until I needed iPhone X support.
Copy [~wtrocki] as instructed.
I tried this on iOS and without that it also scrolled around. So not sure in
what component the problem lies.
> Setting a viewport scale factor on Android causes issues
>
>
> Key: CB-14093
> URL: https://issues.apache.org/jira/browse/CB-14093
> Project: Apache Cordova
> Issue Type: Bug
>Reporter: Doug Davies
>Priority: Major
>
> I'm using Cordova 7.1.0. When I set the following viewport meta tag
>
> The screen is draggable. If I change to 1.14, then it is not.
> You can reproduce this as follows:
> {code:java}
> cordova create demo
> cd demo
> cordova add platform android@7.1.0
> change viewport in index.html to
>
> cordova run android
> {code}
> My real app does this dynamically so that tablets scale the UI up
> appropriately. I swear this has been working until recently, but I can't say
> for sure. On iOS the viewport-fit=cover seems to be taking care of this,
> although I didn't add that until I needed iPhone X support.
> Copying [~wtrocki] as instructed.
> I tried this on iOS and without that it also scrolled around. So not sure in
> what component the problem lies.
> It seems very random… 1.11, 1.12, 1.14, 1.17, 1.18, 1.19 work… 1.13, 1.15,
> 1.16 don’t
> I've tried this on a stand-alone (non-cordovan page) and it ALWAYS seems to
> be scrolling. So Cordova must be intervening and helping at least some of
> the time.
--
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-14093) Setting a viewport scale factor on Android causes issues
Doug Davies created CB-14093:
Summary: Setting a viewport scale factor on Android causes issues
Key: CB-14093
URL: https://issues.apache.org/jira/browse/CB-14093
Project: Apache Cordova
Issue Type: Bug
Reporter: Doug Davies
I'm using Cordova 7.1.0. When I set the following viewport meta tag
The screen is draggable. If I change to 1.14, then it is not.
You can reproduce this as follows:
{code:java}
cordova create demo
cd demo
cordova add platform android@7.1.0
change viewport in index.html to
cordova run android
{code}
My real app does this dynamically so that tablets scale the UI up
appropriately. I swear this has been working until recently, but I can't say
for sure. On iOS the viewport-fit=cover seems to be taking care of this,
although I didn't add that until I needed iPhone X support.
Copy [~wtrocki] as instructed.
I tried this on iOS and without that it also scrolled around. So not sure in
what component the problem lies.
--
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] [Comment Edited] (CB-14009) Build fails on Xcode 9.3
[
https://issues.apache.org/jira/browse/CB-14009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444357#comment-16444357
]
Doug Davies edited comment on CB-14009 at 4/19/18 4:41 PM:
---
I wonder how we get someone to look at this? I just sent a Slack message to
[~surajpindoria]. We'll see what he says.
was (Author: csddavies):
I wonder how we get someone to look at this?
> Build fails on Xcode 9.3
>
>
> Key: CB-14009
> URL: https://issues.apache.org/jira/browse/CB-14009
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Reporter: Doug Davies
>Assignee: Suraj Pindoria
>Priority: Major
>
> Seeing this after I update to XCode 9.3 and build through cli
> Error Domain=IDEProfileLocatorErrorDomain Code=1 “No profiles for
> ‘org.oclc.digby’ were found” UserInfo=\{NSLocalizedDescription=No profiles
> for ‘org.oclc.digby’ were found, NSLocalizedRecoverySuggestion=Xcode couldn’t
> find any iOS Ad Hoc provisioning profiles matching ‘org.oclc.digby’.
> Automatic signing is disabled and unable to generate a profile. To enable
> automatic signing, pass -allowProvisioningUpdates to xcodebuild.}
> When I bring the project up in XCode the signing is correct and not
> complaining.
> I tried adding
> “buildFlag”: [“-allowProvisioningUpdates”]
> to build.json and still not working
> Interestingly… I went into xcode and did an archive/export from there… now
> the cli works… it must set something that it needs
--
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-14009) Build fails on Xcode 9.3
[
https://issues.apache.org/jira/browse/CB-14009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444357#comment-16444357
]
Doug Davies commented on CB-14009:
--
I wonder how we get someone to look at this?
> Build fails on Xcode 9.3
>
>
> Key: CB-14009
> URL: https://issues.apache.org/jira/browse/CB-14009
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Reporter: Doug Davies
>Assignee: Suraj Pindoria
>Priority: Major
>
> Seeing this after I update to XCode 9.3 and build through cli
> Error Domain=IDEProfileLocatorErrorDomain Code=1 “No profiles for
> ‘org.oclc.digby’ were found” UserInfo=\{NSLocalizedDescription=No profiles
> for ‘org.oclc.digby’ were found, NSLocalizedRecoverySuggestion=Xcode couldn’t
> find any iOS Ad Hoc provisioning profiles matching ‘org.oclc.digby’.
> Automatic signing is disabled and unable to generate a profile. To enable
> automatic signing, pass -allowProvisioningUpdates to xcodebuild.}
> When I bring the project up in XCode the signing is correct and not
> complaining.
> I tried adding
> “buildFlag”: [“-allowProvisioningUpdates”]
> to build.json and still not working
> Interestingly… I went into xcode and did an archive/export from there… now
> the cli works… it must set something that it needs
--
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-14009) Build fails on Xcode 9.3
[
https://issues.apache.org/jira/browse/CB-14009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422880#comment-16422880
]
Doug Davies commented on CB-14009:
--
Just setting automatic provisioning wasn't enough for me. I had to actually
archive AND export before it would work.
> Build fails on Xcode 9.3
>
>
> Key: CB-14009
> URL: https://issues.apache.org/jira/browse/CB-14009
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Reporter: Doug Davies
>Assignee: Suraj Pindoria
>Priority: Major
>
> Seeing this after I update to XCode 9.3 and build through cli
> Error Domain=IDEProfileLocatorErrorDomain Code=1 “No profiles for
> ‘org.oclc.digby’ were found” UserInfo=\{NSLocalizedDescription=No profiles
> for ‘org.oclc.digby’ were found, NSLocalizedRecoverySuggestion=Xcode couldn’t
> find any iOS Ad Hoc provisioning profiles matching ‘org.oclc.digby’.
> Automatic signing is disabled and unable to generate a profile. To enable
> automatic signing, pass -allowProvisioningUpdates to xcodebuild.}
> When I bring the project up in XCode the signing is correct and not
> complaining.
> I tried adding
> “buildFlag”: [“-allowProvisioningUpdates”]
> to build.json and still not working
> Interestingly… I went into xcode and did an archive/export from there… now
> the cli works… it must set something that it needs
--
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-14009) Build fails on Xcode 9.3
Doug Davies created CB-14009:
Summary: Build fails on Xcode 9.3
Key: CB-14009
URL: https://issues.apache.org/jira/browse/CB-14009
Project: Apache Cordova
Issue Type: Bug
Components: cordova-ios
Reporter: Doug Davies
Assignee: Suraj Pindoria
Seeing this after I update to XCode 9.3 and build through cli
Error Domain=IDEProfileLocatorErrorDomain Code=1 “No profiles for
‘org.oclc.digby’ were found” UserInfo=\{NSLocalizedDescription=No profiles for
‘org.oclc.digby’ were found, NSLocalizedRecoverySuggestion=Xcode couldn’t find
any iOS Ad Hoc provisioning profiles matching ‘org.oclc.digby’. Automatic
signing is disabled and unable to generate a profile. To enable automatic
signing, pass -allowProvisioningUpdates to xcodebuild.}
When I bring the project up in XCode the signing is correct and not complaining.
I tried adding
“buildFlag”: [“-allowProvisioningUpdates”]
to build.json and still not working
Interestingly… I went into xcode and did an archive/export from there… now the
cli works… it must set something that it needs
--
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-13974) With cordova-android 7.x plugins with jni libraries are not backwards compatible
[
https://issues.apache.org/jira/browse/CB-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399222#comment-16399222
]
Doug Davies commented on CB-13974:
--
Ya, locally I created a hook that gets applied when the plugin is installed to
overwrite the plugin.xml with my version. I was just hoping to provide a PR to
the Manatee guys, but I'll let them know that they should really be moving
forward with cordova-android 7.x.
> With cordova-android 7.x plugins with jni libraries are not backwards
> compatible
>
>
> Key: CB-13974
> URL: https://issues.apache.org/jira/browse/CB-13974
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova-android-7.0.0
>Reporter: Doug Davies
>Assignee: Joe Bowser
>Priority: Major
> Attachments: image1.png, image2.png, image3.png
>
>
> Pull down my project on GitHub
> [https://github.com/funkyvisions/manatee-tester.git]
> It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS
> compatible with cordova-android 6.4.0.
> Execute the following:
> {code:java}
> cordova prepare
> cordova build android{code}
> You'll see everything prepares and builds fine and you can see the libraries
> (.so files and jar) end up in the correct directories in the APK (view
> through Android Studio - Build -> Analyze APK). See image1.
> Now we are going to switch to cordova-android 7.1.0.
> Execute the following:
> {code:java}
> cp package.7.json package.json
> cp config.7.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android
> {code}
> Notice it fails. This is because the plugin.xml is incorrect (although the
> error would never lead you to discover this). So let's fix it. Unfortunately,
> I tried to fork the project and apply a patch, but there seems to be a bug
> with cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so
> instead I included it locally in this project along with the patch to
> plugin.xml.
> I changed these lines in plugin.xml:
> {code:java}
> framework="true" />
> src="src/android/src/com/manateeworks/BarcodeScannerPlugin.java"
> target-dir="src/com/manateeworks" />
> target-dir="src/com/manateeworks" />
> target-dir="res/layout" />
> target-dir="res/drawable" />
> target-dir="res/drawable-hdpi" />
> target-dir="res/drawable" />
> target-dir="res/drawable" />
> target-dir="res/drawable" />
> target-dir="libs/armeabi" />
> target-dir="libs/x86" />
> target-dir="libs/armeabi-v7a" />
> target-dir="libs/arm64-v8a" />
> target-dir="libs/mips" />
> {code}
> to this:
> {code:java}
>
>
>
> target="jniLibs/mwbscanner.jar" />
>
> src="src/android/src/com/manateeworks/BarcodeScannerPlugin.java"
> target-dir="src/com/manateeworks" />
> target-dir="src/com/manateeworks" />
>
> target="res/layout/scanner.xml" />
> target="res/drawable/overlay_mw.png" />
> target="res/drawable-hdpi/overlay_mw.png" />
> target="res/drawable/flashbuttonoff.png" />
> target="res/drawable/flashbuttonon.png" />
> target="res/drawable/zoom.png" />
>
> target="jniLibs/armeabi/libBarcodeScannerLib.so" />
> target="jniLibs/x86/libBarcodeScannerLib.so" />
> target="jniLibs/armeabi-v7a/libBarcodeScannerLib.so" />
> target="jniLibs/arm64-v8a/libBarcodeScannerLib.so" />
> target="jniLibs/mips/libBarcodeScannerLib.so" />
> {code}
> Now let's switch to the forked version of the plugin and see if it works.
> Execute the following:
> {code:java}
> cp package.fork.json package.json
> cp config.fork.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android{code}
> Now you see it builds once again and the APK is correct. See image2.
> However, the directives I put in plugin.xml are not backwards compatible with
> 6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and
> trying to build.
> {code:java}
> cp package.6.json package.json
> cp config.6.xml config.xml
> rm -rf platforms plugins
> cordova prepare
> cordova build android{code}
> Now look at the APK and you will see the libraries are missing. See image3.
> In order to fix this, I have to create a mix on the old config plus the new.
> See
> [https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf]
> I don't think this is a very good solution.
> There needs to be an approach that works with both. I wonder if this
> (https://issues.apache.org/jira/browse/CB-8781) is missing from
> cordova-android 7.1.0:
> {code:java}
> jniLibs.srcDirs = ['libs']{code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
[jira] [Updated] (CB-13973) cordova-fetch fails to retrieve a forked plugin
[ https://issues.apache.org/jira/browse/CB-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Davies updated CB-13973: - Description: Try cordova plugin add [https://github.com/manateeworks/phonegap-manateeworks-v3.git] then try my forked version of the plugin (all I changed was plugin.xml) cordova plugin add [https://github.com/funkyvisions/phonegap-manateeworks-v3.git] verbose logging shows: *No scripts found for hook "before_plugin_add".* *Calling plugman.fetch on plugin "https://github.com/funkyvisions/phonegap-manateeworks-v3.git"* (node:75391) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): [object Object] (node:75391) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. was: Try cordova plugin add [https://github.com/manateeworks/phonegap-manateeworks-v3.git] then try my forked project cordova plugin add [https://github.com/funkyvisions/phonegap-manateeworks-v3.git] verbose logging shows: *No scripts found for hook "before_plugin_add".* *Calling plugman.fetch on plugin "https://github.com/funkyvisions/phonegap-manateeworks-v3.git"* (node:75391) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): [object Object] (node:75391) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. > cordova-fetch fails to retrieve a forked plugin > --- > > Key: CB-13973 > URL: https://issues.apache.org/jira/browse/CB-13973 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-fetch >Affects Versions: cordova@8.0.0 >Reporter: Doug Davies >Priority: Minor > > Try > cordova plugin add > [https://github.com/manateeworks/phonegap-manateeworks-v3.git] > then try my forked version of the plugin (all I changed was plugin.xml) > cordova plugin add > [https://github.com/funkyvisions/phonegap-manateeworks-v3.git] > verbose logging shows: > *No scripts found for hook "before_plugin_add".* > *Calling plugman.fetch on plugin > "https://github.com/funkyvisions/phonegap-manateeworks-v3.git"* > (node:75391) UnhandledPromiseRejectionWarning: Unhandled promise rejection > (rejection id: 1): [object Object] > (node:75391) [DEP0018] DeprecationWarning: Unhandled promise rejections are > deprecated. In the future, promise rejections that are not handled will > terminate the Node.js process with a non-zero exit code. -- 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] [Updated] (CB-13974) With cordova-android 7.x plugins with jni libraries are not backwards compatible
[
https://issues.apache.org/jira/browse/CB-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Davies updated CB-13974:
-
Description:
Pull down my project on GitHub
[https://github.com/funkyvisions/manatee-tester.git]
It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS
compatible with cordova-android 6.4.0.
Execute the following:
{code:java}
cordova prepare
cordova build android{code}
You'll see everything prepares and builds fine and you can see the libraries
(.so files and jar) end up in the correct directories in the APK (view through
Android Studio - Build -> Analyze APK). See image1.
Now we are going to switch to cordova-android 7.1.0.
Execute the following:
{code:java}
cp package.7.json package.json
cp config.7.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android
{code}
Notice it fails. This is because the plugin.xml is incorrect (although the
error would never lead you to discover this). So let's fix it. Unfortunately, I
tried to fork the project and apply a patch, but there seems to be a bug with
cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so instead I
included it locally in this project along with the patch to plugin.xml.
I changed these lines in plugin.xml:
{code:java}
{code}
to this:
{code:java}
{code}
Now let's switch to the forked version of the plugin and see if it works.
Execute the following:
{code:java}
cp package.fork.json package.json
cp config.fork.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android{code}
Now you see it builds once again and the APK is correct. See image2.
However, the directives I put in plugin.xml are not backwards compatible with
6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and trying
to build.
{code:java}
cp package.6.json package.json
cp config.6.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android{code}
Now look at the APK and you will see the libraries are missing. See image3.
In order to fix this, I have to create a mix on the old config plus the new.
See
[https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf]
I don't think this is a very good solution.
There needs to be an approach that works with both. I wonder if this
(https://issues.apache.org/jira/browse/CB-8781) is missing from cordova-android
7.1.0:
{code:java}
jniLibs.srcDirs = ['libs']{code}
was:
Pull down my project on GitHub
[https://github.com/funkyvisions/manatee-tester.git]
It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS
compatible with cordova-android 6.4.0.
Execute the following:
{code:java}
cordova prepare
cordova build android{code}
You'll see everything prepares and builds fine and you can see the libraries
(.so files and jar) end up in the correct directories in the APK (view through
Android Studio - Build -> Analyze APK). See image1.
Now we are going to switch to cordova-android 7.1.0.
Execute the following:
{code:java}
cp package.7.json package.json
cp config.7.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android
{code}
Notice it fails. This is because the plugin.xml is incorrect (although the
error would never lead you to discover this). So let's fix it. Unfortunately, I
tried to fork the project and apply a patch, but there seems to be a bug with
cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so instead I
included it locally in this project along with the patch to plugin.xml.
I changed these lines in plugin.xml:
{code:java}
{code}
to this:
{code:java}
{code}
Now let's switch to the forked version of the plugin and see if it works.
Execute the following:
{code:java}
cp package.fork.json package.json
cp config.fork.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android{code}
Now you see it builds once again and the APK is correct. See image2.
However, the directives I put in plugin.xml are not backwards compatible with
6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and trying
to build.
{code:java}
cp package.6.json package.json
cp config.6.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android{code}
Now look at the APK and you will see the libraries are missing. See image3.
In order to fix this, I have to create a mix on the old config plus the new.
See
[https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf]
I don't think this is a very good solu
[jira] [Updated] (CB-13974) With cordova-android 7.x plugins with jni libraries are not backwards compatible
[
https://issues.apache.org/jira/browse/CB-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Davies updated CB-13974:
-
Description:
Pull down my project on GitHub
[https://github.com/funkyvisions/manatee-tester.git]
It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS
compatible with cordova-android 6.4.0.
Execute the following:
{code:java}
cordova prepare
cordova build android{code}
You'll see everything prepares and builds fine and you can see the libraries
(.so files and jar) end up in the correct directories in the APK (view through
Android Studio - Build -> Analyze APK). See image1.
Now we are going to switch to cordova-android 7.1.0.
Execute the following:
{code:java}
cp package.7.json package.json
cp config.7.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android
{code}
Notice it fails. This is because the plugin.xml is incorrect (although the
error would never lead you to discover this). So let's fix it. Unfortunately, I
tried to fork the project and apply a patch, but there seems to be a bug with
cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so instead I
included it locally in this project along with the patch to plugin.xml.
I changed these lines in plugin.xml:
{code:java}
{code}
to this:
{code:java}
{code}
Now let's switch to the forked version of the plugin and see if it works.
Execute the following:
{code:java}
cp package.fork.json package.json
cp config.fork.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android{code}
Now you see it builds once again and the APK is correct. See image2.
However, the directives I put in plugin.xml are not backwards compatible with
6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and trying
to build.
{code:java}
cp package.6.json package.json
cp config.6.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android{code}
Now look at the APK and you will see the libraries are missing. See image3.
In order to fix this, I have to create a mix on the old config plus the new.
See
[https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf]
I don't think this is a very good solution.
There needs to be an approach that works with both. I wonder if this
(https://issues.apache.org/jira/browse/CB-8781) is missing from cordova-android
7.1.0:
{code:java}
jniLibs.srcDirs = ['libs']{code}
was:
Pull down my project on GitHub
[https://github.com/funkyvisions/manatee-tester.git]
It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS
compatible with cordova-android 6.4.0.
Execute the following:
cordova prepare
cordova build android
You'll see everything prepares and builds fine and you can see the libraries
(.so files and jar) end up in the correct directories in the APK (view through
Android Studio - Build -> Analyze APK). See image1.
Now we are going to switch to cordova-android 7.1.0.
Execute the following:
cp package.7.json package.json
cp config.7.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android
Notice it fails. This is because the plugin.xml is incorrect (although the
error would never lead you to discover this). So let's fix it. Unfortunately, I
tried to fork the project and apply a patch, but there seems to be a bug with
cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so instead I
included it locally in this project along with the patch to plugin.xml.
I changed these lines in plugin.xml:
to this:
Now let's switch to the forked version of the plugin and see if it works.
Execute the following:
cp package.fork.json package.json
cp config.fork.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android
Now you see it builds once again and the APK is correct. See image2.
However, the directives I put in plugin.xml are not backwards compatible with
6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and trying
to build.
cp package.6.json package.json
cp config.6.xml config.xml
rm -rf platforms plugins
cordova prepare
cordova build android
Now look at the APK and you will see the libraries are missing. See image3.
In order to fix this, I have to create a mix on the old config plus the new.
See
[https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf]
I don't think this is a very good solution.
There needs to be an approach that works with both. I wonder if this
(https://i
[jira] [Updated] (CB-13974) With cordova-android 7.x plugins with jni libraries are not backwards compatible
[ https://issues.apache.org/jira/browse/CB-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Davies updated CB-13974: - Description: Pull down my project on GitHub [https://github.com/funkyvisions/manatee-tester.git] It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS compatible with cordova-android 6.4.0. Execute the following: cordova prepare cordova build android You'll see everything prepares and builds fine and you can see the libraries (.so files and jar) end up in the correct directories in the APK (view through Android Studio - Build -> Analyze APK). See image1. Now we are going to switch to cordova-android 7.1.0. Execute the following: cp package.7.json package.json cp config.7.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Notice it fails. This is because the plugin.xml is incorrect (although the error would never lead you to discover this). So let's fix it. Unfortunately, I tried to fork the project and apply a patch, but there seems to be a bug with cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so instead I included it locally in this project along with the patch to plugin.xml. I changed these lines in plugin.xml: to this: Now let's switch to the forked version of the plugin and see if it works. Execute the following: cp package.fork.json package.json cp config.fork.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Now you see it builds once again and the APK is correct. See image2. However, the directives I put in plugin.xml are not backwards compatible with 6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and trying to build. cp package.6.json package.json cp config.6.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Now look at the APK and you will see the libraries are missing. See image3. In order to fix this, I have to create a mix on the old config plus the new. See [https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf] I don't think this is a very good solution. There needs to be an approach that works with both. I wonder if this (https://issues.apache.org/jira/browse/CB-8781) is missing from cordova-android 7.1.0: jniLibs.srcDirs = ['libs'] was: Pull down my project on GitHub https://github.com/funkyvisions/manatee-tester.git It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS compatible with cordova-android 6.4.0. Execute the following: cordova prepare cordova build android You'll see everything prepares and builds fine and you can see the libraries (.so files and jar) end up in the correct directories in the APK (view through Android Studio - Build -> Analyze APK). See image1. Now we are going to switch to cordova-android 7.1.0. Execute the following: cp package.7.json package.json cp config.7.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Notice it fails. This is because the plugin.xml is incorrect (although the error would never lead you to discover this). So let's fix it. Unfortunately, I tried to fork the project and apply a patch, but there seems to be a bug with cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so instead I included it locally in this project along with the patch to plugin.xml. I changed these lines in plugin.xml: to this: Now let's switch to the forked version of the plugin and see if it works. Execute the following: cp package.fork.json package.json cp config.fork.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Now you see it builds once again and the APK is correct. See image2. However, the directives I put in plugin.xml are not backwards compatible with 6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and trying to build. cp package.6.json package.json cp config.6.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Now look at the APK and you will see the libraries are missing. See image3. In order to fix this, I have to create a mix on the old config plus the new. See [https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf] I don't think this is a very good solution. There needs to be an approach that works with both. I wonder if this (https://issues.apache.org/jira/browse/CB-8781) is missing from cordova-android 7.1.0: jniLibs.srcDirs = ['libs'] > With cordova-andr
[jira] [Updated] (CB-13974) With cordova-android 7.x plugins with jni libraries are not backwards compatible
[ https://issues.apache.org/jira/browse/CB-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Davies updated CB-13974: - Attachment: image3.png image2.png image1.png > With cordova-android 7.x plugins with jni libraries are not backwards > compatible > > > Key: CB-13974 > URL: https://issues.apache.org/jira/browse/CB-13974 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova-android-7.0.0 >Reporter: Doug Davies >Assignee: Joe Bowser >Priority: Major > Attachments: image1.png, image2.png, image3.png > > > Pull down my project on GitHub > [https://github.com/funkyvisions/manatee-tester.git] > > It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS > compatible with cordova-android 6.4.0. > Execute the following: > cordova prepare > cordova build android > You'll see everything prepares and builds fine and you can see the libraries > (.so files and jar) end up in the correct directories in the APK (view > through Android Studio - Build -> Analyze APK). See image1. > Now we are going to switch to cordova-android 7.1.0. > Execute the following: > cp package.7.json package.json > cp config.7.xml config.xml > rm -rf platforms plugins > cordova prepare > cordova build android > Notice it fails. This is because the plugin.xml is incorrect (although the > error would never lead you to discover this). So let's fix it. Unfortunately, > I tried to fork the project and apply a patch, but there seems to be a bug > with cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so > instead I included it locally in this project along with the patch to > plugin.xml. > I changed these lines in plugin.xml: > framework="true" /> > target-dir="src/com/manateeworks" /> > target-dir="src/com/manateeworks" /> > /> > target-dir="res/drawable" /> > target-dir="res/drawable-hdpi" /> > target-dir="res/drawable" /> > target-dir="res/drawable" /> > target-dir="res/drawable" /> > target-dir="libs/armeabi" /> > target-dir="libs/x86" /> > target-dir="libs/armeabi-v7a" /> > target-dir="libs/arm64-v8a" /> > target-dir="libs/mips" /> > to this: > > > > target="jniLibs/mwbscanner.jar" /> > > src="src/android/src/com/manateeworks/BarcodeScannerPlugin.java" > target-dir="src/com/manateeworks" /> > target-dir="src/com/manateeworks" /> > > target="res/layout/scanner.xml" /> > target="res/drawable/overlay_mw.png" /> > target="res/drawable-hdpi/overlay_mw.png" /> > target="res/drawable/flashbuttonoff.png" /> > target="res/drawable/flashbuttonon.png" /> > target="res/drawable/zoom.png" /> > > target="jniLibs/armeabi/libBarcodeScannerLib.so" /> > target="jniLibs/x86/libBarcodeScannerLib.so" /> > target="jniLibs/armeabi-v7a/libBarcodeScannerLib.so" /> > target="jniLibs/arm64-v8a/libBarcodeScannerLib.so" /> > target="jniLibs/mips/libBarcodeScannerLib.so" /> > Now let's switch to the forked version of the plugin and see if it works. > Execute the following: > cp package.fork.json package.json > cp config.fork.xml config.xml > rm -rf platforms plugins > cordova prepare > cordova build android > Now you see it builds once again and the APK is correct. See image2. > However, the directives I put in plugin.xml are not backwards compatible with > 6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and > trying to build. > cp package.6.json package.json > cp config.6.xml config.xml > rm -rf platforms plugins > cordova prepare > cordova build android > Now look at the APK and you will see the libraries are missing. See image3. > In order to fix this, I have to create a mix on the old config plus the new. > See > [https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf] > I don't think this is a very good solution. > There needs to be an approach that works with both. I wonder if this > (https://issues.apache.org/jira/browse/CB-8781) is missing from > cordova-android 7.1.0: > jniLibs.srcDirs = ['libs'] > -- 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-13974) With cordova-android 7.x plugins with jni libraries are not backwards compatible
Doug Davies created CB-13974: Summary: With cordova-android 7.x plugins with jni libraries are not backwards compatible Key: CB-13974 URL: https://issues.apache.org/jira/browse/CB-13974 Project: Apache Cordova Issue Type: Bug Components: cordova-android Affects Versions: cordova-android-7.0.0 Reporter: Doug Davies Assignee: Joe Bowser Pull down my project on GitHub https://github.com/funkyvisions/manatee-tester.git It uses the 3rd party plugin (manateeworks-barcodescanner-v3) which IS compatible with cordova-android 6.4.0. Execute the following: cordova prepare cordova build android You'll see everything prepares and builds fine and you can see the libraries (.so files and jar) end up in the correct directories in the APK (view through Android Studio - Build -> Analyze APK). See image1. Now we are going to switch to cordova-android 7.1.0. Execute the following: cp package.7.json package.json cp config.7.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Notice it fails. This is because the plugin.xml is incorrect (although the error would never lead you to discover this). So let's fix it. Unfortunately, I tried to fork the project and apply a patch, but there seems to be a bug with cordova-fetch (https://issues.apache.org/jira/browse/CB-13973), so instead I included it locally in this project along with the patch to plugin.xml. I changed these lines in plugin.xml: to this: Now let's switch to the forked version of the plugin and see if it works. Execute the following: cp package.fork.json package.json cp config.fork.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Now you see it builds once again and the APK is correct. See image2. However, the directives I put in plugin.xml are not backwards compatible with 6.4.0. We can prove this by now switch back to cordova-android 6.4.0 and trying to build. cp package.6.json package.json cp config.6.xml config.xml rm -rf platforms plugins cordova prepare cordova build android Now look at the APK and you will see the libraries are missing. See image3. In order to fix this, I have to create a mix on the old config plus the new. See [https://github.com/funkyvisions/phonegap-manateeworks-v3/commit/9f3b165832141e45fa2c2e92dbf62b2300f0caf2#diff-53f390d375398624afe1cfe1125f42bf] I don't think this is a very good solution. There needs to be an approach that works with both. I wonder if this (https://issues.apache.org/jira/browse/CB-8781) is missing from cordova-android 7.1.0: jniLibs.srcDirs = ['libs'] -- 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] [Updated] (CB-13973) cordova-fetch fails to retrieve a forked plugin
[ https://issues.apache.org/jira/browse/CB-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Davies updated CB-13973: - Summary: cordova-fetch fails to retrieve a forked plugin (was: cordova-fetch fails to retrieve a forked project) > cordova-fetch fails to retrieve a forked plugin > --- > > Key: CB-13973 > URL: https://issues.apache.org/jira/browse/CB-13973 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-fetch >Affects Versions: cordova@8.0.0 >Reporter: Doug Davies >Priority: Minor > > Try > cordova plugin add > [https://github.com/manateeworks/phonegap-manateeworks-v3.git] > then try my forked project > cordova plugin add > [https://github.com/funkyvisions/phonegap-manateeworks-v3.git] > verbose logging shows: > *No scripts found for hook "before_plugin_add".* > *Calling plugman.fetch on plugin > "https://github.com/funkyvisions/phonegap-manateeworks-v3.git"* > (node:75391) UnhandledPromiseRejectionWarning: Unhandled promise rejection > (rejection id: 1): [object Object] > (node:75391) [DEP0018] DeprecationWarning: Unhandled promise rejections are > deprecated. In the future, promise rejections that are not handled will > terminate the Node.js process with a non-zero exit code. -- 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] [Updated] (CB-13973) cordova-fetch fails to retrieve a forked project
[ https://issues.apache.org/jira/browse/CB-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Davies updated CB-13973: - Affects Version/s: (was: 1.3.0) cordova@8.0.0 Description: Try cordova plugin add [https://github.com/manateeworks/phonegap-manateeworks-v3.git] then try my forked project cordova plugin add [https://github.com/funkyvisions/phonegap-manateeworks-v3.git] verbose logging shows: *No scripts found for hook "before_plugin_add".* *Calling plugman.fetch on plugin "https://github.com/funkyvisions/phonegap-manateeworks-v3.git"* (node:75391) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): [object Object] (node:75391) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. was: With cordova-8.0.0 try cordova plugin add [https://github.com/manateeworks/phonegap-manateeworks-v3.git] then try my forked project cordova plugin add [https://github.com/funkyvisions/phonegap-manateeworks-v3.git] verbose logging shows: *No scripts found for hook "before_plugin_add".* *Calling plugman.fetch on plugin "https://github.com/funkyvisions/phonegap-manateeworks-v3.git"* (node:75391) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): [object Object] (node:75391) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. > cordova-fetch fails to retrieve a forked project > > > Key: CB-13973 > URL: https://issues.apache.org/jira/browse/CB-13973 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-fetch >Affects Versions: cordova@8.0.0 >Reporter: Doug Davies >Priority: Minor > > Try > cordova plugin add > [https://github.com/manateeworks/phonegap-manateeworks-v3.git] > then try my forked project > cordova plugin add > [https://github.com/funkyvisions/phonegap-manateeworks-v3.git] > verbose logging shows: > *No scripts found for hook "before_plugin_add".* > *Calling plugman.fetch on plugin > "https://github.com/funkyvisions/phonegap-manateeworks-v3.git"* > (node:75391) UnhandledPromiseRejectionWarning: Unhandled promise rejection > (rejection id: 1): [object Object] > (node:75391) [DEP0018] DeprecationWarning: Unhandled promise rejections are > deprecated. In the future, promise rejections that are not handled will > terminate the Node.js process with a non-zero exit code. -- 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-13973) cordova-fetch fails to retrieve a forked project
Doug Davies created CB-13973: Summary: cordova-fetch fails to retrieve a forked project Key: CB-13973 URL: https://issues.apache.org/jira/browse/CB-13973 Project: Apache Cordova Issue Type: Bug Components: cordova-fetch Affects Versions: 1.3.0 Reporter: Doug Davies With cordova-8.0.0 try cordova plugin add [https://github.com/manateeworks/phonegap-manateeworks-v3.git] then try my forked project cordova plugin add [https://github.com/funkyvisions/phonegap-manateeworks-v3.git] verbose logging shows: *No scripts found for hook "before_plugin_add".* *Calling plugman.fetch on plugin "https://github.com/funkyvisions/phonegap-manateeworks-v3.git"* (node:75391) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): [object Object] (node:75391) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. -- 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] [Comment Edited] (CB-13228) cordova-browser@5 doesn't add with cordova<7
[
https://issues.apache.org/jira/browse/CB-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203833#comment-16203833
]
Doug Davies edited comment on CB-13228 at 10/13/17 5:30 PM:
I'm seeing this too :( It also seems to be leaving behind a "prepare" director
in the root when it fails. I used "phonegap prepare" and specify the platforms
in config.xml for installation. Also, after it fails to install, if I do a
"cordova run browser" then it of course fails to run, but it also leaves behind
a "run" directory in the root. I think the same thing happens with "cordova
platform add browser". The "platform" directory gets left behind.
was (Author: csddavies):
I'm seeing this too :( It also seems to be leaving behind a "prepare" director
in the root when it fails. I used "phonegap prepare" and specify the platforms
in config.xml for installation. Also, after it fails to install, if I do a
"cordova run browser" then it of course fails to run, but it also leaves behind
a "run" directory in the root.
> cordova-browser@5 doesn't add with cordova<7
>
>
> Key: CB-13228
> URL: https://issues.apache.org/jira/browse/CB-13228
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Steve Gill
> Labels: browser-next, easy-fix
> Fix For: 5.0.1
>
>
> {code}
> cordova platform add browser@latest --nofetch
> Warning: using prerelease version 7.0.2-dev (cordova-lib@7.0.2-dev)
> Adding browser project...
> Unable to load PlatformApi from platform. Error: Cannot find module
> 'cordova-common'
> Error: Uncaught, unspecified "error" event. (The platform "browser" does not
> appear to be a valid cordova platform. It is missing API.js. browser not
> supported.)
> {code}
> I believe cordova-common wasn't properly bundled into cordova-browser@5.
> Works fine if I add it locally. Easy fix
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-13228) cordova-browser@5 doesn't add with cordova<7
[
https://issues.apache.org/jira/browse/CB-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203833#comment-16203833
]
Doug Davies edited comment on CB-13228 at 10/13/17 5:27 PM:
I'm seeing this too :( It also seems to be leaving behind a "prepare" director
in the root when it fails. I used "phonegap prepare" and specify the platforms
in config.xml for installation. Also, after it fails to install, if I do a
"cordova run browser" then it of course fails to run, but it also leaves behind
a "run" directory in the root.
was (Author: csddavies):
I'm seeing this too :( It also seems to be leaving behind a "prepare" director
in the root when it fails. I used "phonegap prepare" and specify the platforms
in config.xml for installation.
> cordova-browser@5 doesn't add with cordova<7
>
>
> Key: CB-13228
> URL: https://issues.apache.org/jira/browse/CB-13228
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Steve Gill
> Labels: browser-next, easy-fix
> Fix For: 5.0.1
>
>
> {code}
> cordova platform add browser@latest --nofetch
> Warning: using prerelease version 7.0.2-dev (cordova-lib@7.0.2-dev)
> Adding browser project...
> Unable to load PlatformApi from platform. Error: Cannot find module
> 'cordova-common'
> Error: Uncaught, unspecified "error" event. (The platform "browser" does not
> appear to be a valid cordova platform. It is missing API.js. browser not
> supported.)
> {code}
> I believe cordova-common wasn't properly bundled into cordova-browser@5.
> Works fine if I add it locally. Easy fix
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-13228) cordova-browser@5 doesn't add with cordova<7
[
https://issues.apache.org/jira/browse/CB-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203833#comment-16203833
]
Doug Davies edited comment on CB-13228 at 10/13/17 5:26 PM:
I'm seeing this too :( It also seems to be leaving behind a "prepare" director
in the root when it fails. I used "phonegap prepare" and specify the platforms
in config.xml for installation.
was (Author: csddavies):
I'm seeing this too :(
> cordova-browser@5 doesn't add with cordova<7
>
>
> Key: CB-13228
> URL: https://issues.apache.org/jira/browse/CB-13228
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Steve Gill
> Labels: browser-next, easy-fix
> Fix For: 5.0.1
>
>
> {code}
> cordova platform add browser@latest --nofetch
> Warning: using prerelease version 7.0.2-dev (cordova-lib@7.0.2-dev)
> Adding browser project...
> Unable to load PlatformApi from platform. Error: Cannot find module
> 'cordova-common'
> Error: Uncaught, unspecified "error" event. (The platform "browser" does not
> appear to be a valid cordova platform. It is missing API.js. browser not
> supported.)
> {code}
> I believe cordova-common wasn't properly bundled into cordova-browser@5.
> Works fine if I add it locally. Easy fix
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13228) cordova-browser@5 doesn't add with cordova<7
[
https://issues.apache.org/jira/browse/CB-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203833#comment-16203833
]
Doug Davies commented on CB-13228:
--
I'm seeing this too :(
> cordova-browser@5 doesn't add with cordova<7
>
>
> Key: CB-13228
> URL: https://issues.apache.org/jira/browse/CB-13228
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Steve Gill
> Labels: browser-next, easy-fix
> Fix For: 5.0.1
>
>
> {code}
> cordova platform add browser@latest --nofetch
> Warning: using prerelease version 7.0.2-dev (cordova-lib@7.0.2-dev)
> Adding browser project...
> Unable to load PlatformApi from platform. Error: Cannot find module
> 'cordova-common'
> Error: Uncaught, unspecified "error" event. (The platform "browser" does not
> appear to be a valid cordova platform. It is missing API.js. browser not
> supported.)
> {code}
> I believe cordova-common wasn't properly bundled into cordova-browser@5.
> Works fine if I add it locally. Easy fix
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13404) android-versions module missing
[ https://issues.apache.org/jira/browse/CB-13404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193313#comment-16193313 ] Doug Davies commented on CB-13404: -- With phonegap-cli. phonegap prepare and the entry in config.xml. We are on PhoneGap 6.5.0. > android-versions module missing > --- > > Key: CB-13404 > URL: https://issues.apache.org/jira/browse/CB-13404 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.3.0 >Reporter: Doug Davies >Assignee: Joe Bowser > > I just updated cordova-android from 6.2.3 to 6.3.0. Now when I type > “phonegap emulate android” I get the error "Error: Cannot find module > ‘android-versions’". I think it’s coming from > platforms/android/cordova/lib/emulator.js:var android_versions = > require(‘android-versions’); > If I look in platforms/android/cordova/node_modules I do not see > android-versions installed. > I use the following in my config.xml to have cordova-android installed. > > And then use "phonegap prepare". -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13404) android-versions module missing
Doug Davies created CB-13404: Summary: android-versions module missing Key: CB-13404 URL: https://issues.apache.org/jira/browse/CB-13404 Project: Apache Cordova Issue Type: Bug Components: cordova-android Affects Versions: 6.3.0 Reporter: Doug Davies Assignee: Joe Bowser I just updated cordova-android from 6.2.3 to 6.3.0. Now when I type “phonegap emulate android” I get the error "Error: Cannot find module ‘android-versions’". I think it’s coming from platforms/android/cordova/lib/emulator.js:var android_versions = require(‘android-versions’); If I look in platforms/android/cordova/node_modules I do not see android-versions installed. I use the following in my config.xml to have cordova-android installed. And then use "phonegap prepare". -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12810) keep existing formatting in package.json
[ https://issues.apache.org/jira/browse/CB-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183182#comment-16183182 ] Doug Davies commented on CB-12810: -- I don't like that my original package.json and config.xml get overwritten. I manage them myself and have lots of comments in them to detail intricacies. I also group things together so that they make logical sense for me. How can I get cordova to not touch these files? I tried --nosave on prepare and "cordova config set autosave false". > keep existing formatting in package.json > > > Key: CB-12810 > URL: https://issues.apache.org/jira/browse/CB-12810 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-lib >Affects Versions: 7.0.0 >Reporter: Steve Gill >Priority: Minor > Labels: backlog, cordova-8.0.0, cordova-next > > We will write our own indentation in package.json. For commands that shell > out to cordova-fetch and therefore npm, we have no control over it (cordova > platform/plugin add/rm). > We could theoretically keep indentaiton for commands where we write to > package.json (also platform/plugin add/rm to cordova key & during restore > when we sync config.xml & package.json). > This issue is probably not worth implementing. > npm@5 seems like it will respect existing formatting. > Previous issue with npm formatting: https://github.com/npm/npm/issues/5694 > npm5 respecting indentation: https://github.com/npm/npm/issues/16244 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13009) cordova prepare unnecessarily edits config.xml and package.json
[ https://issues.apache.org/jira/browse/CB-13009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179128#comment-16179128 ] Doug Davies commented on CB-13009: -- I don't like that my original package.json and config.xml get overwritten either. I manage them myself and have lots of comments in them to detail intricacies. I also group things together so that they make logical sense for me. How can I get cordova to not touch these files? I tried --nosave on prepare and "cordova config set autosave false". Let me know if there is a better place we can have this discussion. > cordova prepare unnecessarily edits config.xml and package.json > --- > > Key: CB-13009 > URL: https://issues.apache.org/jira/browse/CB-13009 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-cli >Affects Versions: 7.0.1 > Environment: Mac OSX 10.12.5 > Node 8.1.2 > npm 5.0.3 >Reporter: Christian Tschanz >Priority: Minor > > I crafted my config.xml file by hand (and added comments) to make it more > readable and maintainable. I also removed all '^' or '~' from the versions of > the engines/plugins to fix the version to one specific one (I will manually > test new versions and update if possible). I also removed the '^' from the > package.json file it generates. > When running 'cordova prepare' it will completely re-create the config.xml > file and therefore re-format it. It will also re-add the '^' to all versions. > It will also add the '^' to the versions in the package.json file. > This is VERY annoying. Previous versions did not behave like this. They only > edited the config.xml if explicitly told to do so. I really, really want to > fix the versions to a specific one and don't want it to always add the '^'. I > would also prefer it if it the 'prepare' command would not re-create the > config.xml file as there is no need for that and it kills all formatting and > comments. > At the moment I hope it respects the 'package-lock' file when installing > plugins because I can't have it install newer versions automatically. Sadly > many plugins are not as stable and well maintained for such an automatic > update to work well in large projects. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
