Tap to Share on Android: What It Needs, and Why the Tap Does Nothing

Tap to Share is the rare feature that does what its name says. You bring two compatible Android phones together, the devices establish a connection, and the content - a contact card, photos, a video, a link, a location - goes across without a menu, a PIN or a pairing screen. Google began the rollout on Pixel 6 and newer, with Samsung's current foldables named as the next in line.

It is built on Quick Share rather than replacing it, which is why most of the troubleshooting is Quick Share troubleshooting with one extra variable: the tap itself. Understanding which layer failed tells you whether to look at the radios, the visibility setting or the app.

What each requirement actually does

The third row catches the most people, because it is counter-intuitive on a phone with mobile data: both Bluetooth and Wi-Fi need to be on even when there is no network, since the transfer runs over a direct local link rather than the internet.

Setting it up and sending something

1. Step 1 Update both phones first

   Tap to Share arrived through a Play services and Quick Share update. A device that has not received it will simply not respond to the tap, and no setting will change that.

2. Step 2 Turn on Bluetooth, Wi-Fi and Quick Share

   All three, on both devices. Leave Wi-Fi on even if you are not connected to a network; the direct link needs the radio, not a router.

3. Step 3 Set visibility to contacts or everyone

   Open Quick Share settings on the receiving phone and choose the wider option for the duration of the transfer. "Your devices only" is the setting that makes the other phone invisible.

4. Step 4 Unlock the phone that is receiving

   The receiver has to accept, and a locked screen is the most common reason a transfer hangs at ninety percent. Keep both screens on until it finishes.

5. Step 5 Bring the two devices together and hold

   Tap the backs of the phones together and hold for a second rather than bumping once. The gesture establishes the connection; the actual data then moves over the local link.

6. Step 6 Narrow visibility again afterwards

   Return the receiving device to contacts-only. Leaving a phone permanently discoverable is the setting most people forget, and it is the one with a privacy cost.

When the tap does nothing

• Check that case thickness is not the problem: two thick cases can keep the radios far enough apart to fail the handshake.
• Restart both phones; Quick Share's discovery service is the first thing to wedge after an update.
• Clear the Quick Share cache rather than its data, which keeps your saved devices.
• Check whether a work profile or device policy has disabled nearby sharing.
• Test with a plain photo rather than a contact card, to see whether the issue is the transport or one content type.
• Try the manual Quick Share route - select, share, pick the device - to confirm the transfer layer works and only the tap is broken.

Is Tap to Share the same thing as AirDrop?

No. It is a shortcut on top of Quick Share, which is Android's own proximity sharing system. It produces a similar experience on Android-to-Android transfers, and it does not make an Android phone visible to an iPhone.

Does it need an internet connection?

No. The transfer runs over a direct local link between the two devices, which is why it works on a plane or in a basement. The feature rollout itself arrived over the network, but the sending does not use it.

Does it work with an iPhone?

Not through Tap to Share. Cross-platform transfers on Android go through Quick Share's compatibility with other systems, or through a messaging app, and neither uses the tap gesture.

Why does it only work with some phones?

Because it needs hardware and software on both ends: a supported device, a current Quick Share build and the right radios. Pixel 6 and newer came first, with Samsung's recent foldables named as the next wave - older devices are not a settings problem.