Discovery problems and transfer failures are different. First make the receiving device visible through the current Quick Share controls, then test with one small non-sensitive file.
Prepare the receiver
Open the receiving flow and keep the device unlocked and nearby. Check the visibility setting and the account or contact conditions it uses. Names and options can differ by manufacturer. A device that is deliberately hidden should not be treated as a broken sender.
Check the radios and context
Follow the official requirements for Bluetooth and Wi-Fi on both devices. If a Windows computer is involved, use the Windows-specific guidance rather than assuming the Android-to-Android flow is identical. Managed networks can introduce restrictions.
Run a small test
Send one harmless file and confirm the recipient identity before accepting. If discovery works but the transfer stalls, record that change in the symptom. You have moved to a different stage of the process and should stop repeating discovery-only fixes.
Finish by narrowing visibility
After receiving, return to the visibility level appropriate for normal use. If a temporary everyone mode is available, understand its timeout rather than leaving broader discoverability than necessary. Open the received file to verify that the task actually completed.