Wi-Fi Calling not working? Your probably SIM-swapped and your IMEI is wrong and you don't have HD Voice

When Emily complained of poor call quality I tried enabling Wi-Fi calling on her 13mini -- and got this error message:

Oops! 

We've hit a bump, but we should have it straightened ... ERR0093-WS 

Don't worry, it will never get straightened. This is a crap error message. A pixel page gave me the answer.

Chances are you SIM-Swapped this phone to avoid an infuriating $50 activation fee from AT&T. Turns out that only seems to work, the IMEI in AT&T's system doesn't update. If your plan has HD Voice (most do) it's not working and Wi-Fi (WiFi) calling won't work.

We called AT&T new line support (chat was down) at 611 and after a bit of careful navigating got a human being in "advanced technical support" who updated the IMEI number for us. You may also be asked for the ICCID number. After a phone restart and waiting a few minutes Wi-Fi calling worked. Her voice quality also seemed better.

I did this for a different phone and the first agent said I needed a new SIM -- then (accidentally I think) dropped me. A second agent wanted IMEI and ICCID then told me to restart the phone. It seems to take 3 minutes or so for the change to propagate and enable Wi-Fi calling (and HD Voice by the way).

If you SIM swap to avoid AT&T's #$@$ $50 activation fee you should probably call support or take your phone to an AT&T store to fix the IMEI there.

What's the chance AT&T will ever give up on its activation fee grift? Would be nice for them to just do an eSIM without the fee.

PS

• Business customers can change their own IMEI.
• AT&T's activation page may also allow an IMEI update but you'll probably get charged and it might mess up your account. AT&T used to have a "Wi-Fi calling troubleshooting tool" but it's been removed.

Getting Outlook to export Exchange contacts as vCards (vcf) with proper email addresses for use in macOS

In 2009 I wrote about how it was getting harder to move contact information out of Outlook into something else (like macOS Contacts). I wrote about some options, but that's not what I do now.

Here's what I do (tested in Mojave, which I'm still using because Aperture):

1. Create a simple list Contacts view. I usually only want people so I sort by last name. In a few cases last name of people is blank so I fix that.
2. Now create an empty email. Drag Contacts from Outlook's view into the email body. It has to be to the email, dragging to desktop creates a .msg file. It might fail if you do too many so I distribute 300-400 contacts across 4 separate emails. Outlook creates a vCard file as an attachment. It resolves the email too, so instead of an Outlook x400 (?) you get a proper email address.
3. Send the email to your Mac
4. On the Mac download all attachments. They show as VCF files and macOS renders them quite well.  If they have photos the photos show within the card icon. Spotlight indexes them all. You don't even need to bother with dropping them into Contacts (though that's easy to do, you can drop them into your Contacts Groups (folders)).

It's pretty easy if you know the trick. I've not seen it described anywhere else but I'm sure others know it.

iMessage not synchronizing - your store ID matters too

Based on some issues I've seen with my daughter's devices I think that Apple Message sync will only work when both Apple ID for "iCloud" and Apple ID for "Media & Purchases" agree on both devices.

There's a dependency on "Media & Purchases" Apple ID for Apple Messages, perhaps because it's descended from the Apple messaging apps that predate iCloud.

How to leave Google Apps / G Suite / Google Workspace

UPDATE: As of early May 2022 Google has relented and will allow continued personal use of legacy G Suite domains. You need to login to your domain and then use this URL. (The option is described, a bit obscurely, in a support page).

<background>

It's hard to remember now, but there was a time that geeks had some affection for both Google and Apple (but, TBH, never Microsoft). Those were the glory days my friend.

This year's bitter resentment is brought to you by Google ending free Google Apps services. Back in the glory days Dreamhost bundled these with domains, I picked up 7-9 of them. Two of these Google App domains have been heavily used by my family. They are the core of a wide range of daily things we do, including email addresses association with numerous logins, credentials, passwords, and so on. (But not with Google OAUTH identity services, that is not supported for Google Apps email addresses.)

A few months ago, in early 2022, Google told us that these services, once as permanent as gmail (*cough*, they're coming for you), would become quite expensive. For us the costs to maintain our current setup would be hundreds to thousands of dollars a year. Shortly after this announcement we were told that there *might* be a reprieve, that non-business services would continue. This false-hope was never officially withdrawn, but in May 2022 it has been replaced by a bizarre offer to maybe continue but, like, without email or domain?

Google's very limited online guidance does not review how to exit Google Suite. In email communications they mention a 'suspended state' but do not describe what that means.

So now I have to spend several lovely days in May sitting at my computer trying to salvage our digital identities. We will clearly have to pay for at least one of our domains - principles be damned. Charges begin Aug 1, 2022. </background>

The following is a rough guide to what I will do. Much of this requires knowledge from decades ago that I'm having to refresh.

Considerations and discoveries

1. It's difficult to move IMAP emails between services. IMAP emails can be copied to a local store. In mail. app I've had success dragging and dropping emails from one IMAP inbox to another, but I believe this is fragile and unreliable. You can also copy, see this iCloud example.
2. Local store email is barely supported any more. Mail.app, for example, 
3. My domains are managed by Dreamhost which does provide some classic web services though fewer than it once did.
4. Domain based email forwarding is fragile -- many services including google will reject it. See DKIM notes below.
5. Modern email is both essential and a river of spam and Google has good spam filtering (though it was better once)
6. The knowledge of how to manage DNS settings is more esoteric now than it once was, and Google Search no longer works.
7. My Dreamhost DNS and mail forwarding has lots of old detritus. That's on me!

References related to closing Google Workspace accounts

1. Microsoft on switching to Office 365 - cancel subscription
2. Fastmail also has switching options, but price not much less that Google Workspace
3. Google has not provided any migration guidance.
4. You close your account by canceling the subscription: https://admin.google.com/ac/billing/subscriptions/ then deleting the account (see below).

References for migrating to Dreamhost email services

1. Dreamhost email client configuration
2. The Dreamhost custom MX config panel has 'uses Gmail' management links that take you to Google admin (so not terribly useful but at least can tell what to change.
3. Dreamhost used to support both a mailbox and a forwarding action but you can't do that any more (still works for old settings). Dreamhost uses Roundcube Webmail but has not enabled forwarding in that app. You can use forwarding directly from a domain but I think Google treats emails forwarded this way as spam. (At one time we were supposed to have had quite large storage caps with Dreamhost, but I think email overwhelmed them. Similar to the days our Gmail storage was to be unlimited.)
4. A comment on this post mentioned imap sync for moving email: "For transferring IMAP email, imapsync works well. There's a free version you can download and run on your computer (or on your hosting provider if you have ssh access). It's well documented and relatively easy to get your head around, and is fast and reliable. I’ve not got any affiliation, but someone pointed me to it a couple of years ago, and I’ve since used imapsync to migrate email hosts for a small organisation. Highly recommended."

References for migrating to Apple iCloud+ email

Apple supports custom domains with iCloud+ email including family sharing.

1. You can assign up to 5 domains to a family group and for each domain each member can have up to 3 email addresses.
2. Apple will instruct on how to do DNS settings (there's a bug in the quotes apparently) - there's also a tech note on DNS settings.
3. Useful twitter stream on migration to iCloud
4. Detailed twitter thread on migration - Google takeout mbox, import into Mail, then drag from local to iCloud.

My steps to closing an essentially unused account where I didn't worry about forwarding

1. Go to Google admin console for account.
2. Review how many users exist. (typically one)
3. For that user review email to see if there's anything important, sites, docs, etc. Don't forget google  voice!
4. From Google Admin account cancel your subscription. Now pay close attention so you don't miss the next step - delete your account (https://admin.google.com/ac/companyprofile/accountmanagement)

When you choose to delete account you see:

Now return to Dreamhost

1. Go to DNS for domain and delete the Google CNAME records
2. Go Custom MX controls and Choose "make me regular email". It may take hours for this to work.
3. At this point Dreamhost enables webmail. But I wonder if this actually blocks email forwarding even if you set that up! (The lack of warning doesn't give me a happy feeling about Dreamhost TBH.) So disable webmail. Dreamhost also has a control panel for email forwarding that I think is a disabled feature.) - NEED TO TEST MORE HERE
4. Go to Manage Email and set up a forwarding account as needed. This can take a while. Apple picked up the DNS changes within about 15-30 minutes, but Google took 1-2h. (I wonder if DNS propagation in general works as well as it once did.)
5. Enable DKIM if not already enabled.

Carbon Copy Cloner won't create sparse bundle disk image (grayed out) - Mojave

On Mojave as of May 2022 CCC v 5.whatever wouldn't create a sparse bundle disk image for me when I selected new disk image as destination. The 'action button' was grayed out. 

I switched from the non-admin account I've long used with CCC to an admin account and I was able to do it.

I was able to create disk images using Disk Utility from the non-admin account.

I don't have time or energy to debug further, but if you run into this issue try an admin account.

PS. Once upon a time CCC would just create a disk image if the task referenced one but none was found on the target drive. That's no longer an option, if you are setting up a new drive modern tasks will require the disk image to exist. It's hard to get the 'right' image manually, so you really want CCC to create it for you.

Also, by the way, and unrelated to above, you need to use AFP if you're doing network CCC backup to a sparse bundle disk image.

Universal Clipboard (Handoff, Continuity) not working - Mojave and Monterey, regenerating the authentication token/password

 Recently I've had two issues:

1. Mojave Universal Clipboard stopped working between Mojave and iOS 15.4.1
2. Mojave notes iCloud synced but always showed a spinning activity icon

I found that I could make Universal Clipboard work again by creating or editing a note on my iPhone or on Mojave. Once that synced then UC worked until I rebooted.

If Universal Clipboard isn't working first reboot your devices and confirm connection to WiFi with Bluetooth enabled. Then try toggling Handoff off/on on both devices. Then try:

1. Changing my Mojave location DNS settings from Cloudflare (1.1.1.1) to Google (8.8.8.8). (Based on this post)
2. Toggling Notes iCloud off then on again (restores notes)

Now the spinning is gone, and UC seems to be working.

Update 5/15/2022: UC is back to not working unless I create a note that's synced between iOS and Mojave. Notes doesn't show the skinny activity icon. So this is an open problem.

Update 8/30/2023

Continuity has worked since May 2022 on my Mojave machine, but I'm now switching to a 2023 M2 Air running Monterey. And, of course, the Universal Clipboard didn't work again.

A few hours later my devices notified me that iCloud services would not be available until I reauthenticated. That tedious and annoying process requires entering the iCloud and device passwords; I think it creates a new token/password behind the scenes. After going through this continuity worked again. Signing in and out of iCloud is a common workaround for Continuity issues, I suspect it speeds up regeneration of the new token/password.

It would be nice if Apple improved this process.

PS. Typical things to check when it doesn't work: bluetooth on, devices on same WiFi, etc.

When iCloud Keychain stops working (No more Safari passwords) - Mojave

I'm buying tickets for an event and suddenly there's no password autocomplete in Mojave Safari. Safari Preferences Passwords shows 3-4 entries, but my Apple passwords shows on my iOS devices and my Monterey Air. It's just Mojave that has lost all its iCloud/keychain access.

A good reminder that if you want to use Apple Passwords as a 1Password replacement you need to export a static backup (and this must be automated). The Cloud is where data goes to die.

A found a relevant 2016 Apple Discussion post which would be Mojave era. So I wonder if it's a Mojave bug. The fix there was from "Linc Davis" a "Level 10" with 209K points [1]

Please take these steps to resynchronize the iCloud keychain. Your keychain on iCloud and your other Apple devices won't be affected. Take Step 2 only if Step 1 doesn't solve the problem.

Step 1

Back up all data.

Open the iCloud pane in System Preferences and uncheck the Keychain box. You'll be prompted to delete the local iCloud keychain. Confirm—the data will remain on the servers. Then re-check the box. Follow one of the procedures described in this support article to set up iCloud Keychain on an additional device. Test.

Step 2

If you still have problems, uncheck the Keychain box again and continue.

Triple-click the line below on this page to select it, then copy the text to the Clipboard by pressing the key combination  command-C: 

~/Library/Keychains

In the Finder, select

          Go ▹ Go to Folder...

from the menu bar and paste into the box that opens by pressing command-V. You may not see what you pasted because a line break is included. Press return.

A folder named "Keychains" should open. Inside it is a subfolder with a long name similar to (but not the same as) this:

           421DE5CA-D745-3AC1-91B0-CE5FC0ABA128

The above is only an example; yours will have a different name of the same general form. Drag the subfolder (not the Keychains folder) to the Trash.

Restart the computer, empty the Trash, and re-enable iCloud Keychain.

Toggling Keychain off and on didn't seem to do anything so I figured I'd check in the morning. Before I checked though I did review my passwords in Monterey. For *reasons* (this happens way too often) I had to reenter my iCloud credentials there but I was also asked the usual iCloud keychain questions -- provide passcodes for my other machines.

Then I looked at my Mojave machine and Safari had my passwords again.

Maybe the fix was toggling Keychain and waiting a bit, but I'm suspicious that something happened somewhere in iCloud that required me to do the iCloud Keychain authentication dance from a Mac -- and Mojave couldn't do it.

Again, if you use Apple Passwords as your sole repository you need a non-iCloud backup.

- fn -

[1] No profile info, has participated in 97K threads. Either insane or an Apple staff pseudonym.