Troubleshooting
Your TV doesn't show up in the remote app: a diagnostic checklist
10 min read
A TV usually fails to appear for one of four reasons: the app was denied Local Network access on iPhone, the phone and TV are on different networks that look like the same Wi-Fi, the TV's network remote service is off, or the TV is asleep rather than on. Check them in that order — the permission is the most common cause and the only one iOS gives no error for.
The order matters more than the list. Each check below is cheaper and more likely than the one after it, so working downwards means most people stop within the first two minutes. Working upwards from the most technical cause means restarting a router for an hour over a permission toggle.
Start here: is Local Network access on?
iOS blocks apps from seeing anything on your Wi-Fi until you grant Local Network access, and this is the single most common reason a TV never appears. It is first on the list because it is also the most deceptive: when the permission is missing, iOS does not return an error. It returns nothing. The app's scan runs normally, finds no devices, reports no problem, and displays an empty list.
From the outside that is indistinguishable from a network with no televisions on it, which is why people spend so long on the router.
Open Settings › Privacy & Security › Local Network
This screen lists every app that has asked for the permission, with a switch beside each. It is more reliable than looking for the app itself, because apps appear under their Home Screen name rather than their App Store name.
Check the switch for your remote app
If it is off, that is your answer. If the app is not on the list at all, it has never asked — open it, let it try to find a TV, and the prompt will appear.
Force-quit the app and reopen it
Swipe up and flick the app away, then launch it again. A permission change is picked up when discovery next starts, not while the app is suspended in the background.
Are you really on the same network?
Two devices can be joined to what looks like the same Wi-Fi and still be unable to reach each other. This is the second most common cause, and it is the one people are most confident they have already ruled out — "they're both on the Wi-Fi" is true and insufficient at the same time.
The check that settles it takes about thirty seconds and does not require trusting anyone's memory of which network the TV joined.
Find the iPhone's IP address
Settings › Wi-Fi, then tap the ⓘ beside the connected network. The IP Address row shows something like
192.168.1.34.Find the TV's IP address
On most sets this is under Network › Network Status, or Settings › Support › About. Look for a row labelled IP address.
Compare the first three numbers
192.168.1.34and192.168.1.87are on the same subnet and can reach each other.192.168.1.34and192.168.4.12are not, and no amount of restarting the app will change that.
If the first three numbers differ, one of a handful of things is putting the devices in separate places. Each has a different fix.
| Cause | How to recognise it | What to do |
|---|---|---|
| A guest network | The phone is joined to an SSID with "guest" in the name, or one the TV was never given | Move the phone onto the main network. Guest networks isolate clients from each other by design. |
| Separate 2.4 GHz and 5 GHz SSIDs | The router lists two networks with the same name plus a suffix such as -5G | Join whichever one the TV is on. Older televisions are frequently 2.4 GHz only. |
| A mesh system or extender | IP addresses in different ranges depending on which node a device joined | Check whether the extender is in bridge mode. An extender running its own network puts its clients somewhere the main network cannot see. |
| The TV on Ethernet | The TV has a cable and the phone does not | Usually fine on a normal home router. It fails when the wired and wireless sides are separate segments, which is common with a separate switch or a business-style setup. |
| A VPN on the phone | A VPN profile is active in Settings | Turn it off and retry. Many VPNs capture all traffic including local addresses, which cuts the phone off from its own network. |
One more cause hides in this category and produces the same symptom without any IP mismatch: client isolation. Some routers, and most public or landlord-managed networks, deliberately stop devices on the network from talking to each other. Everything reaches the internet and nothing reaches anything else. If the addresses match and nothing works, this is the usual explanation, and it is a router setting rather than something the phone or TV can override.
Is the TV awake, or just showing a standby light?
A television in standby has usually left the network, which means there is nothing there for a scan to find. The glowing light on the front is not evidence of anything — on most sets it indicates power at the socket, not a live network connection.
This matters more than it used to because of energy-saving standby modes. Sets sold in the last few years default to a deep standby that shuts down the network interface, so the TV disappears from the network entirely within seconds of being switched off. Some brands offer a setting to keep the network alive in standby — worth turning on if you find it, though it lives in a different menu on every brand and is frequently labelled as an eco or power option rather than a network one.
The practical version: switch the TV fully on with its own buttons or its plastic remote, wait until the picture is up, then scan. A TV that appears when awake and vanishes when asleep is behaving normally, not faulty.
Is the TV's remote service enabled?
Most smart TVs expose their remote-control service by default, but not all of them, and a factory reset or a firmware update can switch it back off. The setting rarely lives anywhere labelled "remote" — it is usually filed under external devices, network, or mobile connections.
Menu names move between model years, so treat these as the area to search rather than an exact path:
- Samsung — look under General for External Device Manager, and inside it for Device Connect Manager. That screen holds both the access-notification setting and the list of devices the TV has previously allowed or denied.
- LG — look under Connection or Network for the mobile-connection settings. Some models also keep a separate toggle governing whether apps on the network may connect at all.
- Roku — Settings › System › Advanced system settings › Control by mobile apps, where Network access has to be set to Default or Permissive rather than Disabled.
- Android TV and Google TV — the remote service is normally on and not user-visible, but budget boxes that were never certified sometimes ship without it implemented at all.
While you are in the Samsung menu, it is worth checking the device list for a stale entry. A television that remembers denying your phone once will keep denying it, and the app has no way to tell you that is what happened — Samsung's allow-this-device prompt covers how that list works and how to clear it.
Brand-specific reasons a TV stays hidden
Beyond the general causes, each platform has a quirk of its own worth knowing, because they produce different symptoms and need different patience.
LG sets are slower to find than Samsung ones
LG webOS televisions advertise no Bonjour service for their remote protocol, which is the mechanism iOS is fastest at. LG's own app finds them over SSDP instead, and SSDP needs multicast — which Apple gates behind an entitlement (com.apple.developer.networking.multicast) that developers have to apply for individually. An app without it cannot hear an LG announce itself and has to find the set another way, typically by probing the local network address by address.
The consequence for a reader is simple and worth stating plainly: an LG will normally take longer to appear than a Samsung on the same network, and it is more sensitive to how the network is laid out. If an LG has not appeared yet, waiting is more useful than restarting.
Android TV boxes vary enormously
Certified Android TV and Google TV devices run the remote service and announce themselves normally. Cheap uncertified boxes running a modified Android build frequently do not implement it at all, in which case there is nothing to discover no matter what the box's packaging claimed.
Chromecast and Roku devices are found, and that is not the same as controlled
Both announce themselves over Bonjour and appear in device lists quickly and reliably. Appearing in a list means the discovery scan worked, and nothing more — whether an app can actually drive the device is a separate question and depends entirely on which platforms that app has implemented.
When should I just give the app time?
Discovery is not instant, and impatience is a real cause of empty lists. Brands announce themselves at different speeds, and platforms that have to be searched for rather than listened for take considerably longer — a full pass over a home network means testing every address on it, which cannot be rushed.
Tivi, a universal TV remote app for iPhone from Nefarius Apps, gives a scan up to fifteen seconds before it concludes there is nothing there. Most Samsungs appear in the first second or two; LG sets frequently arrive near the end of that window. Closing the app after three seconds and declaring it broken is, unhelpfully, one of the most common things that happens.
- Let the scan finish. Watch it through to the end at least once before changing anything.
- Keep the app in the foreground. iOS suspends background apps, and a suspended app is not scanning.
- Move closer to the router for the first connection. A weak signal produces partial results that look like missing devices.
- Try once more after the first pass. Some sets respond to a second query when they were busy during the first.
Common questions
My TV worked yesterday and has disappeared today. What changed?
Usually the address. Home routers hand out IP addresses on a lease, and a television that was switched off overnight can come back on a different one, or land on a different mesh node than before. Rescanning rather than reconnecting to the saved entry normally resolves it. A firmware update overnight is the other common answer, since some updates reset the external-device settings.
Do I need to restart my router?
Almost never, and it is worth exhausting the checklist first. A router restart fixes address-lease confusion and nothing else; it does not change client isolation, guest-network separation, or a denied permission on the phone, which between them account for most cases.
The app finds my TV but the buttons do nothing. Is that the same problem?
No, and it is worth treating separately. Appearing in the list means discovery succeeded. Buttons doing nothing means either the connection was never authorised on the TV, the connection has since dropped, or the command is not supported on that platform at all. Discovery fixes will not help with any of the three.
Does it matter whether the TV is on Wi-Fi or Ethernet?
Not on a normal home router, where wired and wireless clients share one network. It matters when the wired side is a separate segment — common with a managed switch, a second router, or a building network — because the phone and the TV then have no route to each other.
The short version
Check the Local Network permission, then compare the first three numbers of the two IP addresses, then make sure the TV is genuinely awake, then look for the remote service in the TV's own menus. Those four cover the overwhelming majority of cases, in that order.
If everything checks out and the list is still empty, the last thing worth trying is patience — particularly on LG. More on how discovery works in the first place is in how to use your iPhone as a TV remote, the rest of the troubleshooting guides cover the failures that come after this one, and the frequently asked questions cover the setup basics.