MacInTouch Amazon link...

macOS 10.14 Mojave

Channels
Apple


Yeah, I also notice it on my Gmail account. (I only have it for YouTube.)
Was on the phone for 90 minutes yesterday with Level 2 and 3 support. Apple engineers are aware (now) and are working on a solution. May be partially due to changes with Google's email APIs - the same ones that broke IFTTT and other services.
 


What fixed Gmail for me:

I had to go through the "forgot password" routine on the Google site when Gmail authentication failed in Mail on my laptop running Mojave 10.14.4.

Changed the password on one Google Mail account after selecting "forgot password" and obtaining an authentication code from Google as a text or call (curiously the old passwords worked on two other Gmail accounts after that.)

Then, of course, had to change to the new password on my iMac and iPhone. Grrrrrrr...
 


What fixed Gmail for me:
I had to go through the "forgot password" routine on the Google site when Gmail authentication failed in Mail on my laptop running Mojave 10.14.4.
Changed the password on one Google Mail account after selecting "forgot password" and obtaining an authentication code from Google as a text or call (curiously the old passwords worked on two other Gmail accounts after that.)
Then, of course, had to change to the new password on my iMac and iPhone. Grrrrrrr...
I wouldn't mind that workaround, but the first support person at Apple had me delete one of my email accounts from Internet Accounts/System Preferences, and I am now unable to create a new one without a "null" error. Grrr.
 


FWIW, the macOS 10.14.4 update had a few effects that I can see, all good. Safari seems much snappier now, Mail no longer hangs around as long after quitting, and the Dock's background has changed, making it easier to see what's going on. (I would be more specific, but I am not sure what the change was, except that the background seems lighter.)

And... the trimming of required manual activity when autofilling login credentials is a nice touch.
 


The macOS 10.14.14 combo updater fails on both my 2018 MacBook Pro 15” and wife’s 2018 MacBook Air. When the installer is run, it sits for 10-15 minutes at the ‘installing’ step and never asks to restart to begin the low-level work. It will eventually throw a generic error message.

I had to use the System Preferences update function to update, after which the combo updater ran fine.

The combo update ran fine on my 2015 MacBook Pro 15”.
 


I have had the opposite effect as others have observed since the update. Mail is particularly slow to load new messages through an iCloud account and to quit the app. FWIW, this is also true for the iOS update, too. It doesn’t matter what network I use. I just watch the spinner, sometimes for more than a minute.
 


One UI change in macOS 10.14.4 that I don't care for is the linking of the dock and menu bar transparency. Previously, there was a setting (somewhere, don't remember) that let me have a solid menu bar but a transparent dock. Now the only option I can find affecting transparency is in System Preferences > Accessibility > Display > Reduce Transparency, and that option is applied to both the dock and the menu bar.
 


I found a workaround to the Apple Mail Google G-Suite problem from MacRumors user @Gannett. Follow the instructions carefully. Also note that you need to repeat this process one by one for each G-Suite account by updating the email address in step 9 and then accessing the account in Apple Mail "Accounts". I had to select Contacts or Calendar and then click on another Account to trigger the Safari update window. Good luck.
MacRumors said:
Mac Mail App Broken for Some Gmail Users in macOS Mojave 10.14.4

Okay, so I've tried to make this as easy as possible. We're going to use Charles to rewrite a response from google to include the email address which is for some reason missing in google's own response. This is a one time setup only needed for verification.
  1. Download, install and run Charles. (it's free for 30 days and runs for 30 minutes at a time)
  2. If this is your first time using Charles it should prompt you to authorize automatic proxy configuration. Do this. (Otherwise just make sure the macOS proxy is enabled and working)
  3. From the Help menu choose SSL Proxying > Install Charles Root Certificate.
  4. Once the certificate is installed, find it in your keychain (type Charles into the search), open it, expand the Trust section and set to Always Trust. You will be prompted for your password when closing it.
  5. Back in Charles, from the Proxy menu choose SSL Proxying Settings.
  6. Add a new location with Host: people.googleapis.com.
  7. From the Tools menu choose Rewrite and click the Add button.
  8. Add a new location with Host: people.googleapis.com.
  9. Add a new action with the following details...
    • Type: Body
    • Where: Response
    • Replace Value: {"names":[{"metadata":{"primary":true},"displayName":"Your Name"}],"emailAddresses":[{"value":"your@email"}]}
    • (Make sure you put in your name and email address)
  10. Once you save this, we're all set. Go to your system Internet Accounts or (Mail) and authorize your account.
  11. If everything thing is working, you can quit Charles and feel free to delete the certificate from Keychain.
 





Ric Ford

MacInTouch
It looks like the Gmail problem is fixed, with no action needed on Apple's part.
Interestingly, however, it appears to be a problem only with macOS 10.14.4 and only with Apple Mail:
Apple Communities said:
Mojave 10.14.4 fails to Authenticate Gmail account
Just update to Mojave 10.14.4 and now Apple Mail will NOT connect to one of my Gmail accounts.

This issue is UNIQUE to Apple Mail as I can access the Gmail account using Spark on the same computer without issues.

This issue is UNIQUE to Mojave 10.14.4 as it did not exist with 10.14.3 and it does not exist on another computer running an earlier version of Mac OS X.
 


After updating to macOS 10.14.4 (did not notice this beforehand), I ran Disk Utility and received 3 warnings (all identical) stating directory valence check: directory (old 0x7004c): orphan directory record.

Subsequent running of Disk Utility on both the startup disk and my backup clone have not eliminated these warnings. Anything to be concerned about?
 



I'm not sure the Gmail authentication problem was unique to macOS 10.14. I had a similar problem on Sierra. It was hard to diagnose, because Apple Mail stinks at handling errors (or sometimes it just fails silently).

I first saw the problem back in February. Mail would fail to authenticate, demanded that I re-enter the password, and refused to do anything else until I did, even though the password was correct. So, of course, it failed again. Mail apparently assumes that every failure is a password problem.

Thunderbird revealed the real error message being returned from Gmail:

Web login required: https://support.google.com/mail/answer/78754

Supposedly, Mail is supposed to pop up a Google authentication dialog, which 'blesses' your email app for use with Gmail. This wasn't happening, so Gmail didn't trust Apple Mail and refused the connection. Thunderbird did show the Google authentication, but the connection still wasn't blessed. I think this was due to a change on Gmail's end.

It was finally fixed a few days or a week later, so it worked it again. It may not be the same issue being seen with macOS 10.14.4 though.

I would suggest trying to connect with Thunderbird, it will at least tell you what the real error is, while Apple Mail hides it. Sometimes Mail just fails silently and behaves as if there is nothing new to retrieve.
 


I found a workaround to the Apple Mail Google G-Suite problem from MacRumors user @Gannett. Follow the instructions carefully. Also note that you need to repeat this process one by one for each G-Suite account by updating the email address in step 9 and then accessing the account in Apple Mail "Accounts". I had to select Contacts or Calendar and then click on another Account to trigger the Safari update window. Good luck.
I found two workarounds...

1. You may have success creating an account in Internet Accounts (system preferences) using the generic Mail button instead of Google, or...

2. I changed the security setting in my G Suite to the most lax, then clicked on this link to disable Google's captcha (temporarily):
I then recreated the mailboxes using the Google button in Internet Accounts.

Either way...

3. Seriously, Apple -- this is crazy, and you should make it work.
 


Ric Ford

MacInTouch
Thunderbird revealed the real error message being returned from Gmail:
Web login required: https://support.google.com/mail/answer/78754
Supposedly, Mail is supposed to pop up a Google authentication dialog, which 'blesses' your email app for use with Gmail.
I encountered this Gmail authentication process in Postbox around that time, too, but Postbox handled it successfully. I suspect the macOS 10.14.4 failure may be a new, different issue.
 


I just noticed that Energy Saver Preferences no longer has a sleep option, just display settings. I am sure it was there when I started Mojave last year (2018 Mac Mini), but I don't know which "security update" removed it. The terminal command getcomputersleep returns Never, so it has maintained my original setting.
 


Ric Ford

MacInTouch
I just noticed that Energy Saver Preferences no longer has a sleep option, just display settings. I am sure it was there when I started Mojave last year (2018 Mac Mini), but I don't know which "security update" removed it. The terminal command getcomputersleep returns Never, so it has maintained my original setting.
I just compared Energy Saver preferences in macOS 10.12.6 and macOS 10.14.4, and they look identical to me.

"getcomputersleep" didn't work for me on either system.
 


I just noticed that Energy Saver Preferences no longer has a sleep option, just display settings. I am sure it was there when I started Mojave last year (2018 Mac Mini), but I don't know which "security update" removed it. The terminal command getcomputersleep returns Never, so it has maintained my original setting.
The sleep option is a checkbox for 'Prevent computer from sleeping automatically when the display is off'
 


I just compared Energy Saver preferences in macOS 10.12.6 and macOS 10.14.4, and they look identical to me.

"getcomputersleep" didn't work for me on either system.
My macOS 10.13.6 High Sierra system still has the "Computer sleep" setting in Energy Saver right above the "Display Sleep" setting. The 10.14.4 Mojave system eliminates the computer sleep and replaces "Display Sleep" with "Turn display off after."

Earlier I used the shorthand term for computer sleep setting; the full terminal command I ran from the admin account:
Code:
sudo systemsetup -getcomputersleep
 


Ric Ford

MacInTouch
My macOS 10.13.6 High Sierra system still has the "Computer sleep" setting in Energy Saver right above the "Display Sleep" setting. The 10.14.4 Mojave system eliminates the computer sleep and replaces "Display Sleep" with "Turn display off after."
Are you looking at battery settings for one and power adapter settings on the other?
 


Are you looking at battery settings for one and power adapter settings on the other?
Both systems are Mac Mini (2018 and 2011), so no battery tab exists. If it helps, the 2011 macOS 10.13.6 MacBook Air has both the computer and display sleep options in the power adapter and the battery tabs.
 


I have recently installed Mojave on a 17" 2008 MacBook Pro using the patch tool published by "dosdude1". It works surprisingly well, considering the machine has only 4 GB of RAM.

But my main reason for building this machine was to watch movies, and I have found that Mojave won't let me double-click .dvdmedia folders to play movies in the DVD Player application.

I have read that I can simply run Apple's DVD Player and then choose File > > Open and then open the video_ts folder inside the .dvdmedia folder to play a movie. Unfortunately this does not work. Has anyone figured out a way to get .dvdmedia folders to play using Apple's DVD Player app in Mojave?
 


My macOS 10.13.6 High Sierra system still has the "Computer sleep" setting in Energy Saver right above the "Display Sleep" setting. The 10.14.4 Mojave system eliminates the computer sleep and replaces "Display Sleep" with "Turn display off after."
This must vary depending on hardware. My 2010 iMac running macOS 10.13.6 has the older two slider settings, but my 2018 MacBook Pro, also running 10.13.6, has the single "Turn display off after".
 


I'm still hesitating to move ahead to Mojave because I have a late 2015 iMac 27" with a Fusion drive and have heard that there can be terrible slowdowns with APFS.

Does anyone know whether things have gotten better in that respect with the latest point versions of Mojave?
 


I'm still hesitating to move ahead to Mojave because I have a late 2015 iMac 27" with a Fusion drive and have heard that there can be terrible slowdowns with APFS. Does anyone know whether things have gotten better in that respect with the latest point versions of Mojave?
Give us more data, for example [the results of the Terminal command] diskutil list

If you have a 'tiny' SSD along with a slow hard drive, slow happens. With a 'larger' SSD, not so bad. One might consider an external boot drive SSD of 500 GB or larger connected by USB 3 or even Thunderbolt for best performance. There have been lots of posts about using 3M double-stick tape for integrating the external drive with the iMac base.
 


Give us more data, for example [the results of the Terminal command] diskutil list
If you have a 'tiny' SSD along with a slow hard drive, slow happens. With a 'larger' SSD, not so bad. One might consider an external boot drive SSD of 500 GB or larger connected by USB 3 or even Thunderbolt for best performance. There have been lots of posts about using 3M double-stick tape for integrating the external drive with the iMac base.
James, it looks like the SSD part of the Fusion drive (dev0) is 128GB (EFI 210MB, CoreStorage 121GB, boot 134MB). So it's not the tiny 32GB one. The spinning part is a Seagate ST2000DM001 (7200 rpm).

Yes, slow happens generally, but I'm wondering about Mojave specifically, where people with Fusion drives have reported radical changes in performance just between a previous OS and Mojave, presumably due to the file system change.
 


Yes, slow happens generally, but I'm wondering about Mojave specifically, where people with Fusion drives have reported radical changes in performance just between a previous OS and Mojave, presumably due to the file system change.
I can only report my personal experience. Ten days ago I upgraded my Late 2013 iMac 21.5" with Fusion Drive from High Sierra 10.13.6 to Mojave 10.14.4. The upgrade took a little over one hour and proceeded smoothly. Everything works as expected, and I see no discernible performance hit. On the contrary, the machine mostly feels snappier. I see no longer startup or login than I was used to. The only thing I notice is that for some applications, both launching and quitting seem to take a little more time than before.
 



Which Fusion drive do you have, Ronald? Is it the 1TB or the 2TB/3TB version with the larger SSD component?
It is a 1TB Fusion drive with 128GB SSD component (and I forgot to mention that FileVault is enabled).

diskutil list

/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *121.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 121.1 GB disk0s2

/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_APFS Container disk2 1000.0 GB disk1s2
 


In a moment of weakness, I installed the macOS 10.14.5 public beta on my 2018 Mac Mini. No problems, though I didn't try Recovery Mode. VMware Fusion worked.

The second public beta installed without any apparent problem, but VMware Fusion broke. It can't find the file dev/vmmon and fails to open any VM. No problem, I thought. I'd just turn off SIP and reinstall.

However, Recovery Mode is also broken. It starts to load but stops cold with a black screen.

I tried starting from the public beta 1 recovery partition on a backup drive, but that stopped with an error saying a software update was required. I accepted the update, and the result still stopped dead at a black screen.

Finally, I tried starting from a pristine 10.14.4 recovery partition. Again, I got a message saying a software update was required. This time I declined. The main 10.14.4 partition on that drive starts up normally.

I suspect that Apple changed the boot ROM. The version I have after public beta 2 is

220.260.154.0.0 (iBridge: 16.16.5107.5.2,0)
 


Yes, slow happens generally, but I'm wondering about Mojave specifically, where people with Fusion drives have reported radical changes in performance just between a previous OS and Mojave, presumably due to the file system change.
I have a 2017 27" iMac with 2TB fusion drive. No long ago I upgraded from Sierra to Mojave 10.14.3. I've definitely not noticed a slowdown, if anything the iMac is a bit faster. One definite improvement is with Safari. Under Sierra (with version 12.0), every page would start loading, then stall for 5-10 seconds with the blue line about an inch long, then resume loading. Under Mojave, the stall went away most of the time. I still have it occasionally, but now I assume it's the fault of the web site, not my Mac.

Otherwise, the upgrade has been problem-free with one exception. My Epson Workforce 635 printer no longer prints two-sided with long edge binding. No matter what setting I use, I get short edge binding. I attribute this to the old driver (the printer is more than five years old) which is 32-bit; I'm certainly hoping Epson upgrades it to 64-bit for 10.15.
 


In a moment of weakness, I installed the macOS 10.14.5 public beta on my 2018 Mac Mini. No problems, though I didn't try Recovery Mode. VMware Fusion worked.

The second public beta installed without any apparent problem, but VMware Fusion broke. It can't find the file dev/vmmon and fails to open any VM. No problem, I thought. I'd just turn off SIP and reinstall.
The problem with VMWare Fusion may be related to a change that Apple is implementing much sooner than they said it would: the requirement that kexts (kernel extensions) be notarized.

Until April 9, Notarizing Your App Before Distribution said:
In macOS 10.14, notarizing your software is optional, but recommended. In a future version of macOS, notarization will be required.
That page now says:
Beginning in macOS 10.14.5, all new or updated kernel extensions and all software from developers new to distributing with Developer ID must be notarized in order to run.
It appears from experimentation that "new or updated" really means "not seen by the system before". If you have a clean install of 10.14.5, anything that uses kexts that are not notarized will not work properly.

Many VPN clients are affected by this, as they use "tap" kexts that are not yet available in notarized versions.
 



In a moment of weakness, I installed the macOS 10.14.5 public beta on my 2018 Mac Mini. No problems, though I didn't try Recovery Mode. VMware Fusion worked.

The second public beta installed without any apparent problem, but VMware Fusion broke. It can't find the file dev/vmmon and fails to open any VM. No problem, I thought. I'd just turn off SIP and reinstall.

However, Recovery Mode is also broken. It starts to load but stops cold with a black screen.
Mojave 10.14.5 Beta 2 (18F108f) is running fine on my 2018 Mac Mini. Out of curiosity, I tried reinstalling macOS from recovery mode. I had to do an *internet* recovery (cmd-opt-R) to connect to Apple’s server.

The first installation screen offered macOS Mojave Beta and when I proceeded it also told me that an update was required, but I elected to continue (instead of Update or Cancel). After it finished, my system was now macOS 10.14.4, not beta. Turns out that it’s possible to revert back to the current version from the public beta.

I have no problem with beta 2 of Mojave, but I just wanted to see if it was possible to downgrade back to macOS 10.14.4. After this, I was able to reinstall the public beta.
 


... The second public beta installed without any apparent problem, but VMware Fusion broke. It can't find the file dev/vmmon and fails to open any VM. No problem, I thought. I'd just turn off SIP and reinstall. However, Recovery Mode is also broken. It starts to load but stops cold with a black screen.…
Mojave 10.14.5 Beta 2 (18F108f) is running fine on my 2018 Mac Mini. Out of curiosity, I tried reinstalling macOS from recovery mode. I had to do an *internet* recovery (cmd-opt-R) to connect to Apple’s server. The first installation screen offered macOS Mojave Beta and when I proceeded it also told me that an update was required, but I elected to continue (instead of Update or Cancel). After it finished, my system was now macOS 10.14.4, not beta. Turns out that it’s possible to revert back to the current version from the public beta.
I have no problem with beta 2 of Mojave, but I just wanted to see if it was possible to downgrade back to 10.14.4. After this, I was able to reinstall the public beta.
I had completely forgotten about Internet recovery. I did that and am now happily back at macOS 10.14.4. The recovery went forward with no notices or choices presented, and my regular desktop appeared at the end.

VMware Fusion is working again, with no need to reinstall. Regular recovery (Cmd-R) is also working again.

I'll wait on further macOS version updates while Apple and VMware sort things out.

Many thanks!
 


I purchased and installed Malwarebytes Premium Edition on my MacBook Pro. I cannot activate it for the premium features. It says that the Mojave OS blocked it from running, even though in the security pane I allow Malwarebytes to have the run of the hard disk. It is hard to understand some of the comments in the FAQ on their web page.
 


I'm a bit late to the Mojave party, but I have a predicament with regard to printing: my (now elderly) Epson Artisan 725 inkjet photo all-in-one printer apparently isn't supported with an Apple driver. The Add Printer dialog box suggests that I contact the vendor.

When I look up the Artisan 725, I see that it has a High Sierra driver, but no Mojave driver available. Is there any way to force Mojave to try this driver? Or will that fail?

I see that the Artisan 710 model is supported in Gutenprint; it uses the same Claria ink that the 725 model uses, do you think that is an option?

Just for reference, I should mention that my Mojave install was an upgrade from a clean install of High Sierra, but High Sierra was just a brief stopover as means to update firmware, in which I never got as far as installing printer drivers - I wonder if they would have been carried along into Mojave if I had installed them into High Sierra?

I'm using a 2010 classic Mac Pro 5,1 with the MSI RX560 GPU card, which is why I had the brief stopover in High Sierra.
 


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

Latest posts