If Applet throw error in selection SEEK library throw applet not found exception
GoogleCodeExporter opened this issue · comments
What's the problem?
I have created one sample Java card applet.In which on selection I am returning
0X6985 in some failure case. When I try to access this applet through SEEK
library on Android Device it through Exception as "Applet with given AID not
exist on SE"
What steps will reproduce the problem?
1.Create one sample applet and in selection through 0X6985
2. Try to select this applet through SEEK on Android device.
What is the expected output? What do you see instead?
According to me, It should not through exception but give proper response. As
other wise we will not be able to identify scenario when Applet is present and
when Applet is locked
What version of the product are you using? On what operating system?
Android OS version : 4.2.2
Device : Samsung S4
Model Number: GT-I9500
Baseband version : I9500DDUBMF8
Build Number : JDQ39.I9500XwUBMG5
Kernal Version : 3.4.5-1133023
dpi@DELL212#1
Thu Jul 18 09:27:00 KST 2013
My device Smart card API Version : 2.4.0
Please provide any additional information below.
Not any.
Original issue reported on code.google.com by theatind...@gmail.com on 20 Dec 2013 at 10:21
I have been encountering a similar issue with certain kernel versions on the S3
and S4 running Android 4.2.2. Looking at the smartcard-api.patch files for
3_1_0 (available in the downloads section), it appears that if the select
response returns anything other than 9000, it flags it as an error. This is
interesting because technically, the select response could be say 61xx which
means there is more data in the response and you would have to issue a GET
RESPONSE command to get the data - something that is not under the control of
the developer as all they can do is openLogicalChannel().
S3/S4 with Android 4.3 works for me so I'm wondering if something is fixed by
Samsung.
Thoughts? This is my understanding. Let me know.
Original comment by ada...@gmail.com on 30 Jan 2014 at 9:24