New day, new issue for Apple’s new MacBook

Aug 10, 2018 08:22 GMT  ·  By

Just when it seemed that all problems are gone for buyers of Apple’s new 2018 MacBook, here’s another issue that may soon become widespread as well.

A growing number of customers are reporting crackling sounds from their MacBook speakers, and by the looks of things, the issue appears at random times with no clear pattern established so far.

There doesn’t seem to be a specific app triggering the issue, and a report from MacRumors points to a number of causes suggested by users, including radio interference due to a lack of shielding, audio drivers, and the T2 chip.

However, the crackling sound shows up occasionally regardless of the app running on the MacBook, including iTunes, YouTube videos, and even when running Windows on Boot Camp.

Videos that have been posted on YouTube reveal how the problem affects audio performance, and posts on Apple Support Communities and Reddit confirm this isn’t an isolated issue.

Apple Store replacing defective units

However, the bug isn’t really widespread so far, though the number of reports is expected to increase as more people become aware of the problem and turn to social media to share their experience.

Apple has remained tight-lipped so far on this problem, yet the company is most likely investigating the bug already. According to posts on company’s support forums, support engineers don’t know how to fix the issue just yet.

“I have a problem with mine as well! I got the 15" i9 version and it was very annoying how the sound would randomly cut-off with no obvious reason, went to the apple store got it replaced but still the same issue persists on the new one as well! (not as frequent though). I'm currently in touch with Apple support and they have the sysdiagnose for both MacBooks and I'm just waiting for apple engineers to figure out exactly what is going on,” one user explains.

It remains to be seen if this is a software issue that can be resolved with an update or Apple needs to launch a recall, but the only thing you can do right now if you’re hitting the same bug is to get in touch with support.