MacInTouch Amazon link...

Apple quality issues

Channels
Apple
Snow Leopard wasn't as buggy, at least by the final release, was it?
It would take intensive research of MacInTouch and other archives to even begin to quantify an answer. My personal recollection is that every OS X and macOS release since 10.3 has had some foibles in the initial release(s).

My Snow Leopard Server 10.6.8 VMs are rock solid for my uses.

It does seem that, at least since 10.14.4, major Mojave problems generally revolve around things like Gmail authentication changes and Adobe Acrobat DC's penchant for crashing just because it was launched or asked to open a file. I see about a 50% success rate in opening, reading, and modifying PDF files without crashing. But this began well before Mojave. Apple-generated faults seem to be primarily removal/hiding of functions rather than simple programming errors.

I recently upgraded a Mini to the latest hardware version and Mojave 10.14.4. Instantly successful were all peripherals, Vuescan, Indigo (home control), Scansnap, Dyn Updater, Office 365, Adobe CC Photo, Malwarebytes, Keyboard Maestro, BBEdit, and Screens 4/Connect, along with the usual Apple suspects. I confess that I did migrate just the user accounts and system configuration, but did fresh download and installs of the third-party applications, along with the usual toolbox of utility programs. With the exception of adding a Thunderbolt to FireWire dongle, the new Mini was literally a drop-in replacement for the old Mini - every cable, even including the AC cord. (I did put the new MAC address in DHCP reservations.)

So, I am well satisfied with both Snow Leopard Server 10.6.8 and Mojave 10.14.4 as reasonably reliable and fit for purpose. And also super-happy with the Mac Mini 8,1 with i7, 16GB, and 500GB SSD, and multiple external drives.
 


It would take intensive research of MacInTouch and other archives to even begin to quantify an answer. My personal recollection is that every OS X and macOS release since 10.3 has had some foibles in the initial release(s).
The general rule of thumb in our part of the world was to wait for the 10.x.3 release to be made available before fully committing to that version of Mac OS X. In addition to the CD/DVD sets for 10.x.0, Apple also tended to release a new set of media for 10.x.3 up through Snow Leopard.
 


The general rule of thumb in our part of the world was to wait for the 10.x.3 release to be made available before fully committing to that version of Mac OS X. In addition to the CD/DVD sets for 10.x.0, Apple also tended to release a new set of media for 10.x.3 up through Snow Leopard.
The problem is that, since the change to annual major macOS releases with OS X 10.8 Mountain Lion, as soon as one macOS is released, Apple is already targeting fixes to the next release. The only fixes you get in the current release are for security issues and major issues.

Also, consider what the difference really is between major vs. point macOS releases: point releases are supposed to maintain framework compatibility, but major releases don't have to.

So this means that there's never a really stable macOS release anymore.
 






Ric Ford

MacInTouch
A friend of mine has experienced Home button problems with an iPhone 5s and an iPhone 4/4s. He ultimately resorted to awkward software workarounds with the iPhone 4/4s. We tried many proposed fixes with the iPhone 5s but had no success. This lawsuit seems to be about a different button, the power button that Apple called "sleep/wake" (and then renamed again recently).
AppleInsider said:
Power button class action suit for iPhone 4, iPhone 4s, iPhone 5 will be heard on Oct. 25
A class action lawsuit against Apple concerning sleep/wake button issues with the iPhone 4, iPhone 4s and iPhone 5 is going to be heard in a Californian court, with the lawyers bringing the lawsuit against the iPhone producer putting out a call for potentially affected device owners ahead of the October trial.

Launched in May 2013, the lawsuit is based on claims there is a design flaw with the sleep/wake button in the iPhone 4, one where the component failed typically about a year after acquiring the device. A recent update to the lawsuit reveals it will finally get its day in court this fall, and will cover the iPhone 4s and iPhone 5 as well.
 


Important recall notice from Apple for international MacInTouch readers. While this does not seem to affect most in the US market, Apple is issuing a recall for some power adapters used elsewhere.
Apple said:
Apple Three-Prong AC Wall Plug Adapter Recall Program
Apple has determined that, in very rare cases, the Apple three-prong AC wall plug adapters designed primarily for use in the United Kingdom, Singapore, and Hong Kong may break and create a risk of electrical shock if exposed metal parts are touched. This wall plug adapter shipped from 2003 to 2010 with Mac and certain iOS devices, and was also included in the Apple World Travel Adapter Kit.
 


Interestingly, the Apple page describing how to exchange an affected 3-prong AC Wall Plug Adapter says:
Apple Three-Prong AC Wall Plug Adapter Recall Program
... We will need to verify your Mac, iPad, iPhone or iPod serial number as part of the exchange process so please find your serial number in advance.
I guess, if one is using the adapter for a different device and no longer own an Apple device, one is out of luck. On the other hand, I suspect that if I took my Apple Travel Kit box to a store, they'd just replace the affected plug.
 


Latest from Casey Johnston on the infamous MacBook keyboards:
Casey Johnston said:
Apple Owes Everyone An Apology And It Should Start With Me, Specifically
... It’s clear at this point that I am extremely not alone in having this problem; developer Marco Arment has written extensively about it, the Wall Street Journal’s Joanna Stern recently wrote an entire column with authentically dropped e’s and r’s that were the result of her new (broken) MacBook Air keyboard. (Stern, notably, actually managed to get a real apology out of the company, unlike me. But Apple has yet to match those words with tangible action, like, for instance, making notebooks with working keyboards and offering them as replacements to all of the people who unwittingly bought computers that were bound to break.)
Comment from John Gruber:
These keyboards are the biggest mistake in Apple’s history.
 



Ric Ford

MacInTouch
Apple's stonewalling on this critical problem seems perverse to me (exactly the opposite of the leadership we used to expect from the company). I'm sure it has nothing to do with forcing more people to visit Apple Stores...
Forbes said:
Why Is Tim Cook Hiding His Fix For The Embarrassing MacBook Problems
While it is not a complete eradication of the problem, the news that Apple will be prioritising repairs to MacBook butterfly keyboards by repairing them at Genius Bars, rather than have them shipped to a central repair centre will be welcomed. It drops the repair time from around five working days to a potential twenty-four turnaround.

It’s just a shame that Apple has not publicly acknowledged this and offered beleaguered users a small amount of comfort around the time they are deprived of their laptop.
 


Forbes said:
Why Is Tim Cook Hiding His Fix For The Embarrassing MacBook Problems
While it is not a complete eradication of the problem, the news that Apple will be prioritising repairs to MacBook butterfly keyboards by repairing them at Genius Bars, rather than have them shipped to a central repair centre will be welcomed. It drops the repair time from around five working days to a potential twenty-four turnaround. It’s just a shame that Apple has not publicly acknowledged this and offered beleaguered users a small amount of comfort around the time they are deprived of their laptop.
"While it is not a complete eradication of the problem..."?

It doesn't solve the problem at all; rather, it attempts to cover it up with quickie repairs. Total male cow manure. Want to actually solve the problem, Tim? Kill this butterfly-keyboard design and add 2mm to the MacBook Pro's thickness to permit the old keyboard to fit. If Apple thinks I'm going to buy a device whose keyboard has key travel the thickness of a business card, they're nuts. There's nothing "better" about this keyboard. It's a disgrace.
 


Ric Ford

MacInTouch
Not to put too fine a point on it...
Howard Oakley said:
TextEdit goes out of its way to destroy data
It’s very unusual to catch a Mac app going out of its way to destroy your data, but recently Chris Hamady (@chamady, via @lapcatsoftware) drew attention to a glaring example in TextEdit. Not only that, but it’s been doing this since Yosemite back in 2014, and persists in TextEdit version 1.14 in Mojave 10.14.4....

... For many years, Apple used TextEdit as exemplary code for macOS developers to see how it’s done. The last time it did this was seven years ago, in early 2012, since when I can only presume that TextEdit has gone steadily downhill and is now too embarrassing to release in source form. Like so many other standard tools in macOS, TextEdit is another festering sore on the rump of Apple’s engineering indolence.
 


Ric Ford

MacInTouch
This is discouraging, if you bought an iPhone 7...
AppleInsider said:
iPhone 7 'Loop Disease' audio chip issue targeted in class action complaint
A new class action complaint seeks damages and a hardware recall from Apple over the so-called iPhone 7 "Loop Disease," an issue that causes audio problems on impacted handsets and can ultimately render the device inoperable.

... Referred to as an "Audio IC Defect," the symptoms of the apparent hardware issue are identical to those described by users who suffered a previously known problem dubbed "Loop Disease" by some repair industry insiders.

... The suit attributes the defect to what amounts to poor design. Specifically, iPhone 7's aluminum chassis is made from "substandard materials" that allows for flexion directly over the audio controller attached to the phone's logic board. Over time, solder connecting the audio IC chip to the logic board fails, resulting in a range of problems.
 


Drag and Drop function is random when editing text of a new message in Apple Mail. Sometimes it does a Copy and Paste, sometimes Cut and Paste. Which operation occurs is unpredictable. The correct behavior is to Cut and Paste, when selected text is dragged and dropped in a new location, or Copy and Paste if the Option key is held.

This Drag and Drop behavior in text editing was described in Inside Macintosh about Volume III and has been standard since about 1986. According to Inside Macintosh, this editing procedure is implemented by system calls, where the determination whether to Cut or Copy is indicated by a single bit in the calling message, which is set or not. Applications other than Mail, from Apple or other vendors, behave according to the standard. My guess is Mail does not properly initiate Drag and Drop operations due to not setting the bit which distinguishes Copy... from Cut... when the message is created. If my guess is accurate, this bug could be fixed by having the Edit object properly initiate itself.

In Apple Discussions, I first reported this bug in Mac OS X 10.6.7 on May 20, 2011. I found other reports had noted the issue as far back as October, 2009. Although a few users reported not being able to replicate the problem, others confirmed the bug in all Mac OS versions from 10.5. After Apple created Feedback Assistant to facilitate bug reporting from users, I submitted six Feedback Assistant reports, beginning September 9, 2014, with the most recent on December 2, 2015.

Whether Drag and Drop does Cut and Paste, or Copy and Paste, is still random in Mail in Mojave 10.14.4. I have given up reporting this issue....
 


... This Drag and Drop behavior in text editing was described in Inside Macintosh about Volume III and has been standard since about 1986. According to Inside Macintosh, this editing procedure is implemented by system calls, where the determination whether to Cut or Copy is indicated by a single bit in the calling message, which is set or not. Applications other than Mail, from Apple or other vendors, behave according to the standard....
I have found Drag and Drop increasingly unreliable in general. Most of the time it's almost impossible to pick up the text I have selected and move it to another point in Apple Mail (or other apps). But once in a while it works. When I was working on a new edition of a book in late 2017, trying to use drag and drop on ".doc" files from the previous edition would crash Word 2011, so I had to turn off the Drag and Drop option. (Converting to .docx files also seemed to help.)
 


The bug appears to copy when a selection is dragged and inserted forward and cut when the selection is dragged and inserted backward, the exception being that full paragraphs drag and drop correctly.
 


More evidence that Apple doesn't care about Apple Mail quality: attachment selection has been broken at least since 2013, when I switched from Eudora.

I can't cite chapter and verse of the human interface guidelines, but every place else in the Mac interface, holding shift while selecting gives you a contiguous selection, while holding command lets you select multiple individual items non-contiguously. When selecting attachments in a mail message, shift-select works as expected, but the command key does nothing. Try it: in a message with multiple attachments, hold down command and try to select multiple attachments. You will be left with only the last one you clicked being selected.

How could something so basic be missed for so long? My only conclusion is that no one inside Apple must use Apple Mail for any productive activity. Does anybody know what they use? Slack?

Yes, I reported it.
 


More evidence that Apple doesn't care about Apple Mail quality: attachment selection has been broken at least since 2013, when I switched from Eudora
I just tried this in macOS 10.14.5 Beta (18F127a), and Command-click to select random attachments in Mail.app (12.4) works as expected. I selected three random documents, and all were attached to email.
 


I just tried this in macOS 10.14.5 Beta (18F127a), and Command-click to select random attachments in Mail.app (12.4) works as expected. I selected three random documents, and all were attached to email.
Lee, I believe the original poster is talking about trying to select multiple attachments already within an existing email message - either one already received or one already sent - not referring to selecting files to attach to a new message or to a reply.
 


There's also some weird stuff going on with drag-and-drop while using Screen Sharing to control another Mac, in High Sierra, such as:

Have two Finder windows open, where one is partially overlapping the other. The window you're dragging to should be the Active window, the window you're dragging from should be behind it. Now try and drag an icon to the active window, and then drop it. But here's the key: drop it in an area that is in the bounds of the source window, even though it is behind where you're dropping.

The result is that the drop is rejected, and the icon bounces back to the source window. Or, depending on what area of the source window is directly under the drop point (but behind the window that you're dropping in!), really weird things can happen such as, when the source window's sidebar is under the drop point.

It is like when Screen Sharing is used, the Finder isn't using the normal window layers but something else entirely.
 


This is very small potatoes in the grand scheme of things, but has anyone noticed what happens when you highlight a single character in Pages with the intent to replace it? For example, say you neglected to capitalize the first letter in the first word of a sentence, and you want to make it uppercase by typing the correct capital letter to replace the highlighted lowercase one.

I can't tell you the number of times I've performed this same action I've been doing for decades on all other Mac programs, and it doesn't work. I often do this out of habit without even looking at the screen — and find when I do that the lowercase letter is still there, followed by the uppercase one.

It turns out that first letter will only be highlighted if you "hold" the initial selection for at least a couple of seconds before releasing the mouse button. If you don't, the highlighting simply doesn't "take."

Just another wonderful feature in the "upgraded" version of Pages that came out a few years ago, joining the wonderfulness of having more than 100 features of Pages 9 simply disappear.

For the record, I am now officially done with ever upgrading my OS, as I understand that macOS 10.15 will only work with 64-bit apps, and Pages 9, which I still use every single day of my working life, is 32-bit.
 


For the record, I am now officially done with ever upgrading my OS, as I understand that macOS 10.15 will only work with 64-bit apps, and Pages 9, which I still use every single day of my working life, is 32-bit.
While I share your sentiment about Pages '09 (and some other 32-bit software), I think security updates are reason enough that one should update and instead look into virtualizing an earlier version, as has already been discussed here. If it's still available from Apple, Snow Leopard Server would be my pick.
 


... I can't tell you the number of times I've performed this same action I've been doing for decades on all other Mac programs, and it doesn't work. I often do this out of habit without even looking at the screen — and find when I do that the lowercase letter is still there, followed by the uppercase one. It turns out that first letter will only be highlighted if you "hold" the initial selection for at least a couple of seconds before releasing the mouse button. If you don't, the highlighting simply doesn't "take." ...
I don't know how you're highlighting the single character (with the mouse, or with the shift key and arrow, or some other way I don't know about), but I have just tried this in my version of Pages (v. 8.0) with High Sierra, and I cannot reproduce the glitch you describe. If I select a character – either with the mouse (and not hovering for any length of time) or with the arrow and shift key – whatever I type immediately replaces the selected character.

So it may have been fixed after Pages '09. If that's the case, I guess if you don't upgrade, you're stuck with the glitch. Of course, there could be something wrong with your copy of Pages, but that would be an odd, tiny manifestation of corruption.
 


I don't know how you're highlighting the single character (with the mouse, or with the shift key and arrow, or some other way I don't know about), but I have just tried this in my version of Pages (v. 8.0) with High Sierra, and I cannot reproduce the glitch you describe. If I select a character – either with the mouse (and not hovering for any length of time) or with the arrow and shift key – whatever I type immediately replaces the selected character. So it may have been fixed after Pages '09. If that's the case, I guess if you don't upgrade, you're stuck with the glitch. Of course, there could be something wrong with your copy of Pages, but that would be an odd, tiny manifestation of corruption.
To be clear, this behavior is in Pages 5.6.2, not Pages '09. (I'm not able to upgrade to the very latest version of Pages 5, as I'm still working in Yosemite for valid reasons I won't go into). It happens when I highlight one character with the mouse.

I've just done some experimenting now in my version of Pages 5.6.2, and I get inconsistent behavior. I'm trying as hard as I can to make the duration of the highlighting the same each time, but sometimes it "takes" and sometimes it doesn't. (I thought maybe the width of the character might make a difference, but that doesn't seem to be the case either.)

I've never seen this behavior in Pages '09, or in any other Mac app, for that matter. Perhaps it was fixed in more recent versions of Pages 5.

It's not that big a deal, as I continue to work in Pages '09, and work in the Pages 5 version only when I absolutely have to. I just noted it as a curiosity, and an example of a "small, stupid bug" (as a MacInTouch summary states!).
 


My list of issues with Apple apps and the Finder is long, but Preview has a couple of annoying issues that have lived on since El Capitan and persist in Mojave.

Initiate a search in Preview with multiple results. Select one of the results in the sidebar. Scroll away from the page corresponding to the result. There is no way to go back to that page by clicking on the result in the sidebar. If you click in the body of the document, the active result changes from blue to grey, but clicking on the greyed-out result will not take you back to the page. You must click on another result and then back on the initial result to get to the corresponding page.

Drag, say, the thumbnail for a page in a multi-page PDF from the sidebar to some location. Then delete that page. Now drag the thumbnail for another page to the sidebar to add it to the PDF. The deleted page shows up. The next drag works as expected - of course, you have to delete the supposedly deleted page again.

This is new to Mojave and I am not if it is a feature or bug: I can open 14 PDF documents, and they will open in separate windows in Preview. Opening the 15th file, either by double-clicking in the Finder or using the Open menu in Preview, will open that, and all subsequent documents, in a tab in the active window. However, the newly opened tab will not become active. You can then drag that tab to create a new window. For a while I couldn't figure out what was happening with newly opened documents, as I did not notice the extra tabs right away. I have the "Prefer tabs when opening documents" set as "Manually" in System Preferences.

Like I said, my list is long and growing longer.
 



"Linus Tech Tips" recently released an interesting video describing some of the heat management choices and related performance tradeoffs on Apple hardware:
Linus is fun, and often makes good points, but I think he's being disingenuous here. Equivalent Windows laptops that compress CPUs capable of boiling water into super-thin Ultrabook cases will also run slower than they could with adequate cooling - e.g., Dell XPS 15 9570.

Over in Windows land, there are laptops with much more generous cooling than any MacBook Pro. At the price of thick and heavy, they're more likely to deliver the speed their components promise. And have RAM and storage that's user upgradable.

The current 15" MacBook Pro weighs 4.02 lbs. The Acer Predator Helios 500, which has been praised for thermal management of the Core i9 chip, is 8.8 lbs. I won't say it needs a dolly, but there's something difficult to imagine about graphics designers lugging in such beasts to conference tables at Madison Avenue advertising agencies.
 


Ric Ford

MacInTouch
"Linus Tech Tips" recently released an interesting video describing some of the heat management choices and related performance tradeoffs on Apple hardware:
Linus is fun, and often makes good points, but I think he's being disingenuous here. Equivalent Windows laptops that compress CPUs capable of boiling water into super-thin Ultrabook cases will also run slower than they could with adequate cooling - e.g., Dell XPS 15 9570. Over in Windows land, there are laptops with much more generous cooling than any MacBook Pro. At the price of thick and heavy, they're more likely to deliver the speed their components promise. And have RAM and storage that's user upgradable.
The current 15" MacBook Pro weighs 4.02 lbs. The Acer Predator Helios 500, which has been praised for thermal management of the Core i9 chip, is 8.8 lbs. I won't say it needs a dolly, but there's something difficult to imagine about graphics designers lugging in such beasts to conference tables at Madison Avenue advertising agencies.
The Linus video is very interesting, and anyone interested may be able to reproduce his tests on other systems, such as the Dell XPS 15, or a Dell G5 Gaming with superior cooling.

Whether disingenuous or not, Linus also provided an answer early in his video to his later unanswered question of why Apple didn't do a better job with thermals in recent MacBook Pros. As I believe Lyman mentioned here in the past, Intel is way behind its promises for delivering smaller CPU lithography, with its lower power requirements, and there's nothing Apple could do about that, other than adjust its designs, which it seems completely unwilling to do (for obvious reasons of cost, etc.).

(Linus also talks about the issue of Apple's misleading advertising.)
 





Here are just a few of the known bugs in the latest macOS release. (It sure would be helpful to have access to Apple's secret list of bugs, but that will obviously never happen.)
This list makes me wonder if I am (for the time being, anyway) safer remaining with the macOS 10.14.3 that my Mac shipped with. Any consensus?
 


Ric Ford

MacInTouch
This list makes me wonder if I am (for the time being, anyway) safer remaining with the macOS 10.14.3 that my Mac shipped with. Any consensus?
Well, each macOS update patches serious security holes... (so I guess the question is whether it introduces more than it patches...).
 



This list makes me wonder if I am (for the time being, anyway) safer remaining with the macOS 10.14.3 that my Mac shipped with. Any consensus?
Not all of us see the same errors. For example, I added two new keyboard app shortcuts to a macOS 10.14.5 instance with no truncated display problem as reported by Howard Oakley.

My practice is to live with each update for a while before recommending or performing the update on client machines. Certainly, I see lots of problems in beta testing (hello, Safari Technology Preview), but that is expected in beta testing.

The scariest problem with, for example, the macOS 10.14.5 update is the seemingly erratic display of multiple progress bars through the update [process]. I suppose at least some of this is due to firmware upgrades, such as those included with macOS 10.14.5 for many machines.

So, presuming that you have adequate (meaning multiple and current) backups, there is no overwhelming reason to not upgrade when you want to (or have to).
 




Amazon disclaimer:
As an Amazon Associate I earn from qualifying purchases.

Latest posts