Unable to update date of birth associated with an Apple ID: "... could not be changed because of a server error"

You can't change the date of birth or family relationship of an Apple ID with a calculated age of less than 13 years old. Otherwise it's supposed to be possible to change the date of birth associated with an Apple ID. I've done it before (for good reasons).

Recently I decided to get #2 child an Apple credit card. Since banks take birth dates seriously I decided I needed to correct his before applying. It didn't work!

This is what his birthday looks like on his Apple ID web page (same as in his iOS devices):

When I edit it to 4/2/1999 I get this message as expected:

The next step is an email sent to the me.com (we're old customers, pre-icloud) associated with my Apple ID:

Can you see what's weird in this email? It says the change will convert his account to a child account. But the current date makes him 17, the correction makes him 22. The email should say it's being converted to an adult account.

When I click on "approve request" I get:

Cannot change date of birth.

The date of birth for ___ could not be changed because of a server error. Try again.

I started an Apple Chat Support ticket on this a week ago. After the usual back and forth I was escalated twice and ended up with a senior advisor (not sure of his title).  After a bit of work and repetition I was told a ticket had been sent to engineering to fix the birth date and I'd hear back the next day.

It's been a week. I've not heard back. I'll try a chat again tomorrow. Fortunately I have my original ticket number.

I suspect his account entry is somehow corrupted and possibly mixed with another account. Otherwise I wonder if this is a side-effect of Apple introducing family credit cards; maybe once I got an Apple credit card all the family birth dates were locked as a side-effect.

It's not a common problem though, I found one similar report from someone trying to convert an adult to child account.

This is going to be a painful slog with no certainty of success.

UPDATE 7/13/2021: After hearing nothing back I called again and was again escalated from chat support to phone support to "senior advisor". Senior advisor said engineering had responded and said it was not actually possible to change date of birth on a child account. I believe that is wrong, it contradicts Apple's documentation saying it should be possible to change for over 13. I have asked that it be reescalated and attach the tech support ref: HT204164.

I reserved a time to call back in 3 days and was told I'd get a link to enable a direct call to a senior advisor.

PS. Related Apple Discussion.

Update 7/24/2021: Support didn't call back on the date they'd promised. There's still a server error. As noted above Support seemed unaware of the contents of HT204164. 

I'm going to have to give up on fixing this for now. I'll try again in a few months, maybe by then Apple will know how to fix the problem. I suspect it's something in their database design that will require serious work to fix. I also suspect their support team is dealing with post-COVID stress syndrome.

Update 1/1/2023: Today I was able to change his birth date without issues. Based on the original birth date he would be 19yo now, so an adult.

Apple Card for Families: non-owners have a $250/transaction limit but no cap on total spend

Turns out when you enable Apple Card for a non-owner family member they have a max transaction limit of $250 but no total cap (can spend to owner credit limit). I thought the transaction limit would be much higher AND I thought there would be a total spending cap.

It's less useful than I expected.

Update: You can set a number for total spend notification and you can lock at any time. The $250 limit per transaction is a hard maximum though. Too low.

Disk Utility First Aid problem in Mojave: Working around the Disk Locked bug

If you've used Disk Utility in Mojave APFS you know it's become much more complex than HPFS days. Recently I tried running it from the Recovery start and got a Disk Locked error that said I needed to wipe the drive and reformat. I couldn't find any fix for this on Google.

This did fix it:

1. I rebooted into macOS and ran Disk Utility from there.

2. I rebooted back into the Recovery mode and this time the disk was not locked.

I don't know what did the trick. Maybe all I had to do was go back into normal boot and then back to Disk Utility, but I think I tried that and it wasn't sufficient. I had to run Disk Utility from macOS.

I suspect a safe boot might have worked too. Anyway, the point is, if you're stuck and you find this post it's fixable.

PS. This isn't about mounting an encrypted disk.

Apple ID problem: sharing iTunes Apple ID in two factor world means authentication requests go to one of many possible devices

In the old days, before family sharing, families shared purchases by sharing an iTunes Apple ID while using their own Apple ID for me.com services.

Now that we've moved to 2FA for iTunes Apple ID there's a new problem with this.

Authentication requests go to one of the devices that uses that shared iTunes Apple ID. Just one. Usually the wrong one.

Apps for mapping out bike rides

I recently asked a MN bicycling group what apps they use to layout trail maps. This is the list they gave me:

Google Maps

I've long used this. Main frustrations are limited number of waypoints, inability to draw segments when Google doesn't know something, and lastly that Google's bike trail knowledge is decaying.

RideWithGPS

Designed for planning routes and had the most support. It can sync to Wahoo and Strava. Premium $10/month, I don't know if you can do a month and then stop it. The free tier is said to be best of the free options.

Komoot

Said to be same platform as RideWithGPS. If you pay you can divide a tour into days and see an integrated forecast.

Strava

I think this requires the non-free tiers.

Plot a Route

This has a pretty complicated web interface. It's ad supported by only $25 US a year to eliminate them.

Also mentioned: MapMyRide and Garmin Connect.

Update: So far I don't like any of 'em. Strava was least useful. RideWithGPS is best so far but need to try others.

The panicky M1 MacBook Air known as Crashy

Nine weeks ago I replaced Emily's 9yo 11" Air with a 2021 M1 Air. Shortly after we passed the return date I realized I'd made a bad decision. The M1 Air panicked so often that it's forever known to us as "Crashy" the M1 Air. On some days Emily would see a spontaneous restart several times a day.

I don't think it's a hardware problem; among other things it's passed repeated hardware tests.  I suspect using Migration Assistant to move from High Sierra didn't help, but I don't think that's all of it. There's something bizarre with residual parental controls on my son's account that I can't seem to clear -- but Apple's parental controls/Screen Time have been horked for my family for years across iOS and now macOS. I don't think that's all of it.

I think it's mostly a bug with Fast User Switching and maybe Chrome/Google Software. We know that Fast User Switching can kill Mail.app spotlight search until corespotlightd is restarted, so we know some defect is leaking across user sessions. We also know that Fast User Switching is disabled by default on Big Sur, which suggests Apple is worried about it. (Maybe the weird Screen Time behavior is playing a role.)

So after doing every possible fix short of wiping the drive and reinstalling data from backup I removed every trace of Chrome and Google software [1] and I turned off FUS. Since then we've had no more crashes.

Eventually I'm going to restore FUS. This is a multi-user machine and we want it to work properly. When I do that I'll make every user admin because Big Sur does not display a Panic report to non-admin users -- then look for a log report. If Crashy stays up then the finger points to Chrome.

I really wish we'd bought an Intel Air. The 2020 Intel Air was basically perfect.

[1] My son used Chrome, Emily is Safari only. After one crash Emily was asked if she wanted to restart Chrome -- but she wasn't using Chrome. Suspicious for more leakage across user sessions.

PS. At one point I saw a very long thread on Apple Discussions about M1's crashing. It vanished. Here's a shorter thread and another.

Update 4/19/2021: Removing Chrome and disabling Fast User Switching eliminated the panics. We are doing ok without both so we aren't doing further testing. I don't miss Chrome and Emily and my son don't mind logging out.

Update 6/18/2021: By Big Sur 11.4 Crashy was fixed. We're keeping the name however. Fast User Switching is on but I never did reinstall Chrome. We bought our M1 Air around Jan 20, 2021 and 11.4 came out 5/24/2021, so it took five months for Apple to fix the damned thing. Eclectic Company wrote an article about M1 instability under Big Sur.

Big Sur bug: Mail Search (corespotlightd) fails on multi-user machine after a user logs out

We are indebted to GanawaGangunawa for figuring out why Mail search was failing on Emily's M1 MacBook Air (known to our family as "Crashy" [1]). It's a Big Sur bug (though I think it happened in some Catalina environments) that hits multi-user machines.

In our case Ben and Emily both have non-admin accounts on her M1 Air running Big Sur 11.2.1 with fast user switching enabled. When Ben logs out Emily's Mail search stops working. There's no error message, but search does nothing and Smart Folders are inactive.

The fix is to kill corespotlightd.

I created an AppleScript with the contents: 

do shell script "killall -9 corespotlightd"

I saved it as an application and put it on Emily's dock. Two clicks fixes her Mail search until Apple fixes the bug.

[1] When we first got the M1 Air it crashed (spontaneous restart) every few hours. Reinstalling Big Sur meant it crashed every few days, with Big Sur 11.2 it didn't crash, with 11.2.1 it restarts every week or so. I suspect a firmware/OS mismatch in the factory was the initial problem and that for the rest that Big Sur/M1 are not quite stable yet. I almost returned Crashy in the 2 week return window but it seems just stable enough. Good chance future OS updates will fix. It does pass hardware test.