Aar Record In Nfc: Where's The Payload?

According to this answer, and validated by testing, when you use Android Beam to push over an NFC message containing an AAR record, the receiving device will start the MAIN/LAUNCHE

Solution 1:

At the risk of answering my own question, one recipe for getting this to work (apparently) is:

• Have the Beam sender use an NFC message with two NFC records, the first containing something for a unique MIME type, the second being the AAR

• Have the Beam recipient have an <intent-filter> on the activity that responds to the first NFC record, such as via:

  <intent-filter><actionandroid:name="android.nfc.action.NDEF_DISCOVERED"/><categoryandroid:name="android.intent.category.DEFAULT"/><dataandroid:mimeType="application/vnd.commonsware.webbeam"/></intent-filter>

If the app already exists, the NDEF_DISCOVEREDIntent will be used, and the recipient can pick up the NFC message and pull out the data from the initial record. If the app does not exist, the AAR will kick in, bringing up the Play Store (whether your app is distributed through the Play Store or not).

This is the recipe shown in the Android Beam example on the developer site.

Solution 2:

From a look at the docs it would seem the use-case is guaranteeing that your application is launched from the NFC event. A second use-case would basically providing a way for the phone to know which app it needs to read a tag.

Couple of questions If you use two records: first normal, second AAR how does the activity get launched? I would expect you'd be started via the tag dispatch intent. Does the AAR intent contain anything that gets you the Tag? I'm thinking you could manua