Engineering notes
Tasker "Couldn't find matching configured network" on Android 17
Tasker "Couldn't find matching configured network" on Android 17 Pixels: a Wi-Fi module update now blocks Tasker Settings. Logs, cause, and workarounds.
If Tasker's Connect To WiFi action stopped working on your Pixel in November 2026 and now fails with this error, your setup is probably fine:
Tasker Action Error
Action: 'Connect To WiFi' (step 2)
Couldn't find matching configured network (Error Code: 1)
On our Pixel running Android 17, Android now refuses to give the Tasker Settings helper app the list of saved Wi-Fi networks. Without that list, Connect To WiFi cannot work, no matter which permissions you grant. Below is how we confirmed it with three log lines, why the usual fixes do nothing, and what to use instead.
The setup that broke
A Tasker profile fires near the home router while the phone sits on a different saved network. Its task runs Connect To WiFi with the home network's name. It worked for about two weeks, then failed every time with the error above.
Versions:
| Component | Version |
|---|---|
| Phone | Pixel 11 Pro |
| Android | 17 (SDK 37), build CD1A.261005.003, patch 2026-10-05 |
| Tasker | 6.7.9 (targets SDK 36) |
| Tasker Settings | 2.0.0 (targets SDK 21), the latest release |
| Wi-Fi module | com.google.android.wifi 373041260 |
Why the usual fixes do nothing
Search for this error and you find old Tasker Google Group threads. They suggest location permission set to "allow all the time", Nearby Devices, Appear on top, location services on, installing Tasker Settings, and exempting it from battery optimization. We had all of that. Exempting Tasker Settings from battery optimization changed nothing.
It also isn't a typo in the network name. We compared the bytes of the SSID in the Tasker export with adb shell cmd wifi list-networks, and they matched exactly.
Being out of range doesn't matter either. The lookup runs against saved networks, which includes networks that are nowhere nearby.
How Connect To WiFi actually works
Since Android 10, apps that target Android 10 or newer get an empty list from WifiManager.getConfiguredNetworks() (Android 10 privacy changes). Tasker targets a recent SDK, so it can't read your saved networks.
The workaround has been Tasker Settings, a helper app that deliberately targets SDK 21. Android keeps a legacy exemption for apps targeting older SDKs, so the helper could still read the list. Its connect action is short (source):
val configuredNetworks = wifiManager.configuredNetworks
val matchingNetwork = configuredNetworks.firstOrNull {
val ssid = it.SSID.nullIfEmpty ?: return@firstOrNull false
ssid.replace("\"", "") == input.ssid
} ?: return PluginResult(false, "Couldn't find matching configured network")
So "Couldn't find matching configured network" means one of two things: the network name doesn't match, or Android returned an empty list.
The three log lines that settle it
Android's Wi-Fi service logs a line whenever it refuses an app the saved-network list. On a busy phone the main logcat buffer held about one minute of history, so reading it after the failure missed the moment twice. We had to stream it live while running the task:
adb logcat -v time -b main,system,events -T 1 \
| grep --line-buffered -E 'getConfiguredNetworks|taskersettings'
One run of the task produced:
12:56:35.026 I/WifiService: getConfiguredNetworks not allowed for uid=<tasker>
12:56:35.046 I/am_proc_start: [...,com.joaomgcd.taskersettings,bound-service,...]
12:56:35.117 I/WifiService: getConfiguredNetworks not allowed for uid=<tasker settings>
Tasker asks first and is refused, which is expected. It then starts Tasker Settings, and Android refuses the helper too. There is no Permission violation line, so the location checks pass. What fails is the check that exempts apps targeting older SDKs.
What changed, and when
The OS did not change: the build is from September with the October security patch. Tasker Settings wasn't updated either. What did change was a Google Play system update. These update core parts of Android, including the Wi-Fi module, in the background and install at the next reboot:
- The phone rebooted on 2026-11-14 at 14:55, and modules from the
2026-10-01bundle installed then.com.google.android.modulemetadataandnetworkstackboth show that timestamp. - The Wi-Fi module had moved from its factory version 370546200 to 373041260, from the same batch.
- The first failure we logged came about 4.5 hours later.
Android doesn't show the Wi-Fi module's own install time without root, so this is a strong correlation rather than proof. The public source code doesn't explain it either. The exemption check (isTargetSdkLessThanQOrPrivileged in WifiServiceImpl) is identical in AOSP android16-release, android17-release and main. In public code, an app targeting SDK 21 still gets the list. Whatever changed seems to be in Google's own build of the Wi-Fi module.
Check whether you have the same problem
With wireless debugging or a USB cable, start the live logcat command above, then run your task once. If you see getConfiguredNetworks not allowed for the Tasker Settings uid, you have this problem. To find the uid:
adb shell cmd package list packages -U | grep taskersettings
If there's no refusal line and you still get the error, compare the SSID in your task with adb shell cmd wifi list-networks. Look for trailing spaces and capitalization differences.
Workarounds
- Let Android pick the network. If the goal is "use the home network when it's in range", turn off Auto-connect for the network the phone keeps choosing instead (Settings, Network & internet, Internet, that network). Android's own auto-join then picks the home network, and the Tasker profile isn't needed.
- Connect from a privileged shell. With Shizuku or Tasker's ADB Wifi support, a Run Shell action can run
cmd wifi connect-network YOUR_SSID wpa3 YOUR_PASSPHRASE. This works without reading the saved list, but your Wi-Fi password then lives in the Tasker task. - Report it. If you can reproduce the log lines above, add them to an issue on the Tasker Settings repository. Include your build and the version of
com.google.android.wifi(adb shell pm list packages --apex-only --show-versioncode).
Takeaways
- On Android 17 Pixels with the October 2026 module update, Tasker's Connect To WiFi through Tasker Settings fails with "Couldn't find matching configured network". Android refuses the helper the saved-network list.
- Permission tweaks and battery exemptions don't help. The refusal shows up in logcat as
getConfiguredNetworks not allowed for uid=.... - Google Play system updates can change Android behavior without an OS update or any public code change. When an automation breaks with no update you remember installing, check the module versions.
This is the second time a Pixel automation sent us into the logs. The first was AirPods that showed as connected on a Pixel but played no audio, also fixed with Tasker and adb.