The Assist request block doesn't work anymore

[Luc M.]

Hello Henrik,

Since the latest app updates, the Assist request block isn't triggered anymore when I long press the welcome button. Automate is declared as the Assistant app in Android settings.

I changed the responding app by setting the Google app or the Finder and it works well.

I've checked the privilege settings and everything seems to be ok.

I've rebooted the device and it's still the same behaviour.

I don't know where I'm wrong.

Can you please have a look and let me know?

My phone is a Samsung Galaxy A51 5G running Android v13 stock ROM.

Thanks a lot.

Luc

[Henrik "The Developer" Lindqvist]

Odd, it works in the Android 13 emulator with both gesture and 3-button navigation, but on newer Android versions the latter will no longer work since Google broke that.

Try "Clear default" in Automate settings.

Does it work if you use gesture navigation then swipe up diagonally from a botton corner?

[Luc M.]

Thanks for the suggestions but neither worked:

- the Clear default didn't change anything

- using the swipe up from a corner produces only a white line at the bottom of the screen

but no triggering of the Assist request block.

What can be done?

Luc

[Henrik "The Developer" Lindqvist]

I forgot, when using gesture navigation also ensure its "Swipe to invoke assistant" option is enabled.

So if you swipe up from a corner a white border around the screen is flashing?

[Henrik "The Developer" Lindqvist]

As a workaround, make long-pressing the power button open the assistant is system gesture settings.

On Saturday, September 6, 2025 at 10:47:04 PM UTC+2 mouta...@gmail.com wrote:

[Luc M.]

I confirm that during my tests, the "Swipe to invoke assistant" option was enabled.

I've even changed the responding app from Automate to Google to check that the Android assistant function works properly.

And when I swipe up from a corner, a white border around the screen was flashing but Automate wasn't triggered.

When I long press on the Welcome button, I get a vibration (this option is enabled too) but nothing happens in Automate, nothing in the log of the flow.

So the problem seems to come from Automate because it worked before the latest updates of the app.

[Luc M.]

And besides, I'm running v1.48.0 from the Google Play Store in which, the Assist request block has been modified according to the update log :

• Assist request block window not showing when always/default available

So there has been a change in this block causing this bug.

Thanks for your help.

[Henrik "The Developer" Lindqvist]

Indeed, the block has changed but i cannot reproduce your issue.

But if you see the white border flashing then Automate should at least been invoked, it's just showing the UI, which is always should since you've "Clear default".

I'll investigate to so if something obvious could be the cause, otherwise i'll have to await further reports, or include some debug logging for the next release.

[Luc M.]

In reality, the white screen border is not fully displayed, it begins at the bottom of the screen as an animation then stops rapidly and it is never fully displayed.

So I've made some more tests and I managed to make it work by enabling the "Screen text analysis" option in Android assistant settings.
In this case, the border is fully displayed and the Automate dialog asking for a flow appears (as I cleared the dialog defaults) and the flow starts correctly.

But if I disable this option, it doesn't work anymore.

As you can imagine, I prefer disabling this option...

I hope this will lead you on the way for insvestigating more precisely.

Thanks.

Luc

[Henrik "The Developer" Lindqvist]

Great find, then i can see if there's a way to get it working without that option enabled, if not then i'll update the documentation at least.