Target API level 28

[ItsHarper]

Apps that target API level 28 can still turn Wi-Fi on and off, but aren't blocked from on-device installation by Android 14. I know this because I work on the FIRST Tech Challenge driver station app, which automatically turns on Wi-Fi under certain conditions, and I just tested that functionality on Android 14.

[ItsHarper]

Hmm, this app provides more functionality than I'd realized, and I'm not sure that all of it is possible when targeting 28. Still, it would be great if there was a version of the app that at least targets API 23, even if that version can't do everything that the version that targets 21 can.

[joaomgcd]

This version targets API 23: https://github.com/joaomgcd/TaskerSettings/releases/download/v1.7.0/Tasker.Settings.1.7.0.Huawei.Xiaomi.apk

Can you try that?

[Jon8RFC]

Interesting thought.

@joaomgcd for future reference, as things get more cumbersome with google changes, maybe a Magisk module which does these things would be possible (that's beyond me, for now, but ChatGPT may help me again). Doing data gathering to determine root users may be helpful.

If not, an application which acts as the hub/manager for update notifications or automatic installations from github could manage installing numerous apks which each, individually, target a specific API.
Each would perform a minimal set of functions specific to that API while supporting a larger number of Android OS versions, so that the maximum number of functions is possible with a minimal loss of functions across many Android versions.

Thanks for doing so much with Tasker. It is a great app.

[scottrepreneur]

I'm also hitting this. As of Android 14, the app cannot be installed at all:

adb: failed to install Tasker.Settings.2.0.0.apk: Failure [INSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 24, but found 21]

Android 14 enforces a minimum targetSdkVersion of 24, and the current release targets 21. This makes Tasker Settings completely unusable on modern devices — not just a policy warning, but a hard install block. Would be great to get this updated.

Workaround: adb install --bypass-low-target-sdk-block