Automagic NFC message when using a tag for SmartLock

Post your questions and help other users.

Moderator: Martin

Post Reply
petr.pavel
Posts: 4
Joined: 24 Aug 2014 18:15

Automagic NFC message when using a tag for SmartLock

Post by petr.pavel » 29 Jan 2017 21:00

Hi everyone,
I use a NFC tag to unlock my phone via SmartLock (vanilla Android 6, Nexus 5).
It used to work fine - I put my phone on the tag, it unlocked, that was it.

Recently I went through a factory reset and since then, Automagic responds to the tag as well. My phone still unlocks but additionally to it, Automagic displays a message:
"NFC tag trigger is not available or the flow is not enabled."

Coincidentally, I do have some flows with NFC triggers but none for this particular tag (all of them currently disabled). I imported my flows from backup, if it makes any difference. Also, I didn't grant Automagic any permissions yet because currently I only use it for Gleeo backup (I need the file placed in a specific directory so I can't use the built-in backup).

I'd like the message not to show when I unlock my phone, it distracts me. I wonder why it's doing now when it wasn't happening before the factory reset. I was without the phone for two months so perhaps a new version of Automagic was published.

Any suggestions?
Thanks
Petr

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: Automagic NFC message when using a tag for SmartLock

Post by Martin » 01 Feb 2017 21:09

Hi,

It's caused when none of the NFC triggers handles the scanned generic tag. I probably missed this case when support for generic tags was introduced. As a workaround you could add a flow with a trigger NFC Tag for this particular tag but without any actions.
You could also avoid the message by disabling Handle existing NFC tags in the preferences of Automagic provided that you don't use this feature.

I'll remove the message for this case in the next update.

Regards,
Martin

petr.pavel
Posts: 4
Joined: 24 Aug 2014 18:15

Re: Automagic NFC message when using a tag for SmartLock

Post by petr.pavel » 06 Feb 2017 10:30

Thank you Martin for confirming the issue and for suggesting the workarounds.
I was able to disable Handle existing NFC tags and it did get rid of the message.

Petr

Post Reply