Detect invalid authentication failures for Tasker profile trigger

Secure Settings had the ability to detect authentication failures as an event for Tasker profiles so you could execute specific things if someone is messing with your device.  It seemed to be pretty popular, and I don't see any current way to do this now that Secure Settings seems to be abandoned and no longer works (easily?) since Marshmallow.

Ideally this could be set to the number of attempts required in order to trigger the profile state, ie:  1 failure not necessarily trigger it, but perhaps 2, or some folks may prefer 3, etc.  This could possibly be done in the task itself, but ideally in the plugin itself to reduce external logic.


1 reply

It should respond to any type of login attempts, be it pattern, pin or fingerprint.