Hello! We developed a mobile payment application which use HCE and listen for MasterCard AIDs. Nevertheless, there are problems with some secure element included SIM cards. I read the Coexistence with Secure Element Cards section in the HCE documentation ( https://developer.android.com/guide/topics/connectivity/nfc/hce.html#Coexistence) but it writes only about routing table and AID handling, not that situation when a HCE and a SE routing table contains the same AID. What should happen then? Does Android send the APDU to all application which listen to the same AID? Unfortunately, my experience with some SE included SIM card is that my app (which use HCE) not gets the APUDs.
I read the Google HCE patent (https://www.google.com/patents/US8744347) too, to get deeper insight, and it mention the following: "In another example of an incoming data routing sequence not shown, the arbitration point P2(AR) decides that the request for application session opening must be rejected, either because it does not recoginze the application concerned (no processing program being provided), or because it has been configured by the operator not to process this application (such as a paid application not subscribed to by the holder of the SIM card/processor HP2)" So is it possible the carrier messed up their SE implementation and aborts any other APDU processing, and that's why my application not gets in some case the APDUs from the POS terminal? Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/ca62e4d4-202d-4ddd-aadd-6bdb4e258176%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.