Apple Shares Fix for File Sharing Issues Following macOS High Sierra Security Update

[MacsRuleOthersDrool]

Human error occurs, I get that... but this definitely isn't a good look lol.

Wrong.

What wouldn't be a "good look" would be to do what MS does:

1. Deny the error for two weeks.
2. Blame the User for another two weeks.
3. Issue a patch.
4. Deny the error that the patch creates for a month.
5. Blame the User for the error that the patch creates for another month.
6. Quietly issue a patch at their next regularly-scheduled Patch Tuesday.

Time for Apple to admit, apologize, and fix the original error: < 24 hours.

Time for Apple to fix the patch: < 12 hours.

Get over it.
[doublepost=1512037774][/doublepost]

Apple fixes one thing and breaks another.
Time for a rebranding ? (Cr)Apple ?

As I said above, I write software for a living, and I have a longstanding phrase:

"Fix a bug, make a bug".

Happens.
[doublepost=1512037833][/doublepost]

They will add a new tab to their website where people will have to go and find the code they need and copy paste it into the terminal app.

Give it a rest.
[doublepost=1512037911][/doublepost]

High Sierra and IOS 11 have been absolute crap, do they even bother checking things before the push them.

Both High Sierra and iOS 11 had Public Betas for months.

So WHO didn't bother to check things?

 

[qawes]

I don't get the whining from various forum colleagues, and also the exaggeration.

Bugs happen, with this new OS version we are witnessing an upgrade to a 30+ years old filesystem. Situations like this were bound to be expected, that's why it will take some time for this version to be truly usable on a day to day basis.

Your Mac is not an iPhone, and upgrading your main machine to the latest version of OS X in a .1 release is just reckless, to put it in good words.

Just my two cents.

 

[MacsRuleOthersDrool]

I wonder when the tipping point for Tim will be that Apple has serious and deep problems in its software function. Because clearly the lack of innovation hasn’t caught his attention. Maybe the shoddy quality will.

Time will tell...

Boy, the instantaneous and contrite statement issued yesterday sure sounds like the root authentication bug has caught Apple's attention...

I can only IMAGINE the meetings...

 

[M2M]

Wrong.

What wouldn't be a "good look" would be to do what MS does:

1. Deny the error for two weeks.
2. Blame the User for another two weeks.
3. Issue a patch.
4. Deny the error that the patch creates for a month.
5. Blame the User for the error that the patch creates for another month.
6. Quietly issue a patch at their next regularly-scheduled Patch Tuesday.

Time for Apple to admit, apologize, and fix the original error: < 24 hours.

Time for Apple to fix the patch: < 12 hours.

Get over it.
[doublepost=1512037774][/doublepost]
As I said above, I write software for a living, and I have a longstanding phrase:

"Fix a bug, make a bug".

Happens.
[doublepost=1512037833][/doublepost]
Give it a rest.
[doublepost=1512037911][/doublepost]
Both High Sierra and iOS 11 had Public Betas for months.

So WHO didn't bother to check things?

Bug has been discussed in the Apple dev forums for 2 weeks. So it’s 2 weeks + 24h.

Don’t think fix a bug, make a bug is a good approach. Especially for a big company like Apple which should have a big QA team.

 

[MacsRuleOthersDrool]

True, bugs will always be present regardless of which platform people choose.

But it is undeniable that Apple products no longer “just work”

And asking people to tinker in the terminal app.... really Apple, really?!

Would you rather that they took an extra week to develop and test a GUI solution for a two-second fix?
[doublepost=1512038338][/doublepost]

The Mac file sharing has always been a mess. Not that it's any better in Windows, but still. There are so many bugs that never got fixed.

...Not that it is any better in Windows...

Indeed!
[doublepost=1512038545][/doublepost]

Bug has been discussed in the Apple dev forums for 2 weeks. So it’s 2 weeks + 24h.

Don’t think fix a bug, make a bug is a good approach. Especially for a big company like Apple which should have a big QA team.

It's not an "approach"; it's a FACT.

And the "QA Team" doesn't get a chance to sign-off in an emergency situation like this.
[doublepost=1512038788][/doublepost]

The average consumer shouldn’t have to mess around in the terminal... that’s just bad customer experience.

It should’ve been released as a security update.

That way everybody would get it. I’d like to believe that they have someone who could write the script that would automate the fix.

Um, it was.

But then, BECAUSE OF THE INSTANTANEOUS RELEASE, there was an UNINTENDED CONSEQUENCE.

But, nobody lost any data.

The fix for the fix was pretty simple.

And Apple released that fix in < 12 hours.

You OBVIOUSLY have never written a byte of code in your life. I make my living doing just that.
[doublepost=1512038919][/doublepost]

Things like this really makes me wonder why I'm still using this operating system, and why Apple is even keeping it alive in this condition.

Then go to Windows or Linux for some REAL "Customer Support".

We'll wait...
[doublepost=1512039032][/doublepost]

The worst operating system in history

Compared to what, exactly?
[doublepost=1512039444][/doublepost]

They really just need to pull the update overnight and figure out the File Sharing issue. I, as the end user, shouldn't have then run a line of code (even if its a single line) to fix something that wasn't even suppose to be effected by said bug and subsequent fix.

Who says they won't?
[doublepost=1512039742][/doublepost]

So great now I can't even access my shared drives through SMB or AFP. All Apple products here. This update just killed File sharing. So now what Apple?

What now?

Apply the simple fix and be happy.

https://support.apple.com/en-us/HT208317

 

[FX120]

You're obviously crazy, Cook's only made Apple the most valuable brand in the world, made iPhone the most popular phone in the world, made Apple Watch (and smartwatches in general) ubiquitous, and made investors wildly wealthy! He's clearly terrible for the company, and must go now!/s

Steve Ballmer also took Microsoft to the peak of market domination, financially Microsoft did exceedingly well and made tons of money during the early years of his tenure. And look what happened to Microsoft after years of small missteps and stalled innovation.

 

[MacsRuleOthersDrool]

The 'solution' requires using the Terminal.app GUI. That requires you to type obscure, cryptic commands that nobody understands. What the heck is Apple playing at? This is a total disaster.

Nope. Just apply the Security Update 2017-001 AGAIN, and it includes the File Sharing Fix.

Done.
[doublepost=1512040174][/doublepost]

I agree.., Apple should be pushing out an update, not asking users to fix this via Terminal.

They did.

Just apply it again, (or now), and it will have both fixes in it.
[doublepost=1512040256][/doublepost]

Ummm why is App Store asking me to update again? "Security Update 2017-001" Looks like the same thing to me.

It isn't.
[doublepost=1512040507][/doublepost]

Quality control at Apple had gone down the hill. They need to take Mac business seriously.

They do.

Thats why there was a fix out in < 24 hours, and another patch in < 12 hours after that, which has already been rolled-up into the original Security Update fix.

 

[SOLLERBOY]

I patched to 17B1002 yesterday, just woke my iMac up and a notification came up saying another security patch was installed. Just checked and am now on 17B1003.

Seems like they pushed another one out?

 

[Rogifan]

That iPhone battery case is still the most incredible design I've ever seen. It's ugly, awkward and so cheap looking.

No effort to make it beautiful, just a case with a battery glued to the back.

But I thought Apple was all about form over function?

 

[Habakuk]

SECOND Security Update!

Apple published another update some minutes ago.

My advice: Restart your machine after the update! Check the build number in "About this Mac" (click on 10.13.1). Is it 17B1003 (after the second update)? If not: Start your machine new. You'll encounter a "Setting up your Mac" routine when it starts (pretty unusual for a "normal" restart).

Here—MacBook Pro (15-inch, Late 2016)—it was 17B48! Only after the restart it was 17B1003!! I hope Apple didn't forget that after the update a restart is obligatory! After both updates a restart was not required by default. (Or it's just the build number which is flawed. Confused.)

Btw when you installed the first security update only the build number should be 17B1002.

Attachment (screenshot): Both updates in the "recent updates" list in Mac App Store (German-language).

Edit: A buddy told me that it isn't necessary to restart the machine for being able to see the most recent build number. BUT you have to close and open again the "About this Mac" window. I can't verify this right now. Please restart your machine anyway.

 

[LarryJoe33]

Any news on a patch for us beta testers? I feel naked😉

 

[chatin]

High Sierra is a mess. I know several users who have had their desktops wrecked by this upgrade.

 

[BaltimoreMediaBlog]

After I updated mine I rebooted anyways. And up came the diagnostic menu that asks if I want to submit to Apple. Then came up the “setting up your Mac” screen..I cringed for a sec lol

But all seems well she finally got out of booting.

I'm not an expert, but this constant re-setting up your Mac thing after updates seems to be what is scrambling all the MAIL server settings and breaking the MAIL program. Don't they even test the installation?

I am so tired of having to select the correct server to use every update to simply respond to an f'ing email from the family! This is epic fail Apple. No update should break so many simple things. UGH! 🙁
[doublepost=1512046196][/doublepost]

High Sierra is a mess. I know several users who have had their desktops wrecked by this upgrade.

Mine is one of them. Somehow it dismantled a completely fine working HD which I tested repeatedly after noticing problems and all test showed nothing wrong with the drive, one of my newest. It started with permissions issues, then it got worse, until High Sierra just started ignoring the drive completely! :-(

 

[robk64]

I seriously hope the audit of Apple's development practices proves enlightening, because this is just sad.

Speaking of enlightening, has anyone else noticed the dock background just got a little lighter and more opaque after the security update? It became so noticeable, I had to try out the dark dock option.

 

[gnasher729]

Apple fixes one thing and breaks another.
Time for a rebranding ? (Cr)Apple ?

Apple fixes one thing that was absolutely 100% required to be fixed as soon as possible. There's a hole in the ship and you have to plug the hole, no matter what. That fix had to get out, without waiting for testing. Sorry if that's something you can't understand.

So it broke something, a bit unfortunate but not unexpected, but now it gets fixed. Meanwhile the Macs that were affected were not vulnerable anymore.

 

[hipnetic]

I'm encountering a different issue - anyone else seeing this?...

I'm not sure if it's related to the security patch, or the previous OS update. I had the last OS update that I had been pushing off and kicked that off this morning, followed immediately by this security patch. So I've got a rather large text file that I store all of my passwords in. I noticed recently that when I open it, and start to scroll down that the scrollbar is only sized for the first xx number of lines, like it's only cached that number of lines into memory. When I get to the bottom of that section, it then pulls more lines into memory and the scrollbar adjusts. This seemed to be new behavior with High Sierra, but I can't say for certain.

Anyway, as of this morning, I open this text file and even after scrolling to the bottom of the initially-cached number of lines, it doesn't pull in any more lines. So I'm just stuck at the bottom of the list. My first thought was that the text file got corrupted or I fell asleep last night with the file open and accidentally deleted most of my file. But then I closed the file and reopened it, and now I have another chunk of lines available. But I still didn't have the whole file, and scrolling to the bottom didn't re-cache any more of it. Again, closing the file and reopening it, I see more lines.

Anyone else experiencing this?

Edit: Re-opening it again and it was cut off shorter than the last time. Ugh. But then I maximized my window and I saw the entirety of my text file available to scroll through. So it looks like maybe this bug is actually more of a bug with viewing large text files in small TextEdit windows.

 

[Bacillus]

I wonder when the tipping point for Tim will be that Apple has serious and deep problems in its software function. Because clearly the lack of innovation hasn’t caught his attention. Maybe the shoddy quality will.
Time will tell...

Of course, this all caught his attention. That's why the pipeline was invented.
It will be just as long as human memory allows

Ah yes, because Tim is sitting in a cubicle personally writing and maintaining code.

And now probably referring to the promised PostPC land "as I said, iPad users will never have these bugs"

 

[gatearray]

Without the iPhone the current Apple is nothing.

Truer words have rarely been spoken.

 

[chrfr]

Here—MacBook Pro (15-inch, Late 2016)—it was (17B48)! Only after the restart it was 17B1003. I hope Apple didn't forget that after the update a restart is obligatory!

If you had simply closed and reopened the "About this Mac" window without rebooting, you'd have seen the change in build number. A restart is not required.

 

[NaOH]

Speaking of enlightening, has anyone else noticed the dock background just got a little lighter and more opaque after the security update? It became so noticeable, I had to try out the dark dock option.

That’s something I’ve seen too.
It’s actually one of the Accessibility settings that has been turned on.
(Reduce transparency)

 

[TroyBoy30]

and you guys say they aint doomed lol

 

[Xavier]

Time for Cook to resign. His tenure has been a disaster.

Actually, quite the opposite.

On a different note, what is this fix going to break?

 

[dogslobber]

This is the nature of all modern software. It’s not an easy task, and will likely only get worse.

If they assigned a QA resource who did some random input testing to the UI (fuzz testing) then the s would fail. It’s not hard and not anything new. It’s elementary stuff.

But of more concern is thT this is the known exposure but where else has Apple fcked up that hasn’t yet been exposed?

Perhaps Cook should be asking security experts like Microsoft how to do security testing nowadays.

 

[fairuz]

Exactly. There is an accumulation of small things that just make the OS unpolished.

There were bugs in the past, but now they seem to be more common and, for some weird reason, accepted as normal.

I would like to see them switch from yearly releases of a new OS to a two year cycle. Maybe this way they can get back some of the polish they have lost.

Two year cycle was great. Now it's just too much. I like how Ubuntu for example has the "long term support" releases. 4 or so years of not worrying.

 

[Jim L]

That's great stuff Tim.

Yeah, you really care about the Mac. .... right

It. Just. Works. .... right 🙄