I feel like we might get 11.2.1 beta or 11.2.2 beta before 11.3.
There will be no public beta of iOS 11.2.1 or iOS 11.2.2 as they will rush out quickly. The current iOS is a ticking time bomb,
I feel like we might get 11.2.1 beta or 11.2.2 beta before 11.3.
Ah two banks... Apple is doomed!
There will be no public beta of iOS 11.2.1 or iOS 11.2.2 as they will rush out quickly. The current iOS is a ticking time bomb,
While more and more banks stop Apple Pay transaction, Apple activates Apple Pay Cash... ok
tvOS seems not to be affected. Interesting.
Furthermore I'm hearing that an iOS 11.2.1 will come this week, alongside macOS 10.13.2 and watchOS 4.2.
I know it from two banks in Canada who temporarily reject Apple Pay transaction...
When someone has a source, do you really think they would name it?Care to name your source? Would love to match it against the Madscotsman's source. I sincerely doubt that we'll see 11.2.1 this week...
There will be no public beta of iOS 11.2.1 or iOS 11.2.2 as they will rush out quickly. The current iOS is a ticking time bomb,
When someone has a source, do you really think they would name it?
He works for a bank and is seeded betas before we are so that they can test them internally for Apple Pay issues.Again, what's your source for this?
Agree there will be no betas for 11.x.y releases... but wondering about their existence (as opposed to betas of 11.3, for example).
[doublepost=1512426106][/doublepost]
Maybe not... but anyone can say anything and claim to have a "source"... I am not looking for a name... but where is this seemingly made up speculation coming from?
Again, what's your source for this?
Agree there will be no betas for 11.x.y releases... but wondering about their existence (as opposed to betas of 11.3, for example).
I can confirm the error message(s) on my Mac running 10.13.1 and iPhone running 11.2. Looks to be related to a few different process. Like others have stated, I wonder what changed in 11.2 which fixed the crashing issue (for now).My sources are colleagues who receive the builds a day early for the implementation of Apple Pay.
And to prove that the date bug has not been fixed:
Just open the console on a mac (with macOS 10.13.1 or below) and you will find several error message like „Month 13 is out of bounds“. Connect your iPhone/iPad to the mac and wait until the error message pops out. Against all news, the date bug was just suppressed.
To be fair, seeing a warning about something doesn't mean that it will actually affect anything as far actual functionality goes. That's not to say that there wouldn't be something to clean up, change, and/or improve, but basically that it by itself (without perhaps more details about it all) doesn't necessarily mean that what's there at this point is necessarily related to that or would actually end up causing actual issues.My sources are colleagues who receive the builds a day early for the implementation of Apple Pay.
And to prove that the date bug has not been fixed:
Just open the console on a mac (with macOS 10.13.1 or below) and you will find several error message like „Month 13 is out of bounds“. Connect your iPhone/iPad to the mac and wait until the error message pops out. Against all news, the date bug was just suppressed.
True, but just Google "month 13 is out of bounds" and you will see countless reports of peoples devices (mainly macOS as most don't plug their iOS device in to check the logs) with this error coming up over and over and over on said devices. This all started on December 1st. Quite the coincidence, but I agree. Correlation does not mean causation.To be fair, seeing a warning about something doesn't mean that it will actually affect anything as far actual functionality goes. That's not to say that there wouldn't be something to clean up, change, and/or improve, but basically that it by itself (without perhaps more details about it all) doesn't necessarily mean that what's there at this point is necessarily related to that or would actually end up causing actual issues.
To be fair, seeing a warning about something doesn't mean that it will actually affect anything as far actual functionality goes. That's not to say that there wouldn't be something to clean up, change, and/or improve, but basically that it by itself (without perhaps more details about it all) doesn't necessarily mean that what's there at this point is necessarily related to that or would actually end up causing actual issues.
I got the error with Calendar, Mail, Reminders, News, and Photos though I didn't test on all of my apps so I'm sure there are others.This is not „just“ a warning. This is an core bug which affects the complete functionality of the device and its features. This time it was notifications which starts the problem. It appears that especially apps stock apps are affected.
Just open the console on a mac (with macOS 10.13.1 or below) and you will find several error message like „Month 13 is out of bounds“. Connect your iPhone/iPad to the mac and wait until the error message pops out. Against all news, the date bug was just suppressed.
Seeing it all over the place and all seem to be a CoreFoundation process. Even happening with my IMDb app with a process simply called IMDb. Definite iOS related and not an app problem.Confirming that in my logs too. Incredibly enough, I'm seeing Outlook throw the same error on the Mac too.
Seeing it all over the place and all seem to be a CoreFoundation process. Even happening with my IMDb app with a process simply called IMDb. Definite iOS related and not an app problem.
They have their own propriety calendar system internally and are working on licensing third parties to use it once all the bugs are worked out. Also, they will be including an "Apple Calendar Converter" dongle with all 2018 devices.Yep, I had just updated my post too. What is it with Apple and dates? They have "incidents" with them seemingly at least once a year.
They have their own propriety calendar system internally and are working on licensing third parties to use it once all the bugs are worked out. Also, they will be including an "Apple Calendar Converter" dongle with all 2018 devices.
My sources are colleagues who receive the builds a day early for the implementation of Apple Pay.
And to prove that the date bug has not been fixed:
Just open the console on a mac (with macOS 10.13.1 or below) and you will find several error message like „Month 13 is out of bounds“. Connect your iPhone/iPad to the mac and wait until the error message pops out. Against all news, the date bug was just suppressed.
I would bet todayI know this is not the right place but can we expect watchOS 4.2 this week?