[jira] [Commented] (CB-10657) [wkWebView] wkWebView disables JS execution when app is backgrounded
[ https://issues.apache.org/jira/browse/CB-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16278037#comment-16278037 ] Ninos commented on CB-10657: I'm having the same issue as Gaven Henry described. This causes a lot of plugins to be useless when the user simply "locks" their phone. > [wkWebView] wkWebView disables JS execution when app is backgrounded > > > Key: CB-10657 > URL: https://issues.apache.org/jira/browse/CB-10657 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-wkwebview-engine > Environment: iOS >Reporter: John Robert Cobbold >Assignee: Shazron Abdullah > Labels: triaged, wkwebview-known-issues > > When using wkWebView, Javascript execution is totally stopped after the app > is backgrounded by the user. This is a major problem for apps using > background modes as no javascript callback will be executed unless the app is > either in the foreground or was already terminated by the user / OS. > example: cordova-plugin-geofence's javascript callbacks will not trigger > after the app was backgrounded but will however trigger if the app is in the > foregrounded or was killed by the user / OS. > UIView does not have this problem. -- 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] [Closed] (CB-13635) Fix docs to remove unnecessary platform release "announce" steps
[ https://issues.apache.org/jira/browse/CB-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Pindoria closed CB-13635. --- Resolution: Fixed > Fix docs to remove unnecessary platform release "announce" steps > > > Key: CB-13635 > URL: https://issues.apache.org/jira/browse/CB-13635 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-coho >Reporter: Suraj Pindoria >Assignee: Suraj Pindoria > -- 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-13635) Fix docs to remove unnecessary platform release "announce" steps
[ https://issues.apache.org/jira/browse/CB-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277709#comment-16277709 ] ASF subversion and git services commented on CB-13635: -- Commit 06fb61338c73e273f6f560ad5e57a3b5ca2b8cab in cordova-coho's branch refs/heads/master from [~surajpindoria] [ https://gitbox.apache.org/repos/asf?p=cordova-coho.git;h=06fb613 ] CB-13635: Fix docs to remove unnecessary platform release steps > Fix docs to remove unnecessary platform release "announce" steps > > > Key: CB-13635 > URL: https://issues.apache.org/jira/browse/CB-13635 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-coho >Reporter: Suraj Pindoria >Assignee: Suraj Pindoria > -- 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] [Updated] (CB-13635) Fix docs to remove unnecessary platform release "announce" steps
[ https://issues.apache.org/jira/browse/CB-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Pindoria updated CB-13635: Summary: Fix docs to remove unnecessary platform release "announce" steps (was: Fix docs to remove sending email to annou...@apache.org step) > Fix docs to remove unnecessary platform release "announce" steps > > > Key: CB-13635 > URL: https://issues.apache.org/jira/browse/CB-13635 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-coho >Reporter: Suraj Pindoria >Assignee: Suraj Pindoria > -- 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-13635) Fix docs to remove sending email to annou...@apache.org step
Suraj Pindoria created CB-13635: --- Summary: Fix docs to remove sending email to annou...@apache.org step Key: CB-13635 URL: https://issues.apache.org/jira/browse/CB-13635 Project: Apache Cordova Issue Type: Bug Components: cordova-coho Reporter: Suraj Pindoria Assignee: Suraj Pindoria -- 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] [Resolved] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13620. - Resolution: Fixed > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277601#comment-16277601 ] ASF subversion and git services commented on CB-13620: -- Commit e7d735a1be7df5aa26675c826165f90bd6e43146 in cordova-docs's branch refs/heads/master from [~bowserj] [ https://gitbox.apache.org/repos/asf?p=cordova-docs.git;h=e7d735a ] CB-13620: Updating upgrade documents > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277605#comment-16277605 ] ASF subversion and git services commented on CB-13620: -- Commit ffcdde1035bc275f60d4e31458f6d7da1eb1af80 in cordova-docs's branch refs/heads/master from [~bowserj] [ https://gitbox.apache.org/repos/asf?p=cordova-docs.git;h=ffcdde1 ] Merge pull request #775 from infil00p/7_0_updates CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277600#comment-16277600 ] ASF GitHub Bot commented on CB-13620: - infil00p closed pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/www/_posts/2017-12-04-cordova-android-7.0.0.md b/www/_posts/2017-12-04-cordova-android-7.0.0.md new file mode 100644 index 0..701ec1c07 --- /dev/null +++ b/www/_posts/2017-12-04-cordova-android-7.0.0.md @@ -0,0 +1,67 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a build artifact should not notice a difference. + +However this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations of files have changed and have been brought in line to the structure used by Android Studio. +This may affect plugin.xml files and config.xml files that use edit-config, and make it so plugins that use edit-config will not be able to be compatible with both Android 6.x and Android 7.x. To fix this issue, please do the following in your XML files: + +``` + + + + + +``` + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277603#comment-16277603 ] ASF subversion and git services commented on CB-13620: -- Commit d8028397730f466636f8c8ec5e3518092619d931 in cordova-docs's branch refs/heads/master from [~bowserj] [ https://gitbox.apache.org/repos/asf?p=cordova-docs.git;h=d802839 ] CB-13620 Announcement Blog Post > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277604#comment-16277604 ] ASF subversion and git services commented on CB-13620: -- Commit 601db9ff1b3175eb0eabaa486876a627c6499365 in cordova-docs's branch refs/heads/master from [~bowserj] [ https://gitbox.apache.org/repos/asf?p=cordova-docs.git;h=601db9f ] CB-13620: edit-config changes > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-12232) [cordova-android] Skipping HTTPS certificate validation should be hidden behind a flag, and not a default in debug builds
[
https://issues.apache.org/jira/browse/CB-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277543#comment-16277543
]
jakub-g edited comment on CB-12232 at 12/4/17 9:31 PM:
---
Hmm to fix the problem of people only checking Chrome DevTools and not logcat,
maybe what could be done is calling the following inside of
`onReceivedSslError`:
{code}
webView.evaluateJavascript("console.warn('SSL error for
$domain...')");
{code}
so basically double logging (on Java and JavaScript side). That would be
difficult to miss by anyone doing any serious work.
was (Author: jakub-g):
Hmm to fix the problem of people only checking Chrome DevTools and not logcat,
maybe what could be done is calling the following inside of
`onReceivedSslError`:
{code}
webView.evaluateJavascript("console.warn('SSL error for
$domain...')");
{code}
so basically double logging (on Java and JavaScript side). That would be
difficult to miss to anyone doing any serious work.
> [cordova-android] Skipping HTTPS certificate validation should be hidden
> behind a flag, and not a default in debug builds
> -
>
> Key: CB-12232
> URL: https://issues.apache.org/jira/browse/CB-12232
> Project: Apache Cordova
> Issue Type: Improvement
> Components: cordova-android
>Affects Versions: 6.2.0
>Reporter: jakub-g
>Priority: Critical
> Labels: android
>
> Right now, when you create a debuggable Cordova build (default behavior for
> commands like `cordova run android` etc.), it by default ignores all HTTPS
> certificate errors, as you can see in the code below:
> https://github.com/apache/cordova-android/blob/23fd0982b0faa6b7e169c2946eab07930f1f4d16/framework/src/org/apache/cordova/engine/SystemWebViewClient.java#L232-L239
> HTTPS certs are only validated when you create a release build, explicitly
> passing a flag, e.g.
> {{cordova run android --release}}
> This behavior is IMO harmful, and let me tell you why (see below for two
> real-life stories)
> *TL;DR I believe it would be better to not bind the lax HTTPS behavior to
> {{\-\-debug}} vs {{\-\-release}} build type, but hide it behind a special
> flag (to follow Chrome's naming convention, that would be
> {{\-\-ignore-certificate-errors}}, but we can name it whatever we like). This
> would expose developers to HTTPS errors much earlier in the dev process,
> which IMO is beneficial; it will also make it easier to understand and debug
> the problems, and avoid last-minute surprises.*
> _Question: do we have a portion of code already that makes runtime behavior
> depend on build-time flag? i.e. would it be easy to add a new flag in a
> similar way, without herculean effort?_
> So, the promised real-life stories:
> 1) Consider, that you have an HTTPS website and your HTTPS certificate is
> somehow invalid (but you don't know about that). You develop your stuff _for
> weeks and weeks_ in debug builds and everything is great. You prepare for
> grand APK upload to Play Store, do a {{\-\-release}} build, and... stuff
> doesn't work! You want to debug it, but you can't - because {{\-\-release}}
> build is non-debuggable! This looks super mysterious and you're totally
> baffled.
> Doing black-box debugging on --release build ain't easy, but you give it a
> try.
> You're thinking about all possible things that could go wrong (code
> minification? some issue with signing keys? Cordova/Chrome/Android are
> broken?), finally after a while you reach to google and you figure out the
> issue is due to cordova only checking HTTPS certs in {{\-\-release}} mode.
> People tell about self-signed certs, but your cert looks legit, after all, it
> works on all desktop client. But at least you know where to look.
> Luckily for you, the staging platform has a publicly accessible domain name.
> You test your cert with SSLLabs and it tells you that your server doesn't
> send all intermediary certs. It's still not sure if this is the issue, but
> you ask the ops team to update the server.
> They get a better cert and update server config to send the intermediary
> cert. You're saved! This was the missing piece to make the app work.
> 2) Suppose you never had the issue 1), you built an app, it works in
> production, all is well. One day, you change the HTTPS cert in production
> (because an old one expired etc.), you do quick tests, all is well (or, even
> worse: when in big corporation, ops guys change the HTTPS cert without
> telling you). You forget about it, and continue developing your app. You're a
> dev and you're constantly in the Chrome DevTools, so naturally you always
> build debuggable builds. You keep adding features for weeks, all works great
> in
[jira] [Comment Edited] (CB-12232) [cordova-android] Skipping HTTPS certificate validation should be hidden behind a flag, and not a default in debug builds
[
https://issues.apache.org/jira/browse/CB-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277543#comment-16277543
]
jakub-g edited comment on CB-12232 at 12/4/17 9:30 PM:
---
Hmm to fix the problem of people only checking Chrome DevTools and not logcat,
maybe what could be done is calling the following inside of
`onReceivedSslError`:
{code}
webView.evaluateJavascript("console.warn('SSL error for
$domain...')");
{code}
so basically double logging (on Java and JavaScript side). That would be
difficult to miss to anyone doing any serious work.
was (Author: jakub-g):
Hmm to fix the problem of people only checking Chrome DevTools and not logcat,
maybe what could be done is calling the following inside of
`onReceivedSslError`:
{code}
webView.evaluateJavascript("console.warn('SSL error for
$domain...')");
{code}
so basically double logging (on Java and JavaScript side). That would be
difficult to miss to anyone doing any serious work.
> [cordova-android] Skipping HTTPS certificate validation should be hidden
> behind a flag, and not a default in debug builds
> -
>
> Key: CB-12232
> URL: https://issues.apache.org/jira/browse/CB-12232
> Project: Apache Cordova
> Issue Type: Improvement
> Components: cordova-android
>Affects Versions: 6.2.0
>Reporter: jakub-g
>Priority: Critical
> Labels: android
>
> Right now, when you create a debuggable Cordova build (default behavior for
> commands like `cordova run android` etc.), it by default ignores all HTTPS
> certificate errors, as you can see in the code below:
> https://github.com/apache/cordova-android/blob/23fd0982b0faa6b7e169c2946eab07930f1f4d16/framework/src/org/apache/cordova/engine/SystemWebViewClient.java#L232-L239
> HTTPS certs are only validated when you create a release build, explicitly
> passing a flag, e.g.
> {{cordova run android --release}}
> This behavior is IMO harmful, and let me tell you why (see below for two
> real-life stories)
> *TL;DR I believe it would be better to not bind the lax HTTPS behavior to
> {{\-\-debug}} vs {{\-\-release}} build type, but hide it behind a special
> flag (to follow Chrome's naming convention, that would be
> {{\-\-ignore-certificate-errors}}, but we can name it whatever we like). This
> would expose developers to HTTPS errors much earlier in the dev process,
> which IMO is beneficial; it will also make it easier to understand and debug
> the problems, and avoid last-minute surprises.*
> _Question: do we have a portion of code already that makes runtime behavior
> depend on build-time flag? i.e. would it be easy to add a new flag in a
> similar way, without herculean effort?_
> So, the promised real-life stories:
> 1) Consider, that you have an HTTPS website and your HTTPS certificate is
> somehow invalid (but you don't know about that). You develop your stuff _for
> weeks and weeks_ in debug builds and everything is great. You prepare for
> grand APK upload to Play Store, do a {{\-\-release}} build, and... stuff
> doesn't work! You want to debug it, but you can't - because {{\-\-release}}
> build is non-debuggable! This looks super mysterious and you're totally
> baffled.
> Doing black-box debugging on --release build ain't easy, but you give it a
> try.
> You're thinking about all possible things that could go wrong (code
> minification? some issue with signing keys? Cordova/Chrome/Android are
> broken?), finally after a while you reach to google and you figure out the
> issue is due to cordova only checking HTTPS certs in {{\-\-release}} mode.
> People tell about self-signed certs, but your cert looks legit, after all, it
> works on all desktop client. But at least you know where to look.
> Luckily for you, the staging platform has a publicly accessible domain name.
> You test your cert with SSLLabs and it tells you that your server doesn't
> send all intermediary certs. It's still not sure if this is the issue, but
> you ask the ops team to update the server.
> They get a better cert and update server config to send the intermediary
> cert. You're saved! This was the missing piece to make the app work.
> 2) Suppose you never had the issue 1), you built an app, it works in
> production, all is well. One day, you change the HTTPS cert in production
> (because an old one expired etc.), you do quick tests, all is well (or, even
> worse: when in big corporation, ops guys change the HTTPS cert without
> telling you). You forget about it, and continue developing your app. You're a
> dev and you're constantly in the Chrome DevTools, so naturally you always
> build debuggable builds. You keep adding features for weeks, all works great
>
[jira] [Comment Edited] (CB-12232) [cordova-android] Skipping HTTPS certificate validation should be hidden behind a flag, and not a default in debug builds
[ https://issues.apache.org/jira/browse/CB-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277520#comment-16277520 ] jakub-g edited comment on CB-12232 at 12/4/17 9:30 PM: --- [~bowserj] I understand it might be annoying to some people that self-signed cert will be rejected, but IMO it's still a better option. Defaults that prevent head-scratching are better, even if initially inconvenient. The difference between `cordova run android` and `cordova run android --ignore-certificate-errors` is IMO not that big, people will maybe complain but that would quickly became their second nature. Alternatively, to ease the pain for those people using self-signed certs, maybe there could be a new setting in `config.xml` called sth like `IgnoreCertificateErrorsInDebugBuilds`? I think if there's an agreement to change the default behavior in the next major version, a good start might be to start logging warnings from the Java code whenever SSL failure happens, saying that in the future, those errors will be hard errors. Orthogonal to that, maybe it could be also interesting to log a warning like this: > "SSL error for domain $domain. This could be due to: Self-signed certificate; > Expired certificate; CA root not supported by the device; or misconfigured > server that is not sending all the intermediate certificates. You may want to > check your HTTPS certificate and server config with SSLLabs or similar > service." Two more points: - passing `--release` should override the `ignore-certificate-errors` flag (to prevent people from shooting themselves in the foot) - The logging I mentioned should happen only if `IgnoreCertificateErrorsInDebugBuilds` is not true / the build is not running with a `--ignore-certificate-errors` The only concern I have is that I'm not sure how many Cordova devs check logcat output. Probably most of devs only check Chrome devtools console. But a big warning in release notes of new major version + in the "getting started" / FAQ / "frequent problems" docs should probably be good enough. was (Author: jakub-g): [~bowserj] I understand it might be annoying to some people that self-signed cert will be rejected, but IMO it's still a better option. Defaults that prevent head-scratching are better, even if initially inconvenient. The difference between `cordova run android` and `cordova run android --ignore-certificate-errors` is IMO not that big, people will maybe complain but that would quickly became their second nature. Alternatively, to ease the pain for those people using self-signed certs, maybe there could be a new setting in `config.xml` called sth like `IgnoreCertificateErrorsInDebugBuilds`? I think if there's an agreement to change the default behavior in the next major version, a good start might be to start logging warnings from the Java code whenever SSL failure happens, saying that in the future, those errors will be hard errors. Orthogonal to that, maybe it could be also interesting to log a warning like this: "SSL error for domain $domain. This could be due to: Self-signed certificate; Expired certificate; CA root not supported by the device; or misconfigured server that is not sending all the intermediate certificates. You may want to check your HTTPS certificate and server config with SSLLabs or similar service." Two more points: - passing `--release` should override the `ignore-certificate-errors` flag (to prevent people from shooting themselves in the foot) - The logging I mentioned should happen only if `IgnoreCertificateErrorsInDebugBuilds` is not true / the build is not running with a `--ignore-certificate-errors` The only concern I have is that I'm not sure how many Cordova devs check logcat output. Probably most of devs only check Chrome devtools console. But a big warning in release notes of new major version + in the "getting started" / FAQ / "frequent problems" docs should probably be good enough. > [cordova-android] Skipping HTTPS certificate validation should be hidden > behind a flag, and not a default in debug builds > - > > Key: CB-12232 > URL: https://issues.apache.org/jira/browse/CB-12232 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Affects Versions: 6.2.0 >Reporter: jakub-g >Priority: Critical > Labels: android > > Right now, when you create a debuggable Cordova build (default behavior for > commands like `cordova run android` etc.), it by default ignores all HTTPS > certificate errors, as you can see in the code below: >
[jira] [Comment Edited] (CB-12232) [cordova-android] Skipping HTTPS certificate validation should be hidden behind a flag, and not a default in debug builds
[
https://issues.apache.org/jira/browse/CB-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277543#comment-16277543
]
jakub-g edited comment on CB-12232 at 12/4/17 9:29 PM:
---
Hmm to fix the problem of people only checking Chrome DevTools and not logcat,
maybe what could be done is calling the following inside of
`onReceivedSslError`:
{code}
webView.evaluateJavascript("console.warn('SSL error for
$domain...')");
{code}
so basically double logging (on Java and JavaScript side). That would be
difficult to miss to anyone doing any serious work.
was (Author: jakub-g):
Hmm to fix the problem of people only checking Chrome DevTools and not logcat,
maybe what could be done is calling the following inside of
`onReceivedSslError`:
webView.evaluateJavascript("console.warn('SSL error for
$domain...')");
so basically double logging (on Java and JavaScript side). That would be
difficult to miss to anyone doing any serious work.
> [cordova-android] Skipping HTTPS certificate validation should be hidden
> behind a flag, and not a default in debug builds
> -
>
> Key: CB-12232
> URL: https://issues.apache.org/jira/browse/CB-12232
> Project: Apache Cordova
> Issue Type: Improvement
> Components: cordova-android
>Affects Versions: 6.2.0
>Reporter: jakub-g
>Priority: Critical
> Labels: android
>
> Right now, when you create a debuggable Cordova build (default behavior for
> commands like `cordova run android` etc.), it by default ignores all HTTPS
> certificate errors, as you can see in the code below:
> https://github.com/apache/cordova-android/blob/23fd0982b0faa6b7e169c2946eab07930f1f4d16/framework/src/org/apache/cordova/engine/SystemWebViewClient.java#L232-L239
> HTTPS certs are only validated when you create a release build, explicitly
> passing a flag, e.g.
> {{cordova run android --release}}
> This behavior is IMO harmful, and let me tell you why (see below for two
> real-life stories)
> *TL;DR I believe it would be better to not bind the lax HTTPS behavior to
> {{\-\-debug}} vs {{\-\-release}} build type, but hide it behind a special
> flag (to follow Chrome's naming convention, that would be
> {{\-\-ignore-certificate-errors}}, but we can name it whatever we like). This
> would expose developers to HTTPS errors much earlier in the dev process,
> which IMO is beneficial; it will also make it easier to understand and debug
> the problems, and avoid last-minute surprises.*
> _Question: do we have a portion of code already that makes runtime behavior
> depend on build-time flag? i.e. would it be easy to add a new flag in a
> similar way, without herculean effort?_
> So, the promised real-life stories:
> 1) Consider, that you have an HTTPS website and your HTTPS certificate is
> somehow invalid (but you don't know about that). You develop your stuff _for
> weeks and weeks_ in debug builds and everything is great. You prepare for
> grand APK upload to Play Store, do a {{\-\-release}} build, and... stuff
> doesn't work! You want to debug it, but you can't - because {{\-\-release}}
> build is non-debuggable! This looks super mysterious and you're totally
> baffled.
> Doing black-box debugging on --release build ain't easy, but you give it a
> try.
> You're thinking about all possible things that could go wrong (code
> minification? some issue with signing keys? Cordova/Chrome/Android are
> broken?), finally after a while you reach to google and you figure out the
> issue is due to cordova only checking HTTPS certs in {{\-\-release}} mode.
> People tell about self-signed certs, but your cert looks legit, after all, it
> works on all desktop client. But at least you know where to look.
> Luckily for you, the staging platform has a publicly accessible domain name.
> You test your cert with SSLLabs and it tells you that your server doesn't
> send all intermediary certs. It's still not sure if this is the issue, but
> you ask the ops team to update the server.
> They get a better cert and update server config to send the intermediary
> cert. You're saved! This was the missing piece to make the app work.
> 2) Suppose you never had the issue 1), you built an app, it works in
> production, all is well. One day, you change the HTTPS cert in production
> (because an old one expired etc.), you do quick tests, all is well (or, even
> worse: when in big corporation, ops guys change the HTTPS cert without
> telling you). You forget about it, and continue developing your app. You're a
> dev and you're constantly in the Chrome DevTools, so naturally you always
> build debuggable builds. You keep adding features for weeks, all works great
> in your
[jira] [Commented] (CB-12232) [cordova-android] Skipping HTTPS certificate validation should be hidden behind a flag, and not a default in debug builds
[
https://issues.apache.org/jira/browse/CB-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277543#comment-16277543
]
jakub-g commented on CB-12232:
--
Hmm to fix the problem of people only checking Chrome DevTools and not logcat,
maybe what could be done is calling the following inside of
`onReceivedSslError`:
webView.evaluateJavascript("console.warn('SSL error for
$domain...')");
so basically double logging (on Java and JavaScript side). That would be
difficult to miss to anyone doing any serious work.
> [cordova-android] Skipping HTTPS certificate validation should be hidden
> behind a flag, and not a default in debug builds
> -
>
> Key: CB-12232
> URL: https://issues.apache.org/jira/browse/CB-12232
> Project: Apache Cordova
> Issue Type: Improvement
> Components: cordova-android
>Affects Versions: 6.2.0
>Reporter: jakub-g
>Priority: Critical
> Labels: android
>
> Right now, when you create a debuggable Cordova build (default behavior for
> commands like `cordova run android` etc.), it by default ignores all HTTPS
> certificate errors, as you can see in the code below:
> https://github.com/apache/cordova-android/blob/23fd0982b0faa6b7e169c2946eab07930f1f4d16/framework/src/org/apache/cordova/engine/SystemWebViewClient.java#L232-L239
> HTTPS certs are only validated when you create a release build, explicitly
> passing a flag, e.g.
> {{cordova run android --release}}
> This behavior is IMO harmful, and let me tell you why (see below for two
> real-life stories)
> *TL;DR I believe it would be better to not bind the lax HTTPS behavior to
> {{\-\-debug}} vs {{\-\-release}} build type, but hide it behind a special
> flag (to follow Chrome's naming convention, that would be
> {{\-\-ignore-certificate-errors}}, but we can name it whatever we like). This
> would expose developers to HTTPS errors much earlier in the dev process,
> which IMO is beneficial; it will also make it easier to understand and debug
> the problems, and avoid last-minute surprises.*
> _Question: do we have a portion of code already that makes runtime behavior
> depend on build-time flag? i.e. would it be easy to add a new flag in a
> similar way, without herculean effort?_
> So, the promised real-life stories:
> 1) Consider, that you have an HTTPS website and your HTTPS certificate is
> somehow invalid (but you don't know about that). You develop your stuff _for
> weeks and weeks_ in debug builds and everything is great. You prepare for
> grand APK upload to Play Store, do a {{\-\-release}} build, and... stuff
> doesn't work! You want to debug it, but you can't - because {{\-\-release}}
> build is non-debuggable! This looks super mysterious and you're totally
> baffled.
> Doing black-box debugging on --release build ain't easy, but you give it a
> try.
> You're thinking about all possible things that could go wrong (code
> minification? some issue with signing keys? Cordova/Chrome/Android are
> broken?), finally after a while you reach to google and you figure out the
> issue is due to cordova only checking HTTPS certs in {{\-\-release}} mode.
> People tell about self-signed certs, but your cert looks legit, after all, it
> works on all desktop client. But at least you know where to look.
> Luckily for you, the staging platform has a publicly accessible domain name.
> You test your cert with SSLLabs and it tells you that your server doesn't
> send all intermediary certs. It's still not sure if this is the issue, but
> you ask the ops team to update the server.
> They get a better cert and update server config to send the intermediary
> cert. You're saved! This was the missing piece to make the app work.
> 2) Suppose you never had the issue 1), you built an app, it works in
> production, all is well. One day, you change the HTTPS cert in production
> (because an old one expired etc.), you do quick tests, all is well (or, even
> worse: when in big corporation, ops guys change the HTTPS cert without
> telling you). You forget about it, and continue developing your app. You're a
> dev and you're constantly in the Chrome DevTools, so naturally you always
> build debuggable builds. You keep adding features for weeks, all works great
> in your debuggable builds. Your QAs do tests and most often stuff works
> great, but sometimes they're getting weird connection issues. First they
> think it's some weird connectivity issue (poor WiFi etc.), but the issues
> happen more often. Turns out the issue happens _only with --release builds_
> and _only on production server_. There's a fire in production, but no one
> noticed for quite a while since the QA test features mostly on staging
> servers, and devs work
[jira] [Comment Edited] (CB-12232) [cordova-android] Skipping HTTPS certificate validation should be hidden behind a flag, and not a default in debug builds
[ https://issues.apache.org/jira/browse/CB-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277520#comment-16277520 ] jakub-g edited comment on CB-12232 at 12/4/17 9:20 PM: --- [~bowserj] I understand it might be annoying to some people that self-signed cert will be rejected, but IMO it's still a better option. Defaults that prevent head-scratching are better, even if initially inconvenient. The difference between `cordova run android` and `cordova run android --ignore-certificate-errors` is IMO not that big, people will maybe complain but that would quickly became their second nature. Alternatively, to ease the pain for those people using self-signed certs, maybe there could be a new setting in `config.xml` called sth like `IgnoreCertificateErrorsInDebugBuilds`? I think if there's an agreement to change the default behavior in the next major version, a good start might be to start logging warnings from the Java code whenever SSL failure happens, saying that in the future, those errors will be hard errors. Orthogonal to that, maybe it could be also interesting to log a warning like this: "SSL error for domain $domain. This could be due to: Self-signed certificate; Expired certificate; CA root not supported by the device; or misconfigured server that is not sending all the intermediate certificates. You may want to check your HTTPS certificate and server config with SSLLabs or similar service." Two more points: - passing `--release` should override the `ignore-certificate-errors` flag (to prevent people from shooting themselves in the foot) - The logging I mentioned should happen only if `IgnoreCertificateErrorsInDebugBuilds` is not true / the build is not running with a `--ignore-certificate-errors` The only concern I have is that I'm not sure how many Cordova devs check logcat output. Probably most of devs only check Chrome devtools console. But a big warning in release notes of new major version + in the "getting started" / FAQ / "frequent problems" docs should probably be good enough. was (Author: jakub-g): [~bowserj] I understand it might be annoying to some people that self-signed cert will be rejected, but IMO it's still a better option. Defaults that prevent head-scratching are better, even if initially inconvenient. The difference between `cordova run android` and `cordova run android --ignore-certificate-errors` is IMO not that big, people will maybe complain but that would quickly became their second nature. Alternatively, to ease the pain for those people using self-signed certs, maybe there could be a new setting in `config.xml` called sth like `IgnoreCertificateErrorsInDebugBuilds`? I think if there's an agreement to change the default behavior in the next major version, a good start might be to start logging warnings from the Java code whenever SSL failure happens, saying that in the future, those errors will be hard errors. Orthogonal to that, maybe it could be also interesting to log a warning like this: "SSL error for domain $domain. This could be due to: Self-signed certificate; Expired certificate; CA root not supported by the device; or misconfigured server that is not sending all the intermediate certificates. You may want to check your HTTPS certificate and server config with SSLLabs or similar service." Two more points: - passing `--release` should override the `--ignore-certificate-errors` flag (to prevent people from shooting themselves in the foot) - The logging I mentioned should happen only if `IgnoreCertificateErrorsInDebugBuilds` is not true / the build is not running with a `--ignore-certificate-errors` The only concern I have is that I'm not sure how many Cordova devs check logcat output. Probably most of devs only check Chrome devtools console. But a big warning in release notes of new major version + in the "getting started" / FAQ / "frequent problems" docs should probably be good enough. > [cordova-android] Skipping HTTPS certificate validation should be hidden > behind a flag, and not a default in debug builds > - > > Key: CB-12232 > URL: https://issues.apache.org/jira/browse/CB-12232 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Affects Versions: 6.2.0 >Reporter: jakub-g >Priority: Critical > Labels: android > > Right now, when you create a debuggable Cordova build (default behavior for > commands like `cordova run android` etc.), it by default ignores all HTTPS > certificate errors, as you can see in the code below: >
[jira] [Commented] (CB-12232) [cordova-android] Skipping HTTPS certificate validation should be hidden behind a flag, and not a default in debug builds
[
https://issues.apache.org/jira/browse/CB-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277520#comment-16277520
]
jakub-g commented on CB-12232:
--
[~bowserj] I understand it might be annoying to some people that self-signed
cert will be rejected, but IMO it's still a better option. Defaults that
prevent head-scratching are better, even if initially inconvenient.
The difference between `cordova run android` and `cordova run android
--ignore-certificate-errors` is IMO not that big, people will maybe complain
but that would quickly became their second nature.
Alternatively, to ease the pain for those people using self-signed certs, maybe
there could be a new setting in `config.xml` called sth like
`IgnoreCertificateErrorsInDebugBuilds`?
I think if there's an agreement to change the default behavior in the next
major version, a good start might be to start logging warnings from the Java
code whenever SSL failure happens, saying that in the future, those errors will
be hard errors.
Orthogonal to that, maybe it could be also interesting to log a warning like
this:
"SSL error for domain $domain. This could be due to: Self-signed certificate;
Expired certificate; CA root not supported by the device; or misconfigured
server that is not sending all the intermediate certificates. You may want to
check your HTTPS certificate and server config with SSLLabs or similar service."
Two more points:
- passing `--release` should override the `--ignore-certificate-errors` flag
(to prevent people from shooting themselves in the foot)
- The logging I mentioned should happen only if
`IgnoreCertificateErrorsInDebugBuilds` is not true / the build is not running
with a `--ignore-certificate-errors`
The only concern I have is that I'm not sure how many Cordova devs check logcat
output. Probably most of devs only check Chrome devtools console.
But a big warning in release notes of new major version + in the "getting
started" / FAQ / "frequent problems" docs should probably be good enough.
> [cordova-android] Skipping HTTPS certificate validation should be hidden
> behind a flag, and not a default in debug builds
> -
>
> Key: CB-12232
> URL: https://issues.apache.org/jira/browse/CB-12232
> Project: Apache Cordova
> Issue Type: Improvement
> Components: cordova-android
>Affects Versions: 6.2.0
>Reporter: jakub-g
>Priority: Critical
> Labels: android
>
> Right now, when you create a debuggable Cordova build (default behavior for
> commands like `cordova run android` etc.), it by default ignores all HTTPS
> certificate errors, as you can see in the code below:
> https://github.com/apache/cordova-android/blob/23fd0982b0faa6b7e169c2946eab07930f1f4d16/framework/src/org/apache/cordova/engine/SystemWebViewClient.java#L232-L239
> HTTPS certs are only validated when you create a release build, explicitly
> passing a flag, e.g.
> {{cordova run android --release}}
> This behavior is IMO harmful, and let me tell you why (see below for two
> real-life stories)
> *TL;DR I believe it would be better to not bind the lax HTTPS behavior to
> {{\-\-debug}} vs {{\-\-release}} build type, but hide it behind a special
> flag (to follow Chrome's naming convention, that would be
> {{\-\-ignore-certificate-errors}}, but we can name it whatever we like). This
> would expose developers to HTTPS errors much earlier in the dev process,
> which IMO is beneficial; it will also make it easier to understand and debug
> the problems, and avoid last-minute surprises.*
> _Question: do we have a portion of code already that makes runtime behavior
> depend on build-time flag? i.e. would it be easy to add a new flag in a
> similar way, without herculean effort?_
> So, the promised real-life stories:
> 1) Consider, that you have an HTTPS website and your HTTPS certificate is
> somehow invalid (but you don't know about that). You develop your stuff _for
> weeks and weeks_ in debug builds and everything is great. You prepare for
> grand APK upload to Play Store, do a {{\-\-release}} build, and... stuff
> doesn't work! You want to debug it, but you can't - because {{\-\-release}}
> build is non-debuggable! This looks super mysterious and you're totally
> baffled.
> Doing black-box debugging on --release build ain't easy, but you give it a
> try.
> You're thinking about all possible things that could go wrong (code
> minification? some issue with signing keys? Cordova/Chrome/Android are
> broken?), finally after a while you reach to google and you figure out the
> issue is due to cordova only checking HTTPS certs in {{\-\-release}} mode.
> People tell about self-signed certs, but your cert looks legit, after all, it
> works on
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277471#comment-16277471 ] ASF GitHub Bot commented on CB-13620: - janpio commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154739970 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback Review comment: Is everything starting with "will most ..." expected to be here? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277473#comment-16277473 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154752488 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback Review comment: Yes, it's the commit message. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277456#comment-16277456 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154768926 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: OK, I added a brief mention after the first paragraph and copy-pasted your code example. BTW: We can all edit the PR in GitHub itself, so nothing is stopping any reviewer from doing these changes. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277455#comment-16277455 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154768926 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: OK, I added a brief mention after the first paragraph and copy-pasted your code example. BTW: We can all edit the PR in GitHub itself. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277449#comment-16277449 ] ASF GitHub Bot commented on CB-13620: - macdonst commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154767756 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: @dpogue no one needs to use cordova-plugin-allow-backup as they can just add those lines in config.xml instead. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277415#comment-16277415 ] ASF GitHub Bot commented on CB-13620: - dpogue commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154762792 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: https://github.com/macdonst/cordova-plugin-allow-backup is one, I know I've used edit-config in a few of my company's internal plugins This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277403#comment-16277403 ] ASF GitHub Bot commented on CB-13620: - macdonst commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154760885 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: CSDK plugins are affected by this but they are not being actively maintained. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277399#comment-16277399 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154759987 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: Fair enough. That said, what's an example plugin that is widely used that would be broken by this? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277395#comment-16277395 ] ASF GitHub Bot commented on CB-13620: - dpogue commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154759402 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: Then we should also mention that it's not possible for a plugin using `edit-config` to support both cordova-android@6 and cordova-android@7? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13634) Allow to keep the splashscreen window in onPause on Android
[ https://issues.apache.org/jira/browse/CB-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277392#comment-16277392 ] Jan Piotrowski (Sujan) edited comment on CB-13634 at 12/4/17 7:59 PM: -- I am asking so specific as this "feels" like code that might not even be necessary any more... Did some digging: https://github.com/agrieve/cordova-android/blame/c255a849411826e98d4cbc9b4c3211cb23e8d6b8/framework/src/org/apache/cordova/CordovaActivity.java#L589 That code is 6 years old :) (originally lived in `cordova-android` directly) https://issues.apache.org/jira/browse/CB-952 [~macdonst] What do you think? Better keep it and add this additional option or get rid of it? was (Author: sujan12): I am asking so specific as this "feels" like code that might not even be necessary any more... https://github.com/agrieve/cordova-android/blame/c255a849411826e98d4cbc9b4c3211cb23e8d6b8/framework/src/org/apache/cordova/CordovaActivity.java#L589 That code is 6 years old :) (originally lived in `cordova-android` directly) https://issues.apache.org/jira/browse/CB-952 [~macdonst] What do you think? Better keep it and add this additional option or get rid of it? > Allow to keep the splashscreen window in onPause on Android > --- > > Key: CB-13634 > URL: https://issues.apache.org/jira/browse/CB-13634 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-splashscreen >Reporter: Michael Goffioul >Priority: Minor > > I have a use case whereby my webapp is launching another app while the > splashscreen is visible, and I want to keep the splashscreen window visible > to prevent unfriendly transient update during the app switching animation on > Android. It would be handy to allow an app to override the default behavior > of removing the splashscreen window in onPause. -- 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-13634) Allow to keep the splashscreen window in onPause on Android
[ https://issues.apache.org/jira/browse/CB-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277392#comment-16277392 ] Jan Piotrowski (Sujan) edited comment on CB-13634 at 12/4/17 7:59 PM: -- I am asking so specific as this "feels" like code that might not even be necessary any more... Did some digging: https://github.com/agrieve/cordova-android/blame/c255a849411826e98d4cbc9b4c3211cb23e8d6b8/framework/src/org/apache/cordova/CordovaActivity.java#L589 That code is 6 years old :) (originally lived in `cordova-android` directly) https://issues.apache.org/jira/browse/CB-952 [~macdonst] What do you think? Better keep it and add this additional option or get rid of it? You fixed this back then! was (Author: sujan12): I am asking so specific as this "feels" like code that might not even be necessary any more... Did some digging: https://github.com/agrieve/cordova-android/blame/c255a849411826e98d4cbc9b4c3211cb23e8d6b8/framework/src/org/apache/cordova/CordovaActivity.java#L589 That code is 6 years old :) (originally lived in `cordova-android` directly) https://issues.apache.org/jira/browse/CB-952 [~macdonst] What do you think? Better keep it and add this additional option or get rid of it? > Allow to keep the splashscreen window in onPause on Android > --- > > Key: CB-13634 > URL: https://issues.apache.org/jira/browse/CB-13634 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-splashscreen >Reporter: Michael Goffioul >Priority: Minor > > I have a use case whereby my webapp is launching another app while the > splashscreen is visible, and I want to keep the splashscreen window visible > to prevent unfriendly transient update during the app switching animation on > Android. It would be handy to allow an app to override the default behavior > of removing the splashscreen window in onPause. -- 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-13634) Allow to keep the splashscreen window in onPause on Android
[ https://issues.apache.org/jira/browse/CB-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277392#comment-16277392 ] Jan Piotrowski (Sujan) commented on CB-13634: - I am asking so specific as this "feels" like code that might not even be necessary any more... https://github.com/agrieve/cordova-android/blame/c255a849411826e98d4cbc9b4c3211cb23e8d6b8/framework/src/org/apache/cordova/CordovaActivity.java#L589 That code is 6 years old :) (originally lived in `cordova-android` directly) https://issues.apache.org/jira/browse/CB-952 [~macdonst] What do you think? Better keep it and add this additional option or get rid of it? > Allow to keep the splashscreen window in onPause on Android > --- > > Key: CB-13634 > URL: https://issues.apache.org/jira/browse/CB-13634 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-splashscreen >Reporter: Michael Goffioul >Priority: Minor > > I have a use case whereby my webapp is launching another app while the > splashscreen is visible, and I want to keep the splashscreen window visible > to prevent unfriendly transient update during the app switching animation on > Android. It would be handy to allow an app to override the default behavior > of removing the splashscreen window in onPause. -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277388#comment-16277388 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154758201 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: I don't believe any of edit-config's functionality has been changed. Of course, we only test on our own plugins, and none of those use edit-config on Android, only on iOS. I'm sure it's possible to add this special case, but that would mean that we would be on the hook for maintaining it, when people really should be editing the path. I think we wrote enough new workaround code for this change already. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277382#comment-16277382 ] ASF GitHub Bot commented on CB-13620: - janpio commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154756733 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback +* Adding the Studio Builder to build a project based on **Android** Studio, and deleting Ant, since Google does not support Ant Builds anymore. Sorry guys! Review comment: Removing the word - as you did - is totally fine, thank you. This is an automated message from the Apache Git Service. To
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277378#comment-16277378 ] ASF GitHub Bot commented on CB-13620: - dpogue commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154756036 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: Actually, if you search GitHub for `edit-config`, it seems like 99% of them are editing AndroidManifest.xml. Is it possible to special case that so it uses the right path? Did that already happen in cordova-common and we're waiting for a tools release? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13634) Allow to keep the splashscreen window in onPause on Android
[ https://issues.apache.org/jira/browse/CB-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277364#comment-16277364 ] Michael Goffioul commented on CB-13634: --- > Oh ok, so because of the `removeSplashScreen` call on pause of the app the > app can flicker if the splashscreen is still showing, correct? Yes. In my case, I want to keep the splashscreen while switching to another app. But because my app is being paused, the splashscreen window gets removed. > Do you know what the original comment "hide the splash screen to avoid > leaking a window" refers to above that call? I'm not sure, but I would say it might be because there is (or used to be) no guarantee that Android calls any other activity lifecycle method after onPause. I'm not sure whether that would leave a visible window on screen, I've never experienced it, but I would assume that when Android kills an app, all associated windows are also automatically removed. There might be some traces in the logs (like a backtrace), but no other visible effects. In all cases, the proposed PR just allow an app to change the default behavior, keeping things backward compatible. > Allow to keep the splashscreen window in onPause on Android > --- > > Key: CB-13634 > URL: https://issues.apache.org/jira/browse/CB-13634 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-splashscreen >Reporter: Michael Goffioul >Priority: Minor > > I have a use case whereby my webapp is launching another app while the > splashscreen is visible, and I want to keep the splashscreen window visible > to prevent unfriendly transient update during the app switching animation on > Android. It would be handy to allow an app to override the default behavior > of removing the splashscreen window in onPause. -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277361#comment-16277361 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154754428 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback +* Adding the Studio Builder to build a project based on **Android** Studio, and deleting Ant, since Google does not support Ant Builds anymore. Sorry guys! Review comment: @janpio The commit is in the changelog because dropping ANT support is important. I've edited it. It was an innocent mistake that I can't fix without violating a bunch of ASF
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277354#comment-16277354 ] ASF GitHub Bot commented on CB-13620: - janpio commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154753714 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback +* Adding the Studio Builder to build a project based on **Android** Studio, and deleting Ant, since Google does not support Ant Builds anymore. Sorry guys! Review comment: No, as it says "Curated Changelog" as headline above. The commit message was similarly problematic then. No need to keep this in the blog post though.
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277350#comment-16277350 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154752339 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback +* Adding the Studio Builder to build a project based on **Android** Studio, and deleting Ant, since Google does not support Ant Builds anymore. Sorry guys! Review comment: You are aware that this is taken directly from the commit messages, right? I can change that here, but I'm not changing the commit message since that would involve a force push on
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277345#comment-16277345 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154753058 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: That's a good idea. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277348#comment-16277348 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154752339 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback +* Adding the Studio Builder to build a project based on **Android** Studio, and deleting Ant, since Google does not support Ant Builds anymore. Sorry guys! Review comment: You are aware that this is taken directly from the commit messages, right? I can change that here, but I'm not changing the commit message.
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277343#comment-16277343 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154752488 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback Review comment: Yes, it's the commit message. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277342#comment-16277342 ] ASF GitHub Bot commented on CB-13620: - infil00p commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154752339 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback +* Adding the Studio Builder to build a project based on **Android** Studio, and deleting Ant, since Google does not support Ant Builds anymore. Sorry guys! Review comment: You are aware that this is taken directly from the commit messages, right? This is an automated message from the Apache
[jira] [Commented] (CB-13634) Allow to keep the splashscreen window in onPause on Android
[ https://issues.apache.org/jira/browse/CB-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277326#comment-16277326 ] Jan Piotrowski (Sujan) commented on CB-13634: - Oh ok, so because of the `removeSplashScreen` call on pause of the app the app can flicker if the splashscreen is still showing, correct? Do you know what the original comment "hide the splash screen to avoid leaking a window" refers to above that call? > Allow to keep the splashscreen window in onPause on Android > --- > > Key: CB-13634 > URL: https://issues.apache.org/jira/browse/CB-13634 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-splashscreen >Reporter: Michael Goffioul >Priority: Minor > > I have a use case whereby my webapp is launching another app while the > splashscreen is visible, and I want to keep the splashscreen window visible > to prevent unfriendly transient update during the app switching animation on > Android. It would be handy to allow an app to override the default behavior > of removing the splashscreen window in onPause. -- 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-13634) Allow to keep the splashscreen window in onPause on Android
[ https://issues.apache.org/jira/browse/CB-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277320#comment-16277320 ] Michael Goffioul commented on CB-13634: --- > What exactly does that mean? Can you illustrate? The removal of the splashscreen reveals the WebView component and whatever content is loaded at that time. This is happening during the app switching transition, and it looks like the screen is flickering, giving a bad user experience. > Allow to keep the splashscreen window in onPause on Android > --- > > Key: CB-13634 > URL: https://issues.apache.org/jira/browse/CB-13634 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-splashscreen >Reporter: Michael Goffioul >Priority: Minor > > I have a use case whereby my webapp is launching another app while the > splashscreen is visible, and I want to keep the splashscreen window visible > to prevent unfriendly transient update during the app switching animation on > Android. It would be handy to allow an app to override the default behavior > of removing the splashscreen window in onPause. -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277317#comment-16277317 ] ASF GitHub Bot commented on CB-13620: - dpogue commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154749429 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. Review comment: We probably need to add something here to tell people that `edit-config` tags in plugin.xml and config.xml will need their paths updated? i.e., ```xml ``` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13523) Add build config option to enable Xcode automatic provisioning
[
https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277313#comment-16277313
]
ASF GitHub Bot commented on CB-13523:
-
surajpindoria closed pull request #762: CB-13523: Add automaticProvisioning to
iOS signing docs
URL: https://github.com/apache/cordova-docs/pull/762
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/www/docs/en/dev/guide/platforms/ios/index.md
b/www/docs/en/dev/guide/platforms/ios/index.md
index de400e6fe..2c6300a77 100644
--- a/www/docs/en/dev/guide/platforms/ios/index.md
+++ b/www/docs/en/dev/guide/platforms/ios/index.md
@@ -160,10 +160,11 @@ To sign an app, you need the following parameters:
| Parameter| Flag | Description
|--|--|---
| Code Sign Identity | `--codeSignIdentity` | Code signing identity
to use for signing. It can be created with Xcode and added to your keychain.
Starting with Xcode 8 you should use `--codeSignIdentity="iPhone Developer"`
both for `debug` and `release`.
-| Provisioning Profile | `--provisioningProfile` | GUID of the
provisioning profile to be used for signing. It is copied here on your Mac:
```~/Library/MobileDevice/Provisioning\ Profiles/```. Opening it in a text
editor, you can find the GUID which needs to be specified here.
-| Code Sign Resource Rules | `--codesignResourceRules`| (Optional) Used to
control which files in a bundle should be sealed by a code signature. For more
details, read [The OS X Code Signing In Depth
article](https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG206)
-| Development Team | `--developmentTeam` | This is new for Xcode
8. The development team ([Team
ID](https://developer.apple.com/account/#/membership/)) to use for code
signing. You would use this setting and a simplified Code Sign Identity (i.e.
just 'iPhone Developer') to sign your apps, you do not need to provide a
Provisioning Profile.
+| Development Team | `--developmentTeam` | The development team
([Team ID](https://developer.apple.com/account/#/membership/)) to use for code
signing. You would use this setting and a simplified Code Sign Identity (i.e.
just 'iPhone Developer') to sign your apps, you do not need to provide a
Provisioning Profile.
| Packaging Type | `--packageType` | This will determine
what type of build is generated by Xcode. Valid options are `development` (the
default), `enterprise`, `ad-hoc`, and `app-store`.
+| Provisioning Profile | `--provisioningProfile` | (Optional) GUID of the
provisioning profile to be used for manual signing. It is copied here on your
Mac: ```~/Library/MobileDevice/Provisioning\ Profiles/```. Opening it in a text
editor, you can find the GUID which needs to be specified here if using manual
signing.
+| Code Sign Resource Rules | `--codesignResourceRules`| (Optional) Used to
control which files in a bundle should be sealed by a code signature. For more
details, read [The OS X Code Signing In Depth
article](https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG206)
+| Automatic Provisioning | `--automaticProvisioning`| (Optional) Enable to
allow Xcode to automatically manage provisioning profiles. Valid options are
`false` (the default) and `true`.
### Using build.json
@@ -171,7 +172,7 @@ Alternatively, you could specify them in a build
configuration file (`build.json
using the `--buildConfig` argument to the same commands. Here's a sample of a
build configuration file:
-Xcode 8 and iOS 10:
+For automatic signing, where provisioning profiles are managed automatically
by Xcode (recommended):
```json
{
@@ -180,6 +181,7 @@ Xcode 8 and iOS 10:
"codeSignIdentity": "iPhone Developer",
"developmentTeam": "FG35JLLMXX4A",
"packageType": "development",
+"automaticProvisioning": true,
"buildFlag": [
"EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
"ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
@@ -190,6 +192,7 @@ Xcode 8 and iOS 10:
"codeSignIdentity": "iPhone Developer",
"developmentTeam": "FG35JLLMXX4A",
"packageType": "app-store",
+"automaticProvisioning": true,
"buildFlag": [
"EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
"ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
@@ -200,7 +203,7 @@ Xcode 8 and iOS 10:
}
```
-Earlier versions:
+For manual signing, specifying the
[jira] [Commented] (CB-13523) Add build config option to enable Xcode automatic provisioning
[ https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277311#comment-16277311 ] ASF GitHub Bot commented on CB-13523: - surajpindoria commented on issue #762: CB-13523: Add automaticProvisioning to iOS signing docs URL: https://github.com/apache/cordova-docs/pull/762#issuecomment-349075699 Cool! Forgot about this PR, merging in! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add build config option to enable Xcode automatic provisioning > -- > > Key: CB-13523 > URL: https://issues.apache.org/jira/browse/CB-13523 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-ios > Environment: Xcode 9 > Cordova-iOS 4.5.3 >Reporter: Darryl Pogue >Assignee: Darryl Pogue > Fix For: cordova-ios@4.5.4 > > > Xcode 9 made more changes to how provisioning works for apps, particularly > around manual vs automatic signing. > The changes required to support manual signing of release builds was > implemented as part of CB-13315. > In order for automatic signing to work, we need to pass an additional flag to > xcodebuild to allow Xcode to manage automatically updating provisioning > profiles as needed. I want to keep this being a build config option because > many people may not want to grant Xcode such power by default. -- 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-13523) Add build config option to enable Xcode automatic provisioning
[ https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277269#comment-16277269 ] ASF GitHub Bot commented on CB-13523: - dpogue commented on issue #762: CB-13523: Add automaticProvisioning to iOS signing docs URL: https://github.com/apache/cordova-docs/pull/762#issuecomment-349068903 This has now been released in Cordova-iOS 4.5.4 and can be merged This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add build config option to enable Xcode automatic provisioning > -- > > Key: CB-13523 > URL: https://issues.apache.org/jira/browse/CB-13523 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-ios > Environment: Xcode 9 > Cordova-iOS 4.5.3 >Reporter: Darryl Pogue >Assignee: Darryl Pogue > Fix For: cordova-ios@4.5.4 > > > Xcode 9 made more changes to how provisioning works for apps, particularly > around manual vs automatic signing. > The changes required to support manual signing of release builds was > implemented as part of CB-13315. > In order for automatic signing to work, we need to pass an additional flag to > xcodebuild to allow Xcode to manage automatically updating provisioning > profiles as needed. I want to keep this being a build config option because > many people may not want to grant Xcode such power by default. -- 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-13634) Allow to keep the splashscreen window in onPause on Android
[ https://issues.apache.org/jira/browse/CB-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277259#comment-16277259 ] Jan Piotrowski (Sujan) commented on CB-13634: - > unfriendly transient update during the app switching animation on Android. What exactly does that mean? Can you illustrate? > Allow to keep the splashscreen window in onPause on Android > --- > > Key: CB-13634 > URL: https://issues.apache.org/jira/browse/CB-13634 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-splashscreen >Reporter: Michael Goffioul >Priority: Minor > > I have a use case whereby my webapp is launching another app while the > splashscreen is visible, and I want to keep the splashscreen window visible > to prevent unfriendly transient update during the app switching animation on > Android. It would be handy to allow an app to override the default behavior > of removing the splashscreen window in onPause. -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277255#comment-16277255 ] ASF GitHub Bot commented on CB-13620: - janpio commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154740404 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback +* Adding the Studio Builder to build a project based on **Android** Studio, and deleting Ant, since Google does not support Ant Builds anymore. Sorry guys! Review comment: Sorry guys => Sorry folks This is an automated message from the Apache Git Service. To respond to the message, please log
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277251#comment-16277251 ] ASF GitHub Bot commented on CB-13620: - janpio commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154739970 ## File path: www/_posts/2017-12-04-cordova-android-7.0.0.md ## @@ -0,0 +1,58 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 7.0.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 7.0.0` has been released! + +With this release, we have changed the default project structure for Android projects. People who currently use the CLI and treat everything in the platforms directory as a +build artifact should not notice a difference, however this a major breaking change for people creating standalone Cordova Android projects. This also means that the locations +of files have changed and have been brought in line to the structure used by Android Studio. + +## Major Changes include: + * Support for Java 1.8 language features in Cordova Plugins + * CordovaInterface now has a Context getter so that contexts can be retrieved without an Activity + * Cordova can now build for x86_64, arm64 and armeabi architecture when building plugins that use the NDK + * The minimum Android API version supported is now API Level 19 + * Due to the directory structure change, we no longer support in-line upgrading, bringing us in line with iOS + * ANT builds are no longer supported and the functionality has been removed. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform remove android +cordova platform add android@7.0.0 + +To add it explicitly: + +cordova platform add android@7.0.0 + + +## Curated Changelog +* [CB-13612](https://issues.apache.org/jira/browse/CB-13612) Fix the remapper so that XML files copy over and the Camera works again. +* [CB-13741](https://issues.apache.org/jira/browse/CB-13741) Bump `package.json` so we can install plugins +* [CB-13610](https://issues.apache.org/jira/browse/CB-13610) Compress the default app assets +* [CB-12835](https://issues.apache.org/jira/browse/CB-12835) add a Context getter in CordovaInterface +* [CB-8976](https://issues.apache.org/jira/browse/CB-8976) Added the `cdvVersionCodeForceAbiDigit` flag to the template build.gradle that appends 0 to the versionCode when `cdvBuildMultipleApks` is not set +* [CB-12291](https://issues.apache.org/jira/browse/CB-12291) (android) Add x86_64, arm64 and armeabi architecture flavors +* [CB-13602](https://issues.apache.org/jira/browse/CB-13602) We were setting the path wrong, this is hacky but it works +* [CB-13601](https://issues.apache.org/jira/browse/CB-13601) Fixing the standalone run scripts to make sure this works without using the CLI +* [CB-13580](https://issues.apache.org/jira/browse/CB-13580) fix build for multiple apks (different product flavors) +* [CB-13558](https://issues.apache.org/jira/browse/CB-13558) Upgrading the gradle so we can upload the AAR +* [CB-13297](https://issues.apache.org/jira/browse/CB-13297) This just works once you bump the project structure. Java 1.8 compatibility baked-in +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) **Android** Studio 3 work, things have changed with how the platform is built +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug where the gradle subproject changes weren't actually getting written to the correct gradle file +* [CB-13470](https://issues.apache.org/jira/browse/CB-13470) Fix Clean so that it cleans the **Android** Studio structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Adding specs for resource files inside an **Android** Studio Project +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Added remapping for drawables +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Found bug in Api.js where xml/strings.xml is used instead of values/strings.xml +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Setup Api.js to support multiple builders based on project structure +* [CB-11244](https://issues.apache.org/jira/browse/CB-11244) Changing directory creation, will most likely hide this behind a flag for the next release of `cordova-android`, and then make it default in the next major pending feedback Review comment: Is everything starting with "will most ..." expected to be here? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact
[jira] [Commented] (CB-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277247#comment-16277247 ] ASF GitHub Bot commented on CB-13620: - janpio commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154739525 ## File path: www/docs/en/dev/guide/platforms/android/upgrade.md ## @@ -27,6 +27,48 @@ Most of these instructions apply to projects created with an older set of command-line tools that precede the `cordova` CLI utility. See [The Command-Line Interface](../../cli/index.html) for information how to update the version of the CLI. + +## Upgrading to 7.X.X + +The best way to upgrade to 5.X.X is to simply remove the Android platform from +your project and re-add it with the new version. For example, + +```bash +cordova platform remove android +cordova platform add android@7.X.X +``` + +If you use the above method, be aware that any changes you made to the android +platform folder will be lost (editing the contents of this folder is +discouraged). + +Unfortunately, due to the update in file structure, non-CLI projects will have +to be updated manually, or a new Cordova project will have to be created, and the +files transferred to the new project. This is due to the migration to Android Studio. + +## Upgrading to 6.X.X + +The best way to upgrade to 6.X.X is to simply remove the Android platform from +your project and re-add it with the new version. For example, + +```bash +cordova platform remove android +cordova platform add android@6.X.X +``` + +If you use the above method, be aware that any changes you made to the android +platform folder will be lost (editing the contents of this folder is +discouraged). + +Alternatively, you may attempt to use the platform update script. For non-CLI +projects, run: + +`` Review comment: Not enough \` (same 2 lines below) This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277245#comment-16277245 ] ASF GitHub Bot commented on CB-13620: - janpio commented on a change in pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775#discussion_r154739141 ## File path: www/docs/en/dev/guide/platforms/android/upgrade.md ## @@ -27,6 +27,48 @@ Most of these instructions apply to projects created with an older set of command-line tools that precede the `cordova` CLI utility. See [The Command-Line Interface](../../cli/index.html) for information how to update the version of the CLI. + +## Upgrading to 7.X.X + +The best way to upgrade to 5.X.X is to simply remove the Android platform from Review comment: 5.X.X => 7.X.X This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13634) Allow to keep the splashscreen window in onPause on Android
[ https://issues.apache.org/jira/browse/CB-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277171#comment-16277171 ] ASF GitHub Bot commented on CB-13634: - goffioul opened a new pull request #142: CB-13634: (android) Allow to keep the splashscreen windows on pause. URL: https://github.com/apache/cordova-plugin-splashscreen/pull/142 This is a cosmetic change, in case the web app starts another app during load. This prevents transient screens to be visible during app transition animation. ### Platforms affected Android ### What does this PR do? Allow the app to keep the splashscreen window in onPause. The default behavior is backward compatible. ### What testing has been done on this change? ### Checklist - [X] [Reported an issue](http://cordova.apache.org/contribute/issues.html) in the JIRA database - [X] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB- is the JIRA ID & "android" is the platform affected. - [ ] Added automated test coverage as appropriate for this change. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Allow to keep the splashscreen window in onPause on Android > --- > > Key: CB-13634 > URL: https://issues.apache.org/jira/browse/CB-13634 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-splashscreen >Reporter: Michael Goffioul >Priority: Minor > > I have a use case whereby my webapp is launching another app while the > splashscreen is visible, and I want to keep the splashscreen window visible > to prevent unfriendly transient update during the app switching animation on > Android. It would be handy to allow an app to override the default behavior > of removing the splashscreen window in onPause. -- 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-13634) Allow to keep the splashscreen window in onPause on Android
Michael Goffioul created CB-13634: - Summary: Allow to keep the splashscreen window in onPause on Android Key: CB-13634 URL: https://issues.apache.org/jira/browse/CB-13634 Project: Apache Cordova Issue Type: Improvement Components: cordova-plugin-splashscreen Reporter: Michael Goffioul Priority: Minor I have a use case whereby my webapp is launching another app while the splashscreen is visible, and I want to keep the splashscreen window visible to prevent unfriendly transient update during the app switching animation on Android. It would be handy to allow an app to override the default behavior of removing the splashscreen window in onPause. -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277168#comment-16277168 ] Joe Bowser commented on CB-13620: - Sent PR to docs, waiting for merge before announcement. > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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-13620) Cordova-Android Platform Release November 30, 2017
[ https://issues.apache.org/jira/browse/CB-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277167#comment-16277167 ] ASF GitHub Bot commented on CB-13620: - infil00p opened a new pull request #775: CB-13620: 7.0.0 Docs Update. Includes upgrade instructions. URL: https://github.com/apache/cordova-docs/pull/775 ### Platforms affected Android ### What does this PR do? This adds the announcement for the 7.0.0 release ### What testing has been done on this change? ### Checklist - [x] [Reported an issue](http://cordova.apache.org/contribute/issues.html) in the JIRA database - [x] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB- is the JIRA ID & "android" is the platform affected. - [] Added automated test coverage as appropriate for this change. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release November 30, 2017 > -- > > Key: CB-13620 > URL: https://issues.apache.org/jira/browse/CB-13620 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Affects Versions: 7.0.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > -- 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] [Resolved] (CB-13629) Malwarebytes classified Cordova Android as Tro/Clicker.EE
[ https://issues.apache.org/jira/browse/CB-13629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13629. - Resolution: Won't Fix We have no idea why Malware Bytes refers to us as a trojan, but this is obviously a false positive. Closing. > Malwarebytes classified Cordova Android as Tro/Clicker.EE > - > > Key: CB-13629 > URL: https://issues.apache.org/jira/browse/CB-13629 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova@7.0.0 >Reporter: chungyl >Assignee: Joe Bowser >Priority: Blocker > > https://blog.malwarebytes.com/detections/trojan-clicker/ > https://drive.google.com/file/d/13fYyEaUG5rwJZq2kgdyNyec_rL21CIeJ/view?usp=sharing > create clean create app and assembleRelease , the apk will classified as > tor/clicker.ee by malwarebytes. -- 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-13633) Report info/warning events on Android
[ https://issues.apache.org/jira/browse/CB-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277141#comment-16277141 ] ASF GitHub Bot commented on CB-13633: - goffioul opened a new pull request #156: CB-13633: (android) Propagate buffering start/stop events on Android. URL: https://github.com/apache/cordova-plugin-media/pull/156 ### Platforms affected Android ### What does this PR do? Propagate info/warning events (from MediaPlayer.OnInfoListener) to the web application. In particular the buffering start/stop events. ### What testing has been done on this change? ### Checklist - [X] [Reported an issue](http://cordova.apache.org/contribute/issues.html) in the JIRA database - [X] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB- is the JIRA ID & "android" is the platform affected. - [ ] Added automated test coverage as appropriate for this change. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Report info/warning events on Android > - > > Key: CB-13633 > URL: https://issues.apache.org/jira/browse/CB-13633 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-media >Reporter: Michael Goffioul >Priority: Minor > > In order to get notified of buffering events, it is handy to report > info/warning events (MediaPlayer.OnInfoListener) up to the web application. -- 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-13633) Report info/warning events on Android
Michael Goffioul created CB-13633: - Summary: Report info/warning events on Android Key: CB-13633 URL: https://issues.apache.org/jira/browse/CB-13633 Project: Apache Cordova Issue Type: Improvement Components: cordova-plugin-media Reporter: Michael Goffioul Priority: Minor In order to get notified of buffering events, it is handy to report info/warning events (MediaPlayer.OnInfoListener) up to the web application. -- 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-13632) UDP not handled as streaming on Android
[ https://issues.apache.org/jira/browse/CB-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277104#comment-16277104 ] ASF GitHub Bot commented on CB-13632: - goffioul opened a new pull request #155: CB-13632: (android) Allow UDP media streaming. URL: https://github.com/apache/cordova-plugin-media/pull/155 ### Platforms affected Android. ### What does this PR do? Handle UDP media URL as streaming. ### What testing has been done on this change? ### Checklist - [X] [Reported an issue](http://cordova.apache.org/contribute/issues.html) in the JIRA database - [X] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB- is the JIRA ID & "android" is the platform affected. - [ ] Added automated test coverage as appropriate for this change. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > UDP not handled as streaming on Android > --- > > Key: CB-13632 > URL: https://issues.apache.org/jira/browse/CB-13632 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-media >Reporter: Michael Goffioul >Priority: Minor > > When using a UDP multicast URL as media source, it is not handled as a > streaming content by AudioPlayer.isStreaming(). -- 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-13632) UDP not handled as streaming on Android
Michael Goffioul created CB-13632: - Summary: UDP not handled as streaming on Android Key: CB-13632 URL: https://issues.apache.org/jira/browse/CB-13632 Project: Apache Cordova Issue Type: Improvement Components: cordova-plugin-media Reporter: Michael Goffioul Priority: Minor When using a UDP multicast URL as media source, it is not handled as a streaming content by AudioPlayer.isStreaming(). -- 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-13631) Can't read files from cordova.file.applicationDirectory on cordowa-browser platform
Joonas Trussmann created CB-13631: - Summary: Can't read files from cordova.file.applicationDirectory on cordowa-browser platform Key: CB-13631 URL: https://issues.apache.org/jira/browse/CB-13631 Project: Apache Cordova Issue Type: Bug Components: cordova-plugin-file Reporter: Joonas Trussmann I'm attempting to copy files from my cordova.file.applicationDirectory to my cordova.file.dataDirectory on the cordova-browser platform with cordova-plugin-file. resolveLocalFileSystemURL fails (with error code 5) because applicationDirectory is at http://localhost:8000/ URL. The implementation of resolveLocalFileSystemURL in src/browser/FileProxy.js accounts for this by having a rule for lookups from applicationDirectory to be fetched via a GET request. The implementations in www/resolveLocalFileSystemURI.js and www/browser/Preparing.js do not handle this case. In most browsers the second is actually called, in Chrome it's the latter. I've yet to see the first implantation (FileProxy.js) get called. I'd love to fix this myself and submit a PR on github, but I'm having a bit of trouble understanding the reasoning between 3 different implementations, of which the most feature complete is never actually called. -- 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-13502) Android - add support for "setRate" method already available on iOS
[ https://issues.apache.org/jira/browse/CB-13502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276695#comment-16276695 ] ASF GitHub Bot commented on CB-13502: - radicalfitness commented on issue #152: CB-13502: (android) Implementation of setRate method for Android Marshmallow and later URL: https://github.com/apache/cordova-plugin-media/pull/152#issuecomment-348947102 Do you have planned that this happens to the stable version at some point? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Android - add support for "setRate" method already available on iOS > --- > > Key: CB-13502 > URL: https://issues.apache.org/jira/browse/CB-13502 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-plugin-media >Reporter: Julian Hall >Priority: Minor > > The iOS media plugin supports a method "setRate" which changes the playback > rate. Android has support for this feature in the MediaPlayer class used by > the media plugin since API version 23 (Marshmallow), therefore supporting > this method there is very easy. -- 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-13630) "Cannot connect to the camera" issue in android lollipop (android 5.1)
Rajakumar created CB-13630: -- Summary: "Cannot connect to the camera" issue in android lollipop (android 5.1) Key: CB-13630 URL: https://issues.apache.org/jira/browse/CB-13630 Project: Apache Cordova Issue Type: Bug Components: cordova-plugin-camera Affects Versions: 3.0.0 Environment: issue in Android: 5.1 (lollipop), Gradle: 2.14.1, cordova-android: 6.3.0 Reporter: Rajakumar I have created a Cordova application and built an apk using gradle for cordova-android version 6.3.0 which is required for camera plugin. when i testing the apk in device android version > 7 its working fine, but getting "Cannot connect to the camera" alert as error for device android version 5.1 and 6 as well. -- 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
