Application Closed trigger acts like Application Launched

[Quidn]

There's no other macros using Application Launched/Closed trigger.

Is there any idea to figure this out why this weird symptom happens?

Turning on Force legacy mechanism option tends to be barely fires.

I'm almost just before give up to using Application Launched/Closed trigger for detect all applications'.

Anyway it seems mostly works if apps are specified so may not a huge deal in general.

 

[dhj49er]

I have Galaxy S23 running Android 13 and have found the following for application closed trigger:-

All applications selected and force legacy mechanism disabled - triggers on app launch. No trigger on app closed

All applications selected and force legacy mechanism enabled - no trigger on closing (or launching) an app.

Single app selected and force legacy mechanism disabled - no trigger on closing (or launching) the selected app.

Single app selected and force legacy mechanism enabled - triggers on closing the selected app.

If I was I using this trigger I would limit it to individual apps (not all) and enable the force legacy mechanism.

I see @Quidn has decided to use individual apps but not the force legacy mechanism.

The need to use force legacy mechanism may depend on the version of Android and perhaps the make of phone.

 

[Quidn]

I have Galaxy S23 running Android 13 and have found the following for application closed trigger:-

All applications selected and force legacy mechanism disabled - triggers on app launch. No trigger on app closed

All applications selected and force legacy mechanism enabled - no trigger on closing (or launching) an app.

Single app selected and force legacy mechanism disabled - no trigger on closing (or launching) the selected app.

Single app selected and force legacy mechanism enabled - triggers on closing the selected app.

If I was I using this trigger I would limit it to individual apps (not all) and enable the force legacy mechanism.

I see @Quidn has decided to use individual apps but not the force legacy mechanism.

The need to use force legacy mechanism may depend on the version of Android and perhaps the make of phone.

Thank you for detailed testing.
Then basically this issue is not just for me.

Mine is too Android 13 / One UI 5.1 but preceding model. So maybe it's vendor-specific issue, or maybe a common bug.

To detect closing of selected app(s) mostly works fine whether force legacy mechanism or not. That's a difference but anyway both of ours triggers fine if detect only selected apps.

I'd upload a sample macro to make others easy to test.
I found that Force Legacy Mechanism is a global option. It'd be applied globally wherever you set and whatever you had set before in a trigger.
So preset won't be much helpful and maybe create a new would be faster than download and import a macro.

 

[sampleuserhere]

This is reproduceable on my device as well.

Another thing to be noted is that the trigger also recognised "One Hand Operation+", which had been showing up all the time as an overlay window, as "Closed Application".