Continuity Camera not working on macOS Tahoe: the reports, the pattern, and what actually helps

When Continuity Camera stops working, run the short checks first: both devices signed in to the same Apple Account with two factor authentication, Bluetooth and Wi-Fi on, the iPhone unlocked recently and nearby, and neither device sharing its connection. Then try a cable, because the macOS Tahoe reports below share one shape: USB works while wireless fails.

Every claim about the Tahoe behavior below is a public report, linked and dated, and Apple's own guidance is cited to Apple. Where the cause is inferred, the sentence says so.

Continuity Camera quick checks, in order

Apple's Continuity Camera support page, last updated in May 2026, lists the conditions the feature needs before any troubleshooting is worth your time. Both devices on the same Apple Account with two factor authentication. Bluetooth and Wi-Fi on, on both. The iPhone near the Mac, an iPhone XR or later on iOS 16 or later, and the Mac on macOS Ventura or later. The iPhone must not be sharing its cellular connection, the Mac must not be sharing its internet connection, and for wireless use the Mac cannot be running AirPlay or Sidecar at the same time.

The feature's own switch lives on the phone: Settings, General, AirPlay and Continuity, called AirPlay and Handoff on older versions, then Continuity Camera. Flip it off and on. Apple's escalation list when the phone still refuses to appear: install the latest updates on both devices and on the video app itself, take the iPhone off its lock screen and lock it again, plug the iPhone into the Mac, and restart both. That plug it in step is doing more work in 2026 than the page lets on, which is the rest of this article.

The macOS Tahoe reports: wireless fails while USB works

Days after macOS 26 shipped, a report on Apple's Support Communities, dated 23 September 2025, described a Mac Studio with an M2 Ultra on macOS Tahoe 26.0 and an iPhone 15 Pro Max on iOS 26.0 that had worked as a camera for years. After the update, the iPhone stopped appearing wirelessly in FaceTime, Zoom, Photo Booth or the System Report camera list. Over a USB cable it appeared immediately, every time.

The strange part is what brought wireless back: plugging an unrelated external USB camera into the Mac. With the webcam attached, the iPhone appeared wirelessly again in every app. Unplug the webcam and the iPhone dropped off with it, unless a video app already using the iPhone stayed open, in which case it kept working until that app quit. A community moderator acknowledged the report the same day and pointed the author to Apple's product feedback channel; the thread records no fix.

A second report from 16 December 2025 repeats the shape on different hardware: an M1 Mac mini on macOS 26.2 with an iPhone 16 Pro Max, where Continuity Camera worked only while an old Logitech USB webcam was plugged in, kept working after unplugging it, and broke again at the next restart. Seven other users marked themselves affected before the thread closed, unresolved.

Treat these as what they are: user reports, consistent with each other, not an Apple advisory. Apple's documentation requires no external camera for Continuity Camera, and that mismatch between the documented behavior and the reported one is exactly what makes this read as a bug rather than a rule.

Macs without a built in camera: the reboot trap

A thread on Apple's developer forums pins down the cleanest version of the pattern, on a Mac Studio with no camera plugged in. After a normal reboot, System Information's camera section reports that no video capture devices were found, and Continuity Camera is absent from every app. Plug in any standard UVC webcam and camera services come up: the webcam appears, and so does the iPhone. Unplug the webcam and Continuity Camera keeps working, until the next reboot starts the cycle again. In January 2026, an Apple Developer Technical Support engineer asked the reporter for their Feedback Assistant bug number to confirm it was routed correctly, which is engagement, though not a fix.

The inference, stated as inference: camera discovery on these systems appears not to start until at least one physical camera has shown up since boot, and Continuity Camera rides on that discovery rather than triggering it. It would explain why the reports cluster on the Mac Studio and Mac mini, the Macs with no built in camera, while a MacBook, which always boots with one, never lacks a first camera to wake the machinery.

How to tell whether you are in the reboot trap

Two observations separate this failure from every other Continuity Camera problem, and both take under a minute.

First, ask the system what cameras it believes exist: open System Information from the Utilities folder, or hold Option and choose System Information from the Apple menu, and read the Camera section. The developer forum report above is built on exactly this check. A Mac in the trap reports that no video capture devices were found, which is a different statement from your iPhone being missing: it means the camera machinery below every app has nothing at all.

Second, plug in any USB camera you own and watch that same section change. If the webcam appears and the iPhone appears beside it, you are looking at the reported Tahoe pattern rather than a pairing problem, and the workarounds below are your realistic options. If the webcam appears and the iPhone still does not, the problem is the pairing itself, and Apple's quick checks at the top of this page are the right list to walk again.

The cable fallback, done right

A cable takes Wi-Fi and Bluetooth out of the question entirely, and it is the one path the reports describe as working every time. Apple's requirement for USB use is that the iPhone trusts the Mac: plug it in, and if a Trust This Computer prompt appears on the phone, accept it and enter the passcode. The iPhone then shows up in the same camera pickers the wireless path would have used, which are set per app, not once for the system.

Workarounds the reports say hold up

Each of these traces to the threads above or to Apple's own steps, in rough order of dignity. Use the cable and trust the Mac. Keep any cheap UVC webcam plugged in, which is inelegant and, per two separate threads, effective. On a desk Mac, plug a webcam in once after each boot, then unplug it, and Continuity Camera survives until the next reboot. If wireless is working and you need to unplug the webcam that enabled it, leave the video app open, since one report describes the iPhone surviving exactly as long as the app that was using it. Toggle Continuity Camera off and on from the phone's settings, unlock and relock the phone, and restart both devices, which are Apple's listed steps. And file the bug through Feedback Assistant or Apple's product feedback page: a DTS engineer asking for a bug number in one of these threads means filed reports are being read.

What a self view app can and cannot do here

A camera that silently fails to enumerate is invisible right up until the meeting starts, which is the moment you can least afford to learn about it. This is the one part of the problem a mirror app genuinely helps with. Preen asks macOS for four kinds of camera, built in, external, Continuity and Desk View, and shows them grouped and named, so one click tells you whether your iPhone made it into the system's camera list at all, and whether the feed behind it is live rather than a stale label. That check takes seconds and works as a pre meeting habit rather than a diagnosis after the fact.

What no mirror app can do, Preen included, is make the iPhone appear. Device discovery happens in macOS, below every app, and an app can only show what the system enumerated. If Preen's picker has no Continuity entry, the fixes live in the sections above, not in any app's settings. What the picker saves you is the joining a call to find out, and the ten minutes of blaming Zoom for a camera the system never offered it.

Continuity Camera, macOS, FaceTime and Photo Booth belong to Apple. The reports quoted are public threads on Apple's Support Communities and developer forums, linked above with their dates, and they describe the reporters' systems, not ours. If Apple documents a fix, this page will be corrected and the changelog will say so.

Changelog

2 September 2026. First published.