Relentless beeping when plug iPhone into MacBook USB port: reset iPhone Location and Privacy

Solved 9/12/2022

I wrote the post below when I used an iPhone 8. When I went to an iPhone 13 it seemed to resolve, but today I tried charging my iPhone from my Air and it was beeping again.

I didn't have time to waste so I switched to a normal charger, but later it occurred to me that there might be a way to reset the trust relationship.

There is, but it's not on the iTunes side. It's on the iPhone side.

If you don't want to trust a computer or other device anymore, change the privacy settings on your iPhone, iPad, or iPod touch. Go to Settings > General > Transfer or Reset [Device] > Reset > Reset Location & Privacy. Now when you connect to formerly trusted computers, the Trust alert will ask you whether you trust that computer. 

I did the reset on my iPhone and next time I plugged it in to my Mojave Air I got the "do you want to trust" dialog. I accepted it and now the phone charges without beeping. I suspect the problem will recur based on the notes below however.

--

When I plug my iPhone 8 into my MacBook Air's USB port I get relentless beeping and the iPhone power icon flashes. Sometimes iTunes throws up a "received an unexpected response" error. I'm on Mojave iTunes.

I figured this was a bad USB cable or bad port or bad connection, but it's both ports and all cables and the phone connection is good. More importantly, I rebooted with no peripherals connected and switched to my admin account. Then every beep was associated with a new iTunes dialog asking me (yet again, and again, this is such a pain) to authenticate. When the dialogs ended the beeping stopped.

Stack Exchange has an article on this, but that's definitely connection issue related. This Apple tech article seems closest; but they also focus on cable issues.

I'm not entirely sure it's not something hardware related on my Air, but I think there's an iTunes component too.

The console shows:

I see: usbmuxsd errors, HandleUSMMuxConnect, iTunes Helper, MobileDeviceUpdater, "no such device". So iTunes is causing the beeps (though the underlying issue could be hardware).

From those clues I found these posts:

• https://discussions.apple.com/thread/251691536: kill usbmuxsd related processes
• https://discussions.apple.com/thread/6611777?answerId=27079314022#27079314022 - a bug in usbmuxsd that Apple may have fixed in later releases
• https://discussions.apple.com/thread/6728641?answerId=6728641021#6728641021 has a discussion:

It's an iTunes 12 bug... Not sure who's responsible for usbmuxd at Apple, but they should be fired! This was extensively discussed and worked out here: itunes 12 will not recognize iphone

All credit to oskapt, who's post detailed the entire issue. The short version is a recent version of usbmuxd has a programming error that leads it to never close any connection. At the same time, it's constantly making new connections too. The end result is this background process actually hits the built-in UNIX limit on open connections by a single process (to prevent bugs like this from ultimately crashing an entire computer), and is blocked by design from functioning after that point. Once usbmuxd fails, iTunes can't see your iOS devices.

The fix is to quit usbmuxd, either via Activity Monitor or Terminal. It will automatically relaunch, and work again until it hits the limit. That thread has several suggestions for automated scripts to run every 24-48 hours to prevent this.

Update 2/20/22: I never solved this problem, but I did get a new phone and the beeping is gone. So either a connection problem with the old iPhone or a bug with the "trust relationship" between iPhone and MacBook.

Update 3/5/2022: In the process of cleaning out old iPhones I tried various iPhones and I tried iPhones that beeped on my Mojave iTunes machine on a different machine. I think it's a bug with establishing a Trust relationship. Probably fixed in later versions of iTunes.

How to remote (push) install a xbox store purchase to xbox from Mac

I couldn't find out how to push an xbox game install to the console with Google searches. Here's what I learned on my own.

1. Go to xbox store.
2. Login
3. From profile picture choose 'My Microsoft Account' 
4. Click Order History
5. Click on appropriate order
6. The bold text below the order number is actually a link. It's evidently a secret
7. Click on the link (Resident Evil ...)
8. You'll the item description in the store. There's a button to push install.

Family sharing screen time bug: a fix for ghost apps

I'm happy to say I actually fixed a bug in the buggiest apple product ever - family sharing screen time.

The "always allowed" app list showed "ghost apps" -- left over apps from old versions of iOS like Find Friend. They appeared with a generic icon.

Removing my son from the family then adding him back in removed the ghost apps.

One bug down, dozens remain.

Update: Nope, the fix was transitory. Ghost apps back again. Screen Time is such a cluster.

Update: Ok, this might be the real fix. His Apple ID had 3 associated devices -- and iPad, and iPhone and a macOS user account on an old machine running maybe Sierra.  I removed the obsolete macOS relationship from his Apple ID on the web site, but it had to be remove again on his iPad.

Apple Mac App Store: "Unable to download item. Please try again later": The problem may be that you are not the purchaser.

I was logged into my admin account on my daughter's Big Sur Air and saw the usual nag to update Apps. When I tried though I got  "Unable to download item. Please try again later."

It never works to try again later. This is a typically useless Apple error message produced when something has gone wrong with their complex FairPlay DRM authentication. There are a range of fixes that Google shows but, even after I figured out the bug (a design fail of this sort is a bug) I couldn't find anything that explained the fix [1]. So here you go!

The problem happens on a multi-user Mac with multiple admins installing software using different Apple Store Apple IDs. It might also require that automatic updates are not enabled and it might require that Family Sharing is enabled.

Every admin gets notification of a pending update, but only the FairPlay determined DRM owner can actually successfully do the update. Other admins who try get the useless error message.

The fix on Big Sur's Mac App Store is to cast your gaze down to the bottom left corner of the App Store window. There you see a user name. Click on the user name and you'll see an "Account" screen. At the top of the "Account" screen is a "Purchased by" drop down with the user name of every family sharing member [1]. Switch between Accounts here to find who has the "update" for the problem app. Then update. Continue until all apps are updated.

It will be interesting to see if this is handled better in Monterey. I can imagine several potential fixes!

[1] As every Old will repeat ad nauseam, the Google web was much better 20 years ago.

How to mitigate SMS spam in iOS 15: filter unknown AND disable notifications for unknown senders

I do not understand why it took Apple so long to do basic management of text message (SMS) spam. I don't understand why the solution appeared over two releases. I don't get why the implementation is so obscure. And I don't get why I had to write this; even knowing the two necessary settings I can't find a good article on it. Apple's own documentation doesn't mention disabling notifications.

Anyway, as of iOS 15 you can finally turn off notifications for SMS sent from an unrecognized number. This is in addition to iOS 14 enabling sorting of unrecognized number SMS into a separate tab. (I think iOS 13 you could only filter iMessages, which is basically useless.)

First enable "Filter Unknown Senders". Unrecognized SMS messages go into a separate tab.

Second turn off notifications for unknown senders

You still get SMS spam but it doesn't interrupt you and it's hidden away.

Using Apple Locator devices (AirTags) with an older iPhone

AirTags will work with older iPhones but things are a little different. 

The trick is that they work by Bluetooth with a range of about 20 to 30 feet. The last known location showing in Find My tells you roughly where they are. The next step is to try activating the sound feature. If you see that it's working you know the lost AirTag is within about 20 to 30 feet. If it doesn't work keep moving until you start to see it working. Now you can try to listen for the sound. It can be faint. It's also short-lived. You may have to keep tapping the sound icon. Eventually you'll find the missing AirTag.

Safari on US Bank: "our system is not cooperating"

For the last few days when my wife entered https://onlinebanking.usbank.com into M1 Big Sur 10.4.2 and 10.5.1 Safari she immediately received the error message: 

Our system is not cooperating

Try connecting again 

She can access the US Bank site from a different user account using Safari on her machine. She can also get to it from from Chrome in her account. Edge didn't work at all -- it just hung.

I tried deleting Safari Cache and deleting all US Bank associated cookies/data. No change. I tried a Private window - no luck. I tried changing DNS provider - no help. I tried removing ALL Safari cache and cookie and other data - no change. I tried with our 1Password extension enabled and disabled.

So for now she's using Chrome. There's something wrong with either Safari or something deeper in her user profile but I don't know where to look next.