Action "launch app" with strange behaviour

[rainscho]

Hi all.

If I use the action "launch app" for an non-installed app, I get an error "Could not get launch intent for package com.abc.xyz. Please define a class." and the flow is stopped ... okay.
After adding an exception link from this action "launch app", this error is not notificated anymore ... okay.
But with this added exception link from this action, also the standard link is executed ... my expectation is that only the exception link should be executed.

Is this a bug or a feature?

Any comments welcome! Thanks in advance.

[Desmanto]

Seem to be featured, the normal connection still executed even after branching to exception. You can add expression after the normal connection to check the error first.

Code: Select all

!contains(exception_message, "Could not get launch intent for package")

False, stop and do nothing. True, continue to your normal connection if the app launch properly.

But I still think that the flow should have branch to the exception and not executing normal connection anymore.

[rainscho]

Hi Desmanto!

Thanks for the work-around. I did not know the variable exception_message.

Let's wait for Martin to comment if it is a bug.

[Martin]

That's a bug. The regular connection should not be executed in such a case.
Thanks for reporting! It's fixed in the next build.

Regards,
Martin