After many of complaints about Wi-Fi issues, Apple dumps discoveryd in latest OS X beta

“After many complaints from the developer community about poor networking performance on Yosemite, the latest beta of OS X 10.10.4 has dropped discoveryd in favor of the old process used by previous versions of the Mac operating system,” Benjamin Mayo reports for 9to5Mac.

“This should address many of the network stability issues introduced with Yosemite and its new networking stack,” May reports. “The discoveryd process has been subject to much criticism in recent months as it causes users to regularly drop WiFi access and causes network shares to list many times over, due to bugs.”

“discoveryd would cause random crashes, duplicate names on the network and many other WiFi-relate bugs,” May explains. “In the latest beta, Apple appears to have applied the same fix as the enthusiasts by axing discoveryd completely.”

Read more in the full article here.

MacDailyNews Take: Mac users, our long worldwide nightmare is over!

Thanks for listening, Apple!

Related articles:
OS X Yosemite networking issues and ‘discoveryd’ – May 7, 2015
Open letter to Tim Cook: Apple needs to do better – January 5, 2015

28 Comments

  1. Still no fix for the IMAP fail? Cook and Federighi promised it a year ago. Hosing sys admins and enterprise clients with unreliable service for two years now.

    1. There are two people on this board who keep repeating this, although I have yet to find any evidence that it is true. Other than these two, nobody else anywhere seems to be experiencing any “sys admin hosing” or any other significant issues with IAMP on Yosemite.

      Goebbels has been attributed as saying that if you say a lie often enough, others will come to believe it to be true. Now, I don’t want to claim that these two are lying, but I simply cannot find any evidence that supports their claims. Therefore…

        1. @ silverhawk: you use that label with everyone. Clearly you haven’t done your homework at all. Thousands of Mac users have been screwed over by Apple’s flaky IMAP changes starting with Mavericks and continuing to the present day. It affects not only Gmail but also other mail services.

          – once upon a time, Apple Mail allowed you to download full messages w/attachments, message text only, read messages, or new messages. now those options are gone.

          – Mavericks introduced a bug where email was duplicated endlessly, overloading the Junk folder for most affected people

          – Smart folders were broken in Mavericks for many users such that badges reported incorrect number of unread messages, rules didn’t work properly or consistently, etc. Totally unacceptable schitzo behavior.

          – sidebar arrangement is broken

          – Applescript and 3rd party plugins were broken in Mail without warning

          Bottom line, silverhawk: just because your Mail needs are so simple that you don’t have any problems doesn’t mean that Apple didn’t royally screw up these last few years. Mac users have devoted lots of time to cobble together workarounds or just abandon Mail for better programs. Perhaps Apple is just actively shitting on Gmail users, but in doing so they have screwed other pop3 and IMAP mail service users as well.

          This is not the quality we expect from Apple, nor is it an indication that Mark or anyone else with these well-reported problems are “trolls” as you naively or maliciously claim. Would you please get the facts before continuing your annoying personal attacks on public forums?

      1. Do MacBooks still spontaneously explode if you use them in sunlight?

        Did they ever fix the triple-click on Macintosh HD which causes the home folder to be deleted?

        Did the lawsuit over Stickies.app causing cancer ever settle?

        Make a lie, repeat a lie, lie until it becomes “true”. Be afraid of truths.

      2. No evidence that this is true?? Then why did Federighi stand on stage in front of Cook and promise to make IMAP work “the way it should” when he previewed Yosemite six months prior to launch? By then it had been unreliable for 8 months in 10.9.

    2. Mail has been a mess for me since Yosemite. I had to stop using it completely. Using Postbox now. Periodically, I check Mail to see if it’s under control again. So far, no luck. Mail freezes and sometimes just quits regularly. Sorry others are not experiencing problems. If more were, I suspect Apple would have fixed it by now.

      1. Mail has been problematic since Mavericks. Finally addressed the last of my bugs with 10.10.3 but it sounds like there are still issues for others. I wouldn’t be surprised if dns/discoveryd were the root of a lot of stability issues.

  2. Everything I have, works fine on my Airport Extreme. Except, my MacBook Pros. I have to switch over to my old router to get simple things on the web. It’s as if sections of the web stop working while others continue to work fine. The worst experience ever. I hope this is the end of the bad dream.

  3. Good news! Still, it’s not like Mavericks was the most stable thing either. Airport is rock solid but Macs with Mavericks drop out occasionally, Airdrop is a random event, and Airplay can be extremely frustrating. Apple needs to make WiFi stable and easy to manage again, not just return to where they left off in late 2013.

      1. Simple explanation: They wanted their discoveryd code to work and tried valiantly to fix it to no avail so while they might continue in-house to get it to work, they’ll resort to reverting back to the already proven more stable solution.

  4. Are they also going to toss pacemaker in the scrap heap and go back to letting ntpd actually keep the system clock synced with the ACTUAL time? It’s infuriating that it fails to keep your system clock in sync with the time-server, since that is its whole fucking job – that’s why it exists.
    As Steve Jobs would have said: “What is it supposed to do? So why the fuck doesn’t it do that?”

      1. If you have you menu bar clock showing seconds, you can see this by going to the Date & Time system preference pane. Just going to that pane will make your system say “Whoa! Well, look at that – I’m off of the timeserver by 23 seconds – I should do something about that!”
        Never mind the fact that pacemaker (Apple’s attempt to partially replace the venerable and near-perfect ntpd) was supposed to be doing that on a regular basis so your clock is always within a second or two of the timeserver.
        If you don’t have seconds displaying in the menu bar already, turn that on, then wait a few weeks and check the Date & Time system preferences pane: you can watch your clock suddenly jump to what it should have been all along.
        When you’ve got systems using timestamps, this can really fuck things up. And, it used to work flawlessly.

    1. Don’t blame the engineers. They aren’t the ones who map an unrfocused product planning strategy, set the unrealistic schedules, and arbitrarily shift budgets from one pet project to another without advance coordination. Apple has grown into a bureaucratic corporation and its late, buggy product releases (as well as total lack of product updates in many areas) demonstrate that Apple now has management problems.

  5. Thanks for listening Apple? That is way too late!! Disgusting. Next time listen immediately!

    It’s unbelievable evident that thing did not work and these guys did nothing. Reason why am still on Mountain Lion. We’ll see what Apple comes up with, hopefully it just works.

  6. Discovered was a total networking disaster – magnified if you used Apple wireless routers. I went to 10.10.4 Beta yesterday and all issues have been resolved.

    Hard to believe Apple would let this go on for so long. And there was no easy way for most users to get back to Mavericks for a quick fix.

    A total failure on Apple’s part after years of relatively smooth upgrades.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.