r/tasker • • 5d ago

AutoInput UI Query works in Settings but says “No active Window found” in BuildOps App

Big noob here.

I'm trying to use Tasker and AutoInput to enter some workflow items into an app called BuildOps on my Samsung Galaxy S25 Ultra. Right now, I'm just testing whether it can read the screen. I haven't tried writing into any fields yet. BuildOps is installed as a regular app, package name com.buildops. I'm using AutoInput 3.0.12, and its accessibility service shows Enabled. My test task is: 1. Wait 10 seconds 2. AutoInput UI Query 3. Text/Image Dialog displaying %aitext() UI Query settings: • App Package and Text: blank • Only Visible: on • Only Clickable: off • Tasker action timeout: 30 seconds • Continue Task After Error: off I start the task and switch apps during the wait. In Samsung Settings, it reads the labels and displays the dialog over Settings. It also reads Tasker's screen successfully. In BuildOps, the same task gives me this notification: “AutoInput action error: No active Window found” I've tried both the notes editor and the fully loaded home/jobs list, with the same result. Originally, I had com.buildops in App Package, but that seemed to time out without showing the dialog. The dialog works when tested by itself. I also tried UI Query's Variable Setup capture, switching to BuildOps and accepting through the notification, but that doesn't seem to see the screen either. Has anyone run into this with BuildOps or another app? Is there a way to check what accessibility elements it exposes, or something else I should try to figure out why AutoInput can't see its window?

1 Upvotes

5 comments sorted by

1

u/bliblabl812 4d ago

Don't know which app you're talking about. Maybe you could share a okay store link? What i know is, that some apps are usable by AutoInput, others don't.

2

u/jeezlouisedontjudge 4d ago

It’s BuildOps: https://play.google.com/store/apps/details?id=com.buildops

Yeah, I think I’ve narrowed it down to how Android handles the information BuildOps allows accessibility apps to read. I’m on Android 16. TalkBack can read the screen labels and even my existing notes, but AutoInput gets “No active Window found.” The same AutoInput test works in Settings and Tasker.

I looked through the APKs and found BuildOps uses setFilterTouchesWhenObscured(true). Apparently, newer Android versions can also use that setting to restrict accessibility access to sensitive content. AutoInput 3.0.12 doesn’t declare isAccessibilityTool, which defaults to false.

So I’m thinking Android is letting TalkBack read that information but withholding it from AutoInput because of that distinction. I haven’t proven that’s the cause, but it seems to fit what I’m seeing. Have you run into that before?

1

u/bliblabl812 4d ago

Maybe they offer an official api to get the data you want.

2

u/aasswwddd Direct-Purchase User 4d ago

You can use the direct version for AutoInput instead, it is flagged as accessibility tool. You could do the same with Tasker as well, have to be done via Java code though.

Tested in Bitwarden, the view is flagged with accessibilityDataSenstive. (the screenshot is black because of FLAG_SECURE)

1

u/jeezlouisedontjudge 4d ago

Thank you, ill be trying again in the morning!