NFC warning

[evebrea]

I had almost this exact issue with an automagic tag. instead of just writing the tag, it writes

http://automagic4android.com/en/automag ... d=desk_nfc

which when read by my tablet is a URL, so both automagic AND firefox (my chosen browser) want to open it.

[Martin]

Does it work when you use one of the new tag writing options (Include Android application record and/or Write alternate tag information) available in the EAP-version?

-Include Android application record writes an additional AAR to the tag which tells Android that this tag should be opened specifically by Automagic
-Write alternate tag information uses a different protocol in the URL which should only be handled in Automagic

[evebrea]

I'll have to wait. I'm not gonna install EAP and break all my existing flows.

Unless you made an EAP that doesn't do that now

but why make it use a URL at all? i have seen so many nfc writing apps that can write specifics to the tag. why not just do that?

i took the tag that was having issues, wrote text to it, locked it ( i believe) and then told automagic to use existing tag and scanned it as a digit code. Now it works fine without that URL junk.

[MURTUMA]

The flows do not break but if you make a new flow which uses new elements n not available in official version they won't work.

[Martin]

@evebrea: Usually an NFC tag needs to carry some information to ensure that the tag is opened with a specific app like Automagic (can be an URL or a MimeType etc.). Until now the URL-mechanism worked quite well including older Android versions like 2.3 etc. Android 4 introduced a new mechanism to write some Android-proprietary information to the tag called an Android application record that should ensure that a tag is opened with a specific app. It was not necessary to do this but it makes sense to add it now when other apps also want to process tags written by Automagic.