Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
Not open for further replies.
jhall8, what do you want to say with this link?

„Apple started working on iOS 12 before iOS 11 was even announced.“

Source?
 
No, thats just theory, believe me.

And it still doesnt explain why Apple shuts down the company when they have so much issues left to fix.
 
No, thats just theory, believe me.

And it still doesnt explain why Apple shuts down the company when they have so much issues left to fix.
Theory? Craftsmen who work at our home right know will not work on holidays. There is one serious bug. They will fix it, this week, at least I hope so.

Some people work. Sure and normal.
 
“Holiday” simply means vacation in many parts of the world. It seems many of you are confusing it with a holiday like Christmas.
 
the only way i see them not releasing 11.2.2 today or tomorrow is if this bug for 13 month does nothing on january 1st.
 
So back in our current pre-holiday time: Anyone think that 11.2.2 will be released today?
I sorta think it will. Or at least something. But again it depends on how serious that Month 13 bug really is. Could be the patch that was introduced in 11.2 is enough to keep it from totally blowing up on 1/1.
 
  • Like
Reactions: jhall8
Yes and no, a friend of mine she works way more than what is allowed.
I’ve been part of various class cation lawsuits in the US for former employees violating working laws.

So it’s definitely a world wide issue. But the law is still the law. Employers just find loopholes.
 
Last edited:
nothing again...

my guess there is nothing to worry about for the month 13 bug.

iOS 11.2.5 sometime in january followed by iOS 13 after?
 
Last edited:
I’ve been part of various class cation lawsuits in the US for former employees violating working laws.

So it’s definitely a world wide issue. But the law is still the law. Employers just find loopholes.

Freudian slip there!
 
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.
 
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.
I was wondering if his had anything to do with the move from Objective C. Very curious to see how this will play out. Glad I have advised my fam and friends to stay on iOS 10, still.
 
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.