How to Back Up an iPhone or iPad with Your Mac Running Catalina

/in , , , , , /by

One of the most significant changes in macOS 10.15 Catalina was the breakup of the long-standing iTunes app into separate Music, Podcasts, and TV apps. But what about backing up iOS devices, which you also used to do in iTunes? In Catalina, Apple moved this function into the Finder. So if you’ve upgraded to Catalina or bought a new Mac that comes with Catalina, here’s how you can continue to back up your iPhone, iPad, or iPod touch in the Finder.

One note first. If you haven’t been using iTunes to back up, manage, and sync media to your device from your Mac all along, we don’t recommend that you start now. Although Apple continues to make these capabilities available for those who need or prefer them, the company focuses most of its efforts on cloud-based services like iCloud Backup, Apple Music, and iCloud Photos. Plus, many of Apple’s apps, like Books, Calendar, Contacts, Podcasts, and TV, can sync their data among all your Apple devices through iCloud. We’re focusing on backup here—for more details about manually syncing media to your iOS device, check out Take Control of macOS Media Apps, by Kirk McElhearn.

Initial Connections

As when you were using iTunes, you’ll need to connect your iOS device to the Mac with a USB cable, either a USB-to-Lightning cable for most devices or a USB-C cable for recent iPad Pro models. When you plug your device into your Mac, it should appear in a Finder window’s sidebar. However, it may not show unless you open Finder > Preferences > Sidebar and select CDs, DVDs, and iOS Devices. (And if it still doesn’t appear, restart your Mac.)

The first time you connect an iOS device to your Mac, you’ll need to establish a trust link between the two devices. That requires that you select the iOS device in a Finder window’s sidebar, click a Trust button that appears, click Trust again on the device itself, and then enter the device’s passcode. This is all very sensible since it prevents someone from stealing your iPhone and connecting to their Mac to read its contents.

Back Up Your Device

Once you’ve jumped through the necessary security hoops, select your device in a Finder window sidebar to view the General screen, which has an interface that’s eerily reminiscent of iTunes. Here’s where you’ll find backup controls, along with a button that lets you update your device’s version of iOS and (not shown) a variety of other general options. Again, we’re focusing on backup here.

You have two choices: storing the backups on iCloud or keeping them on your Mac. Apple has more information comparing the two, but here are the basics:

  • iCloud backups: Assuming you have enough (or are willing to buy more) storage space in iCloud, select “Back up your most important data on your iPhone to iCloud.” Backing up to iCloud is the best option because it automatically happens once per day whenever the device is connected to power, locked, and on Wi-Fi—for us, that usually means during an overnight charge. Plus, if your Mac has a relatively small SSD, you may not have space to store the backups for a large iOS device. iCloud backups are highly secure and reliable, but there are those who don’t want to pay for sufficient iCloud space or don’t want their data in iCloud.
  • Local backups: If you prefer, select “Back up all of the data on your iPhone to this Mac.” Be sure to select “Encrypt local backup.” Otherwise, the backup won’t include saved passwords, Wi-Fi settings, browsing history, Health data, and your call history. And anyone breaking into your Mac could access everything else in your iPhone backup! When you select “Encrypt local backup,” you’ll be asked for a password—make sure it’s one you won’t forget.

If you’re going with iCloud backups, you’re done—backups will happen automatically. For local backups, however, click Back Up Now to initiate a backup. Backups can take quite some time—a circular progress indicator replaces the eject button next to the device’s name in the sidebar. That’s a hint that you shouldn’t unplug the device while it’s backing up.

In fact, you don’t have to choose between iCloud and local backups. Nothing prevents you from leaving the default set to iCloud (this mirrors the setting on the device itself in Settings > Your Name > iCloud > iCloud Backup) but occasionally connecting your device to your Mac and clicking Back Up Now to make a secondary local backup, just in case. That would be a sensible thing to do before switching devices or intentionally erasing the device for some reason.

Since iOS device backups can be quite large—up to hundreds of gigabytes—you may need to recover space used by backups for devices you no longer have. Plus, if you switch to iCloud backups at some point, there’s little point in devoting many gigabytes of storage to obsolete backups.

Click Manage Backups to see a list of backups. To delete one, select it and click Delete Backup. You can also Control-click any backup to delete it, archive it (which prevents it from being overwritten by future backups), or show it in the Finder. That last option is useful for determining the size of the folder containing the backup—select it in the Finder and choose File > Get Info.

Finally, backups are useful only if you can restore from them in case of problems. To do that from the Finder in Catalina, connect your iOS device and click Restore Backup. You can choose which backup to restore, if necessary, and enter the password you set for an encrypted backup. Restoring will likely take quite some time, depending on how much data needs to be transferred.

We’ll leave you with one last thought. An eject button appears next to your iOS device in the Finder window’s sidebar. You can click it to disconnect the device or, if there’s no other progress indicator there, just unplug the device.

(Featured image components by Apple)

Here’s How the Exposure Notification System from Apple and Google Protects Your Privacy

/in , , , , , /by

Apple recently released iOS 13.5, incorporating a new Exposure Notification API in response to the global COVID-19 pandemic. We’ve seen a few people freaking out about this, but seriously, calm down, folks. At best, the Exposure Notification API could lower contact tracing costs, reduce the spread of COVID-19, prevent life-changing health consequences, and save lives. At worst, it won’t prove particularly effective. In neither case does it pose any threat to personal privacy.

Why have Apple and Google—two companies that normally compete tooth and nail—formed this unprecedented partnership? Contact tracing is one of the key techniques employed by public health authorities in slowing the spread of COVID-19. It involves gathering information from an infected person about those they’ve been in contact with, enabling authorities to learn who might have been the source of the infection and who they may have infected. It’s a slow, laborious, and error-prone process—do you know or even remember all the people you’ve come in contact with over the past few weeks?—but it’s helpful nonetheless.

To speed up this process and make it more accurate, Apple and Google are building exposure notification capabilities into their respective smartphone operating systems. A large percentage of the population carries a smartphone running either iOS or Android, and since these phones have the capability to detect when other phones are in their vicinity via Bluetooth, Apple and Google realized they could use technology to alert people when they had been exposed to a person who later tests positive for COVID-19.

Their solution comes in two phases. In the first phase, Apple and Google are releasing the Exposure Notification API, and that’s what just happened with iOS 13.5. This API, or application programming interface, allows apps written by public health authorities to work across both iOS and Android devices, something that’s never been possible before. The first key fact to understand is that only public health authorities will be allowed to write apps that leverage the Exposure Notification API. It cannot be incorporated into sketchy social media apps.

Unfortunately, it seems likely that many people will never learn about or download those apps. So in the second phase, Apple and Google will build the exposure notification technology directly into iOS and Android, so it can work without a public health authority app being installed.

The second key fact to understand is the entire system is opt-in. You must explicitly consent to the terms and conditions of the program before it becomes active on your phone. That’s true whether you get an app in the first phase or rely on the integration in the second phase. And, of course, if you change your mind, you can always turn it off in the app or the operating system settings.

How does it work? Apple and Google have developed an ingenious approach that ensures that those who opt-in to the technology can use it without worrying about privacy violations.

Your phone creates a Bluetooth beacon with a unique ID derived from a randomly generated diagnosis encryption key. The system generates a fresh diagnosis key every 24 hours and stores it on your phone for 14 days, deleting all older keys. Plus, the unique Bluetooth beacon ID that your phone broadcasts to other phones in your vicinity changes every 15 minutes. Similarly, your phone reads the unique IDs from nearby phones and stores them locally. This approach ensures privacy in three important ways:

  • No personal information is shared. The ID is based on a random encryption key and changes constantly, so there’s no way it could be traced back to your phone, much less to you personally.
  • No location information is stored. The only data that’s generated and transferred between the phones are these unique IDs. The system does not record or share location information, and Apple and Google have said they won’t approve any public health authority app that uses this system and also records location separately.
  • No data is uploaded unless you test positive. As long as you remain uninfected by COVID-19, no data from your phone is uploaded to the Apple- and Google-controlled servers.

What happens if you test positive for COVID-19? (Sorry!) In that case, you would need to use a public health authority app to report your test results. You’ll likely have to enter a code or other piece of information to validate the diagnosis—a requirement necessary to prevent fake reporting.

When the app confirms your diagnosis, it triggers your phone to upload up to the last 14 days of diagnosis encryption keys—remember, these are just the keys from which the IDs are derived, not the IDs themselves—to the servers. Fewer days might be uploaded depending on when the exposure could have occurred.

All the phones enrolled in the system constantly download these diagnosis keys from devices of infected people. Then they perform cryptographic operations to see if those keys match any of the locally stored Bluetooth IDs captured during the period covered by the key. If there’s a match, that means you were in proximity to an infected person, and the system generates a notification with information about the day the exposure happened, how long it lasted, and the Bluetooth signal strength (which can indicate how close you were). A public health authority app will provide detailed instructions on how to proceed; if someone doesn’t have the app yet, the smartphone operating system will explain how to get it. Additional privacy protections are built into these steps:

  • No one is forced to report a positive diagnosis. Just as you have to opt-in to the proximity ID sharing, you must explicitly choose to share your positive diagnosis. Not sharing puts others, including your loved ones, at risk, but that’s your decision to make.
  • Shared diagnosis keys cannot identify you. The information that your phone uploads in the case of a positive diagnosis is limited to—at most—14 encryption keys. Those keys, which are then shared with others’ phones, contain no personal or location information.
  • The matching process takes place only on users’ phones. Since the diagnosis keys and the derived IDs only meet on individual phones, there’s no way Apple, Google, or any government agency could match them up to establish a relationship.
  • The notification information is too general to identify individuals. In most cases, there will be no way to connect an exposure notification back to an individual. Obviously, if you were in contact with only one or two people on a relevant day, that’s less true, but in such a situation, they’re likely known to you anyway.

Finally, Apple and Google have said they’ll disable the exposure notification system on a regional basis when it is no longer needed.

We apologize if that sounds complicated. It is, and necessarily so, because Apple and Google have put a tremendous amount of thought and technical and cryptographic experience into developing this exposure notification system. They are the preeminent technology companies on the planet, and their knowledge, skills, and expertise are as good as it gets. A simpler system—and, unfortunately, we’ll probably see plenty of other apps that won’t be as well designed—would likely have loopholes or could be exploited in unanticipated ways.

You can read more about the system from Apple and Google, including a FAQ and the technical specifications.

Our take? We’ll be installing the necessary app and participating in this exposure notification system. It’s the least we can do to help keep our loved ones and others in our communities safe. In a pandemic, we all have to work to help others.

(Featured image based on an original by Dennis Kummer on Unsplash)

Got a Mac Laptop? Here’s What You Need to Know about Battery Health Management in Catalina

/in , , , , , /by

We all want Mac laptops that can run for days on a single charge and never need their batteries serviced. Sadly, we’re always going to be disappointed. Battery and power management technologies continually improve, but those improvements are matched by more powerful processors and smaller designs with less room for battery cells. And, because physics is a harsh mistress, current lithium-ion batteries are always going to age chemically, so they hold less of a charge over time.

In the just-released macOS 10.15.5 Catalina, Apple has introduced a new battery health management feature that promises to increase the effective lifespan of the batteries in recent Mac laptops. It does this by monitoring the battery’s temperature and charging patterns and, in all likelihood, reducing the maximum level to which it will charge the battery.

You see the problem. While battery health management can extend your battery’s overall lifespan, it will likely also reduce your everyday runtime before you need to charge. It’s too soon to know the full extent of this tradeoff, and we suspect that it may be impossible to determine, given that everyone uses their Macs differently.

It’s worth noting that this battery health management feature appears only for those running macOS 10.15.5 or later, and only then if the Mac in question is a laptop with Thunderbolt 3 ports. In essence, then, it’s available only on MacBook Pro models introduced in 2016 or later, and MacBook Air models introduced in 2018 and later. (The Thunderbolt 3 port requirement is merely a shorthand way for Apple to indicate “recent Mac laptops.”)

So, if you have a supported laptop and you’re running macOS 10.15.5, what should you do? We see three scenarios:

  • Favor lifespan: If you seldom run your laptop’s battery down to the electronic fumes because it’s easy for you to plug in whenever you need to charge, leave battery health management enabled. That will preserve the battery’s overall lifespan to the extent possible.
  • Favor runtime: For those who need to eke every last bit of power from their batteries, disable battery health management. You might have to replace the battery sooner, but you’ll get more runtime in everyday usage.
  • Switch as needed: Many people need the longest possible runtime only occasionally, such as on long flights with no under-seat power. In such situations, switch battery health management off for the flight and back on when you return to normal usage patterns.

Switching is easy, but Apple buries it deeply enough that it’s clear that the company doesn’t think most users should be disabling it regularly. Open System Preferences > Energy Saver, click the Battery Health button at the bottom, and in the dialog that appears, uncheck Battery Health Management and click OK. You’ll be prompted to make sure you know what you’re doing; click Turn Off to finish the job.

One final note. The reduced maximum capacity with battery health management enabled may have an undesirable side effect—a recommendation from the Battery Status menu’s health indicator that you need to replace your battery. To check your battery’s health, hold the Option key down and click the Battery Status icon on the menu bar. At the top of the menu, next to Condition, you’ll see either Normal or Service Recommended. (In previous versions of macOS, it could have said Replace Soon, Replace Now, or Service Battery.)

Regardless of the term, anything but Normal indicates that your battery is holding less of a charge than when it was new. If you see that message and you aren’t getting enough runtime for your needs, get the battery evaluated at an Apple-authorized service provider or Apple Store.

(Featured image by Thomas Kelley on Unsplash)