You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Guys,
The new version don't allow me to perform a SELECT command.
But, in the EMV wolrd, SELECT command returns important information and I need
them on my application.
I wont migrate to this new version due to this limitation. Can you handle this
by at least providing the SELECT answer in the basicChannel?
Thanks.
Original issue reported on code.google.com by kdusilve...@gmail.com on 22 Jun 2011 at 3:32
The text was updated successfully, but these errors were encountered:
Correcting gramma ;)
"By prohibiting SELECT command EMV applications will be limited:
Guys,
The new version doesn't allow me to perform a SELECT command.
But, in the EMV world, SELECT command returns important information and I need
them on my application.
I won't migrate to this new version due to this limitation. Can you handle this
by at least providing the SELECT answer in the basicChannel?
Thanks."
Original comment by kdusilve...@gmail.com on 22 Jun 2011 at 5:17
It's not desirable to support a SELECT command in the OpenMobileAPI spec as
- this might result with an 'SIM error' if the selected applet is changed on
the basic channel for the UICC
- most basebands discard SELECT by name commands to omit an 'SIM error'
- (it might become challenging with Access Control when the applet selection is
changed on a tranmit() )
-> Android applications should filter a SELECT command and translate to
closeChannel and openChannel(new AID) to change the context
Receiving the SELECT response within an application (if possible) should be
included in next OMAPI spec and correspondig SEEK release
Original comment by Daniel.A...@gi-de.com on 27 Sep 2011 at 8:52
Original issue reported on code.google.com by
kdusilve...@gmail.com
on 22 Jun 2011 at 3:32The text was updated successfully, but these errors were encountered: