[solved] [bug] Macro not invoking (application launched)

[roughnecks]

Not sure if related but MD thinks foobar2000 is closed when it's not in the foreground anymore, even if it's still up and running - the mini player is also available in the notifications window.
So when I tap on the "home" button and foobar's window goes away, MD triggers as application closed; on the contrary, if I really close foobar, MD doesn't trigger.

 

[MacroDroidDev]

This issue is now fixed in 5.6.2.

For anyone interested in the reason, I tweaked an accessibility service permission to try and prevent some other bug happening on some devices but this seems to have prevented the app launched trigger working in some cases (It works ok with this change on all the devices I tested but many others have issues).

 

[roughnecks]

This issue is now fixed in 5.6.2.

For anyone interested in the reason, I tweaked an accessibility service permission to try and prevent some other bug happening on some devices but this seems to have prevented the app launched trigger working in some cases (It works ok with this change on all the devices I tested but many others have issues).

Thanks

 

[roughnecks]

This issue is now fixed in 5.6.2.

For anyone interested in the reason, I tweaked an accessibility service permission to try and prevent some other bug happening on some devices but this seems to have prevented the app launched trigger working in some cases (It works ok with this change on all the devices I tested but many others have issues).

Sorry to tell but it's still not working for me.

 

[tanutanu]

Sorry to tell but it's still not working for me.

try turning off/on MD accessibility services. It works for me.

 

[roughnecks]

try turning off/on MD accessibility services. It works for me.

Oh, nice, it worked! Thanks