Cordova App crashes in iOS 12.4
I am an engineer from WalletHub, a Cordova app that is also one of the highest-rated personal finance apps on the U.S. App Store ( https://apps.apple.com/us/app/wallethub/id1110552982). We've been noticing a problem happening with our app lately on iPads in iOS 12.4 to which I've submitted an issue here: https://github.com/apache/cordova-ios/issues/665 . This came after we just released a new build updating to the latest platform and plugins, although I can see the issue coming on the older build as well but at a much lower rate. We were wondering if you could help us get to the bottom of it. The crash rate on the iPad is really high and so this is very urgent for us. Any help you can provide would be much appreciated!
Nightly build #1166 for cordova has succeeded!
Nightly build #1166 for cordova has succeeded! The latest nightly has been published and you can try it out with 'npm i -g cordova@nightly' For details check build console at https://builds.apache.org/job/cordova-nightly/1166/consoleFull - Jenkins for Apache Cordova - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Node 6.x & 8.x Deprecation & Node 12.x Support
For example, I think migration of packages such as cordova-android to fs-extra should only target Node.js 10(+) https://github.com/apache/cordova-android/issues/781 fs-extra supports >= Node 8, so I don't think not deprecating/dropping node8 will be a blocker here. There is an issue with the language in the blog post. Deprecation means that support will be removed in the future, we should deprecate now, and remove support somewhere down the road. - Jesse 100% agree with this. Makes sense to add the deprecation notices now, so that support can be removed in the following major release. On 2019-09-09 12:36 p.m., Chris Brody wrote: Here is my response to what looks like the original discussion on Node.js versions 6 and 8: Considering that the Apache Cordova maintainers do not even have enough time resources to keep up with bugs and features on the current platform stack versions, I find it ridiculous that we should even consider maintaining support for old tool versions such as Node.js 8. For example, I think migration of packages such as cordova-android to fs-extra should only target Node.js 10(+) https://github.com/apache/cordova-android/issues/781 On Thu, Apr 11, 2019 at 12:42 AM Jesse wrote: There is an issue with the language in the blog post. Deprecation means that support will be removed in the future, we should deprecate now, and remove support somewhere down the road. The sooner the better for Node 6.x imho On Wed, Apr 10, 2019 at 8:17 PM Gedas Gardauskas < gedas.gardaus...@gmail.com> wrote: +1 I believe it is a good idea to hold out until December. Keeping in fact that there is little time to take action right now (except informing the user) and that we have released Cordova 9.0 not so long ago. Plus, the fact that the Android and iOS new versions are coming later this year. As Bryan said, I think, everything would line up nicely for the Cordova 10 release in December. On April 10, 2019 at 16:42:45, Bryan Ellis (er...@apache.org) wrote: I would like to start the discussion around Cordova's planning for deprecating Node 6.x and Node 8.x as well as starting to support Node 12.x. Since Node 6.x is being deprecated by the end of this month, I am not expecting drastic action. Additionally, Node 8.x is expected to be deprecated by December. IMO, we could hold out till December to deprecate both versions and just warn users about our recommendation to upgrade in the meantime. These notices and warnings can be added in April and September as a patch or minor release. As a side note, I suspect Android Q's release (August?) and possible iOS (Sept?) to be out before December. For a major release for these new platforms, adding Node will fall in nicely. Blog Post PR: https://github.com/apache/cordova-docs/pull/965 GH Issue Ticket: https://github.com/apache/cordova/issues/79 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Node 6.x & 8.x Deprecation & Node 12.x Support
Here is my response to what looks like the original discussion on Node.js versions 6 and 8: Considering that the Apache Cordova maintainers do not even have enough time resources to keep up with bugs and features on the current platform stack versions, I find it ridiculous that we should even consider maintaining support for old tool versions such as Node.js 8. For example, I think migration of packages such as cordova-android to fs-extra should only target Node.js 10(+) https://github.com/apache/cordova-android/issues/781 On Thu, Apr 11, 2019 at 12:42 AM Jesse wrote: > There is an issue with the language in the blog post. > Deprecation means that support will be removed in the future, we should > deprecate now, and remove support somewhere down the road. The sooner the > better for Node 6.x imho > > > On Wed, Apr 10, 2019 at 8:17 PM Gedas Gardauskas < > gedas.gardaus...@gmail.com> > wrote: > > > +1 > > > > I believe it is a good idea to hold out until December. Keeping in fact > > that there is little time to take action right now (except informing the > > user) and that we have released Cordova 9.0 not so long ago. Plus, the > fact > > that the Android and iOS new versions are coming later this year. As > Bryan > > said, I think, everything would line up nicely for the Cordova 10 release > > in December. > > > > > > > > On April 10, 2019 at 16:42:45, Bryan Ellis (er...@apache.org) wrote: > > > > I would like to start the discussion around Cordova's planning for > > deprecating Node 6.x and Node 8.x as well as starting to support Node > 12.x. > > > > Since Node 6.x is being deprecated by the end of this month, I am not > > expecting drastic action. > > > > Additionally, Node 8.x is expected to be deprecated by December. > > > > IMO, we could hold out till December to deprecate both versions and just > > warn users about our recommendation to upgrade in the meantime. These > > notices and warnings can be added in April and September as a patch or > > minor release. > > > > As a side note, I suspect Android Q's release (August?) and possible iOS > > (Sept?) to be out before December. For a major release for these new > > platforms, adding Node will fall in nicely. > > > > Blog Post PR: https://github.com/apache/cordova-docs/pull/965 > > GH Issue Ticket: https://github.com/apache/cordova/issues/79 > > >
Re: [DISCUSS] Dropping support for Node 8
My apologies, I did do a search to see if there was a discussion in the mailing list but found nothing. I only realized that the search by default only looks back 1 month. I'll forward the rejection then to the ticket that prompted me to start this discussion. To expire this discussion thread, I'll link back to the original thread https://lists.apache.org/thread.html/de3f47975bfe2a41f0e0145829ec1058225a0fe789fb862859026389@%3Cdev.cordova.apache.org%3E On 2019-09-09 12:01 p.m., julio cesar sanchez wrote: This was discussed already and I think everybody agreed to drop it. Some people agreed, but said we should wait until December. I've checked telemetry and node 8 is ~18% of users, but going down. El lun., 9 sept. 2019 a las 16:38, Darryl Pogue () escribió: +1 from me On Mon, Sep 9, 2019 at 7:20 AM Norman Breau wrote: Just starting a thread here to whether or not we should drop support for Node 8 at the same time of dropping Node 6 support. The original thought for this I believe is to avoid having to have 2 major version bumps as Node 8 EOL is in December 2019, only a few months away. Personally I don't see why we should keep support something that is in maintenance mode and is coming to the end of life soon, so I think dropping Node 8 is a good idea. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Dropping support for Node 8
This was discussed already and I think everybody agreed to drop it. Some people agreed, but said we should wait until December. I've checked telemetry and node 8 is ~18% of users, but going down. El lun., 9 sept. 2019 a las 16:38, Darryl Pogue () escribió: > +1 from me > > > On Mon, Sep 9, 2019 at 7:20 AM Norman Breau > wrote: > > > > Just starting a thread here to whether or not we should drop support for > > Node 8 at the same time of dropping Node 6 support. > > The original thought for this I believe is to avoid having to have 2 > > major version bumps as Node 8 EOL is in December 2019, only a few months > > away. > > > > Personally I don't see why we should keep support something that is in > > maintenance mode and is coming to the end of life soon, so I think > > dropping Node 8 is a good idea. > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: [DISCUSS] Dropping support for Node 8
+1 from me On Mon, Sep 9, 2019 at 7:20 AM Norman Breau wrote: > > Just starting a thread here to whether or not we should drop support for > Node 8 at the same time of dropping Node 6 support. > The original thought for this I believe is to avoid having to have 2 > major version bumps as Node 8 EOL is in December 2019, only a few months > away. > > Personally I don't see why we should keep support something that is in > maintenance mode and is coming to the end of life soon, so I think > dropping Node 8 is a good idea. > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Dropping support for Node 8
+1 for dropping Node.js 8 at the same time I would say we should not spend our limited resources on supporting old versions of Node.js or other tooling. On Mon, Sep 9, 2019 at 10:20 AM Norman Breau wrote: > Just starting a thread here to whether or not we should drop support for > Node 8 at the same time of dropping Node 6 support. > The original thought for this I believe is to avoid having to have 2 > major version bumps as Node 8 EOL is in December 2019, only a few months > away. > > Personally I don't see why we should keep support something that is in > maintenance mode and is coming to the end of life soon, so I think > dropping Node 8 is a good idea. > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
[DISCUSS] Dropping support for Node 8
Just starting a thread here to whether or not we should drop support for Node 8 at the same time of dropping Node 6 support. The original thought for this I believe is to avoid having to have 2 major version bumps as Node 8 EOL is in December 2019, only a few months away. Personally I don't see why we should keep support something that is in maintenance mode and is coming to the end of life soon, so I think dropping Node 8 is a good idea. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
