Monterey orphaned our physical podcast files. What can we do with them?

Podcasts started out as distributing MP3 files; back then iTunes was a great podcast app (and music and audiobooks, and voice memos and more -- it was a glorious app before the fall.)

Over the years Podcasts really shifted to streaming, listen once, don't keep. Then, somewhere post Mojave (Monterey) Apple orphaned the physical podcast files stored in iTunes. The Finder shows physical files in your media library but neither Music.app or Podcast.app can browse them. Music. app's browser Get Info still shows the media type dropdown, but there's only one type! (Music)

If you click on a podcast file iTunes will play it and import the file into the media library where it has media type Music but genre podcast.

So the fix is:

1. Move Podcast folder out of media library

2. Reimport all podcast as music.

3. For genre podcast multi-edit to make more like podcasts. You use macOS Music.app column browse to see all with genre "podcast", select all then hit cmd-I. You'll see a prompt asking if you wish to multi-edit (yes). Then in Options select: 'remember playback position' 'skip when shuffling'. I think this operation may fail if a file is being uploaded to Apple Music (at least I get to burn GB of Apple Storage!) so let uploads complete if it doesn't work.

Reference Stack Exchange.

PS. Voice Memos are supposed to have a migrate path, but that didn't show for me.

Using Apple's USB-C to T2 adapter: not for video but still good

My 2015 MacBook Air uses Thunderbolt 2; it was connected to an elgato T2 hub (reliable for over 6 years) with a few USB and Firewire 800 peripherals. That Air is in for a battery swap after which it will be primarily an Aperture machine with some portable use. At the moment I'm sharing my son's 2020 Air; there may be a Pro or M2 Air ahead.

To reduce costs and hassles I decided to try Apple's T3/USB-C to T2 adapter. It costs around $45. Everything works for now -- except my external HDMI monitor. It flickers on and off. I might play with it a bit but for now I have it connected directly to the laptop via a compact Anker USB-C hub [1]. Apple tells us that "This adapter does not support DisplayPort displays...". I wonder if the HDMI display connected to a Hub with a DisplayPort/T2 cables affected by this limitation.

Overall it's worth the money, even though I'm likely to switch everything to a USB-C or better hub eventually. The single remaining Firewire 800 device can be retired.

- fn -

[1] When I disconnect the laptop I have to pull two cables! Oldness helps with the indignity.

Migration Assistant from Mojave to Monterey is mostly a train wreck

Ugh. Almost nothing went well with doing migration assistant from Mojave to Monterey. I had to trash my Photo Library and recreate a new system photo library to repopulate from iCloud. I had to turn off iCloud Drive, delete the Archive versions, then turn it back on again. A bug with deleting user accounts was unrelated but took up an hour or two.

Kind of what I'm used to with Apple to be honest.

I probably would have been better off to migrate my documents folder and my mail files manually, then recreate the rest.

Unrelated but also sad: I hoped Apple's T2 to USB-C cable would let me continue to use my T2 hub and related peripherals (some Firewire 800!) but it's unstable in early testing.

Can't empty trash because VoiceTrigger is in use: It's a macOS system integrity bug

If you delete a user account in some versions of macOS (Monterey in my case) where the user account was created in certain earlier versions of macOS you will run into a System Integrity bug.

There's a folder called VoiceTrigger that in the deleted user account that is protected by System Integrity (~/Library/VoiceTrigger/SAT. ) It's located in the User's Library, so it should not be SIP protected. (In Monterey there's nothing there called SAT).

I'm guessing the bug is that it was never supposed to be SIP protected but in some version of macOS it was. Maybe Big Sur. (There's a second bug because the error message is incorrect. The problem isn't that the file is in use, the problem is it's SIP protected.)

I found the fix in in r/MacOS - disable SIP, delete, re-enable SIP:

Disable System Integrity Protection

1. Click the  menu.

2. Select Restart...

3. Hold down Command-R to boot into the Recovery System.

4. Click the Utilities menu and select Terminal.

5. Type csrutil disable and press return.

6. Close the Terminal app.

7. Click the  menu and select Restart....

Login normally, then Empty the Trash Can

Re-Enable System Integrity Protection

1. Click the  menu.

2. Select Restart...

3. Hold down Command-R to boot into the Recovery System.

4. Click the Utilities menu and select Terminal.

5. Type csrutil enable and press return.

6. Close the Terminal app.

7. Click the  menu and select Restart....

Things other's suggested that didn't work:

1. Terminal: sudo rm -rf ~/.Trash/*

Note you need to be admin to do this. There's a way to escalate non-admin to use sudo but I think Apple has basically given up on non-admin user accounts.

2. Turn off iCloud document sync.

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.