Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS 11.x.x Release Speculation Thread

Status
Not open for further replies.
B

Broken Hope

macrumors 68000
Jan 15, 2015
1,823
1,880
sunny2k1 said:
Back to Apple:

I’m hearing that the “Month 13” issue is not that easy to fix, as it looks like it is an issue within SWIFT 4. It’s interesting for that point of view, as only apps already transferred (such as calendar, calculator) creates such log files. In macOS 10.13.3 they obliviously moved back to the previous SWIFT 3.
Click to expand...

Doesn't look like it would be hard to fix at all

https://twitter.com/timacfr/status/938155405460623360

Seems to be a fairly simple error.

No idea why they are taking so long to fix it.
 
P

Paddle1

macrumors 603
May 1, 2013
5,151
3,604
sunny2k1 said:
Just to clarify: next Wednesday to next Friday (30th) are normal work days (even though the main part of the business is on vacation in Germany). This does not mean that important projects are totally off, there are lot of people on stand by in case of “emergencies”.

Back to Apple:

I’m hearing that the “Month 13” issue is not that easy to fix, as it looks like it is an issue within SWIFT 4. It’s interesting for that point of view, as only apps already transferred (such as calendar, calculator) creates such log files. In macOS 10.13.3 they obliviously moved back to the previous SWIFT 3.
Click to expand...
I was wondering this, it could be a deeper issue that'll take time to fix, hence 11.2.5?
 
C

C DM

macrumors Sandy Bridge
Oct 17, 2011
51,392
19,461
Paddle1 said:
Last time it was triggered, the device repeatedly crashes after a few minutes of use.
Click to expand...
Was that really what was causing that, or is this something else (perhaps related or perhaps not)? And if it's not an issue as of iOS 11.2 what would make it an issue at some point?
 
Last edited:
P

Paddle1

macrumors 603
May 1, 2013
5,151
3,604
C DM said:
Was that really what was causing that, or is this something else (perhaps related or perhaps not)? And if it's not an issue as of iOS 11.2.1 what would make it an issue at some point?
Click to expand...
The respringing was attached to the date and according logs they appear to be connected.
But that's what I'm wondering. If this is the case, what did 11.2 do to temporarily fix this issue? Will it come up again at the end of the month?
digitalexplr said:
I know that has been the issue on High Sierra, but if that were the case with iOS would not all iOS users be experiencing the same problem? Admitted ignorance to the problem.
Click to expand...
The problem only appeared if you had certain apps on iOS sending preprogrammed time based notifications.
 
S

sunny2k1

macrumors 6502
Nov 9, 2013
420
396
Toronto, Ontario, Canada
The resprings were caused by the Month 13 issue. That’s proven. It not only impacted the resprings. Also other core features (e.g. ApplePay) are affected. iOS 11.2 was just a placebo, which really didn’t fix the problem at all. As for macOS it had a dramatic impact to the performance on some macs.
 
sbailey4

sbailey4

macrumors 601
Dec 5, 2011
4,571
3,253
USA
sunny2k1 said:
The resprings were caused by the Month 13 issue. That’s proven. It not only impacted the resprings. Also other core features (e.g. ApplePay) are affected. iOS 11.2 was just a placebo, which really didn’t fix the problem at all. As for macOS it had a dramatic impact to the performance on some macs.
Click to expand...
Then why exactly was 11.2 emergency released on a Saturday am at 12:00 AM if not to be anything but a placebo? It makes no since that it did nothing to resolve that issue on Dec 2nd and they just released it in the middle of the night on a Saturday just for the heck of it. And in fact the folks who had an issue on Dec 2nd got resolution with 11.2 yes? Not being argumentative just curious how you arrive at your conclusions.
 
C

C DM

macrumors Sandy Bridge
Oct 17, 2011
51,392
19,461
sunny2k1 said:
The resprings were caused by the Month 13 issue. That’s proven. It not only impacted the resprings. Also other core features (e.g. ApplePay) are affected. iOS 11.2 was just a placebo, which really didn’t fix the problem at all. As for macOS it had a dramatic impact to the performance on some macs.
Click to expand...
But what changed in 11.2 that got the resprings to stop (even though the warning/error is still there)?
 
Last edited:
  • Like
Reactions: sbailey4
S

sunny2k1

macrumors 6502
Nov 9, 2013
420
396
Toronto, Ontario, Canada
sbailey4 said:
Then why exactly was 11.2 emergency released on a Saturday am at 12:00 AM if not to be anything but a placebo? It makes no since that it did nothing to resolve that issue on Dec 2nd and they just released it in the middle of the night on a Saturday just for the heck of it. And in fact the folks who had an issue on Dec 2nd got resolution with 11.2 yes? Not being argumentative just curious how you arrive at your conclusions.
Click to expand...

C DM said:
But what changed in 11.2 that got the restrings to stop (even though the warning/error is still there)?
Click to expand...

My assumption is that the multiple reboots of the phone during the OTA process caused to sort things out. The resprings are technically no reboots.

Radon87000 said:
When I connected to iMazing console on Windows I got the Month 13 out of bounds.
Click to expand...

That would support the theory, that something is wrong with coding language.
 
P

Paddle1

macrumors 603
May 1, 2013
5,151
3,604
sunny2k1 said:
My assumption is that the multiple reboots of the phone during the OTA process caused to sort things out. The resprings are technically no reboots.



That would support the theory, that something is wrong with coding language.
Click to expand...
If rebooting fixed the issue then that shouldn't have required an update. 11.2 has to have something in it that stopped the respringing directly seeing as 11.2 beta users didn't experience the problem.
 
  • Like
Reactions: sbailey4
S

sunny2k1

macrumors 6502
Nov 9, 2013
420
396
Toronto, Ontario, Canada
Paddle1 said:
If rebooting fixed the issue then that shouldn't have required an update. 11.2 has to have something in it that stopped the respringing directly seeing as 11.2 beta users didn't experience the problem.
Click to expand...

The issue was caused by a specific configuration with local (non-icloud) notifications with customised repeat intervals. It does not matter which iOS version was on the device. I was on the beta version with my iPod touch and I had the issue (even with the latest then final beta).

iOS 11.2 final was just the placebo to solve the issue.
 
Chazzle

Chazzle

macrumors 68020
Jul 17, 2015
2,043
2,154
sunny2k1 said:
The issue was caused by a specific configuration with local (non-icloud) notifications with customised repeat intervals. It does not matter which iOS version was on the device. I was on the beta version with my iPod touch and I had the issue (even with the latest then final beta).

iOS 11.2 final was just the placebo to solve the issue.
Click to expand...
So how did you fix the issue on your iPod Touch?
 
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom