title: AAR Record in NFC: Where's The Payload?
body: <p>According to <a href="https://stackoverflow.com/a/9235624/115145">this answer</a>, 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 <code>MAIN</code>/<code>LAUNCHER</code> activity for the app specified in the AAR.</p>
  
  <p>That <code>MAIN</code>/<code>LAUNCHER</code> <code>Intent</code> does not contain the <code>NfcAdapter.EXTRA_NDEF_MESSAGES</code> extra. Hence, the data that we went through all the trouble to beam over appears to be lost if you use AAR.</p>
  
  <p>Is there some way to get the NFC messages that triggered the app to be started in this scenario?</p>
  
  <p>And if the answer is "no", then what is the use case of AAR? I can see where it might be helpful when the desired app does not exist on the receiving device (brings up Play Store), but then once the app is installed, AAR foils any attempt to deliver data from one device to the other, which is kinda the point behind NFC.</p>
  
  <p>Thanks!</p>