Setup & pairing
Why a TV remote app asks for Local Network access on iPhone
7 min read
A TV remote app needs Local Network access because iOS blocks apps from discovering or contacting devices on your Wi-Fi until you grant it. The permission covers Bonjour/mDNS discovery and direct connections to local IP addresses. If you decline it, the app cannot see your TV, and iOS gives it no error to display — the device list simply stays empty.
What does the Local Network permission control?
The Local Network permission gates two specific abilities: browsing for services advertised on the local network, and opening connections to addresses on that network. Apple introduced it in iOS 14 and has tightened it since; before that, any app could quietly enumerate everything on your Wi-Fi without telling you.
That covers more than it first appears. In scope:
- Bonjour and mDNS browsing — the mechanism by which a Samsung TV announces itself as
_samsung-remote._tcp.and a Roku announces itself as_roku._tcp. - Direct connections to local IP addresses — anything in the private ranges a home router hands out, such as
192.168.1.xor10.0.0.x - Broadcast and multicast traffic on the local link, which is how several discovery protocols find devices that do not advertise over Bonjour
Apple's stated reason for gating it is that the set of devices on your home network is revealing. It is a stable fingerprint of what you own, and because networks do not move, it is a strong hint about where you are. An app that could silently list every device on your Wi-Fi would learn a lot without asking for anything that looked like a privacy permission. Hence the dialog.
There is a second, less-known restriction alongside it. An app cannot browse for arbitrary Bonjour service types — it has to declare each one in advance, in its Info.plist, and iOS will only let it look for the types on that list. A remote app declares the TV service types it searches for and can see nothing else, permission granted or not.
Why can't a remote app work without it?
Remote control is entirely a local-network operation, from the first second to the last. Finding the TV means browsing the local network; connecting to the TV means opening a socket to its local IP address; sending a button press means writing to that socket. All three are on the wrong side of the permission when it is denied.
The part that makes this genuinely confusing is the failure mode. iOS does not return an error when the permission is missing — it returns nothing. The discovery browser starts, finds no services, and reports no problem. From inside the app the result is indistinguishable from a network with no TVs on it, which is why a denied permission usually looks like a broken app rather than a permissions issue.
What does the permission not give the app access to?
Local Network access is narrower than its name suggests. It grants the ability to find and talk to devices on your Wi-Fi. It grants nothing else, and it is not a general-purpose key to the phone.
| The permission allows | The permission does not allow |
|---|---|
| Discovering devices that advertise on the local network | Reading your browsing history or the traffic other apps send |
| Connecting to a TV's remote-control service on its local IP | Access to your files, photos, contacts or messages |
| Sending button presses to a device you have connected to | Seeing what is on the TV screen, or what you are watching |
| Looking for the Bonjour service types the app declared up front | Your location — that is a separate permission the app never requests |
It is also not an internet permission. Granting Local Network access does not give an app any additional ability to reach the wider internet; every app can already do that. The permission is specifically about the private side of the router.
How do I turn Local Network access back on?
iOS asks for Local Network access exactly once. Tap Don't Allow and the app has no way to ask again — there is no API for a second prompt, so an app that seems to have given up on asking is not being polite, it is out of options. The switch lives in Settings and has to be flipped there.
Open Settings and go to Privacy & Security
This route lists every app that has asked for the permission in one place, which is more reliable than hunting for the app itself.
Tap Local Network
You will see a list of apps with a toggle beside each. An app that was denied appears here with its switch off.
Turn the switch on for your remote app
Apps are listed under the name that appears on your Home Screen, which is not always the name in the App Store listing — look for the icon if the name is not what you expect.
Force-quit the app and reopen it
Swipe up from the bottom of the screen, flick the app away, and launch it again. The permission change is picked up when the app next starts its discovery, not while it is suspended in the background.
If the app does not appear in that list at all, it has never asked — which usually means it has not yet reached the point of starting a scan. Opening the app and letting it try to find a TV will produce the prompt.
Once the permission is on and the TV still does not appear, the cause has moved somewhere else: usually the network layout, the TV's own settings, or the TV being asleep rather than on. The diagnostic checklist for a TV that will not show up works through the rest in order of likelihood.
Does anything leave your home network?
With Tivi, a universal TV remote app for iPhone from Nefarius Apps, remote commands go from the phone straight to the TV over the local network. There is no server in between, no relay, and no account. When you press volume up, your iPhone opens a connection to the television's own address on your Wi-Fi and writes to it directly — the same thing the manufacturer's app does, minus the sign-in.
This is a consequence of how the protocols work rather than a design flourish. Samsung's and LG's remote services listen on the local network only; there is no public endpoint to route through even if someone wanted to. It is also why the app cannot control a TV from outside the house — the same property that keeps commands local prevents them travelling.
The formal version of what is and is not collected is in the privacy policy. The short version is that the device list is a list of the televisions on your own network, held on your own phone.
Common questions
Is it safe to allow Local Network access?
For an app whose entire purpose is talking to a device on your Wi-Fi, it is the permission the app exists to use, and iOS constrains what it unlocks — the app can only browse for the Bonjour service types it declared in advance, and the permission grants no access to files, location, or anything another app is doing. The judgement worth making is about the app rather than the permission: an app with no reason to touch your network asking for it is the case to be suspicious of.
Why does iOS ask again after I reinstall the app?
Deleting an app clears the permission decisions attached to it. A reinstall is treated as a new app, so the prompt appears again and a previous refusal does not carry over. The same happens after restoring a phone from certain backups.
Does the permission drain battery or slow down Wi-Fi?
Granting it does nothing on its own; only an app actively scanning uses the network. Discovery is a short burst of traffic when the app opens, not a continuous background process, and it stops when the app is closed.
Can I allow it just once?
No. Unlike location and photo access, Local Network is a simple on-or-off switch with no per-use option. It stays as you set it until you change it in Settings or remove the app.
The short version
Local Network access is the permission that lets an app see your Wi-Fi at all, and a TV remote app cannot function without it — not partly, not slowly, not at all. Denied, it fails silently, which is why an empty device list is so often a permission and so rarely a fault.
It is also narrower than it sounds: device discovery and device connections, nothing more. More on how the pieces fit together is in how to use your iPhone as a TV remote, and the rest of the setup and pairing guides cover the steps either side of this one.