macOS 10.14.4 G-Suite bug is fixed

The previously reported bug that caused a login loop for Google-hosted G-Suite accounts has been fixed, presumably on the server side.

The bug was first introduced in macOS 10.14.4 beta. Originally the bug affects any Google accounts with Two-Factor-Authentication (2FA) turned on; Gmail and G-Suite altogether. When macOS 10.14.4 was released, only G-Suite accounts with 2FA were affected. iOS 12.2 was also affected by this bug.

We checked on Saturday morning, March 30, 2019, and found out that the issue was fixed. Assuming that it was fixed on the server side by Google.

A lot of businesses and educational institutions are using G-Suite.

macOS Mojave 10.14.4 breaks G-Suite Account Access in

Add the accidentally deleted “Two-Factor Authentication” bit.

With the release of macOS Mojave 10.14.4, another bug that was originally introduced in 10.14.4 beta. This bug also presents in macOS 10.4.5 beta, iOS 12.2 and iOS 12.3 beta.

Google-hosted G Suite account with Two-Factor Authentication enabled will not be able to log in properly.

When adding a G Suite account you will get a message:

Enter the password for the account “(null)”.
Google requires completing authentication in Safari.

In macOS 10.14.4, to authenticate Google Accounts, Safari opens in Private Browsing Mode.

This bug had been reported multiple times by Apple Developers and Beta testers since the release of macOS 10.14.4 beta 1.

DNS Routing Problem on Wednesday, March 25, 2015.

On Wednesday, March 25, 2015, several DNS servers were having trouble resolving domain names. I first noticed this when visiting Daring Fireball. I was not able to load the site on my iPhone, which is on T-Mobile network. By 4:00 p.m. Pacific Daylight Time, I was still unable to access Daring Fireball on my iPhone. I took the screenshot and tweeted:

If I had to guess, it might be DNS issue with T-Mobile. 

DaringFireball T-Mobile DNS

Two hours later I noticed that I still couldn’t access Daring Fireball. This time I was using the office network; connected through AT&T DSL. We could only get AT&T in this particular area. Then I tweeted to John Gruber:

It seems  is still down. 

Within 3 minutes, Gruber replied:

 No, my site is up. There are internet-wide routing problems, alas: 

Daring Fireball is still down

When I arrived at a colleague’s residence, I was able to to load Daring Fireball site through Verizon FiOS.

Later on, Ben Drago replied:

 It looks like Google’s DNS servers are not resolving . Working OK w/ 

Ben Drago Google DNS has a problem

I tested a few DNS servers and some of them were having the same issues with Google DNS.

At the time of this post, the issue persists on some DNS servers.