Misfiring Profiles

[nmyshkin]

The three profiles shown below are meant to activate for three different apps:

Profile: FBReader (117)
Application: FB Library
Enter: Anon (124)
A1: Flash [ Text:Fbreader triggered Long:Off ]
A2: Perform Task [ Name:Library2 Stop:Off Priority:5 Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: ]
A3: Perform Task [ Name:CoverTimer Stop:Off Priority:5 Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: ]

Profile: Ebookdroid (47)
Application: Bookshelf
Enter: Anon (132)
A1: Flash [ Text:Ebookdroid trigger Long:Off ]
A2: Perform Task [ Name:Library3 Stop:Off Priority:5 Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: ]
A3: Perform Task [ Name:CoverTimer Stop:Off Priority:5 Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: ]

Profile: PerfectViewer (125)
Application: My Bookshelf
Enter: Anon (133)
A1: Flash [ Text:Perfect viewer triggered Long:Off ]
A2: Perform Task [ Name:Library4 Stop:Off Priority:5 Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: ]
A3: Perform Task [ Name:CoverTimer Stop:Off Priority:5 Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: ] 

I've been chasing odd behavior in an AppFactory-made app and am back with the Tasker routines. I only discovered what was happening because I wanted to set a variable when the profile kicked in. I saw the variable was not being set correctly and that led me to add the flash steps. To my surprise, selecting any one of the three apps fires up all three profiles! Whichever gets in there last is the one that takes over.

What in the world can be causing this effect?

Better, how can I get around it? Please don't say "just use such-and-such plugin app" because I am working with an Android 2.1 e-reader and it's all got to be done mostly the hard way with an ancient version of Tasker. 

I would hate to poll for the app in the foreground via shell script, but right now that's the only thing that comes to mind.

[SDS]

Use a single profile: Application->select the three apps. Inside the entry task to distinguish which app is opened, use: %WIN or Tasker function-> getcurrentApp. Or if there is only entry task(no exit task), then use profile: event->application->app changed: put the package name of the three apps, and  Inside the task to distinguish which app is opened, use: %app_package.

[nmyshkin]

Thanks for the suggestions. For all the time I've been using Tasker I did not know you could have more than one app as a trigger of a profile! That solved the issue (which is still mysterious) of all three profiles being triggered by any of the three apps.

None of the other functions/options you mentioned were available in the Tasker version I am using, so I used a shell script to determine which of the three apps was in focus.That let me set my housekeeping variable.

This actually (finally) seems to be working really well--as a Tasker routine.

I don't understand what is going on with the apk version. It runs just fine when first installed and I take it through its paces. The next day the profile appears not to fire no matter what I do.

I saw this behavior in the actual Tasker routines in the past, but have not seen it since I made the changes suggested by your idea.

So...not there yet...

[SDS]

Check by using other versions. I am using  6.5.11. Also Tasker works great on Android 10-12. I am using Android 11 and its amazing experience with tasker.