Closed GoogleCodeExporter closed 9 years ago
Awkward topic - SCAPI releases are <release>.<major>.<minor> where major
changes (from 2.1.x to 2.2.x to 2.3.x) indicate no backward compatibility.
How to fix?
Original comment by Daniel.A...@gi-de.com
on 10 Feb 2012 at 7:21
Indeed, it is awkward explanation from me. ;-) In fact, the following case
occurs:
1. Create an android app on Eclipse
2. Compiled with Smartcard 2.3.2 jar file
3. Run on a Gingerbread device with Smartcard 2.2.2
The android app compiled with Smartcard 2.3.2 cannot run on a device with
Smartcard 2.2.2.
Thanks,
Danny
Original comment by danny.w....@gmail.com
on 14 Feb 2012 at 12:47
The Gingerbread device used for testing is HTC Amaze/Ruby device.
Original comment by danny.w....@gmail.com
on 14 Feb 2012 at 12:47
[deleted comment]
Th root cause was found. The org.simalliance.openmobileapi.jar was
accidentally included in the apk file of my app.
Case closed.
Original comment by danny.w....@gmail.com
on 14 Feb 2012 at 8:09
I suspected the Performance Tester also included
org.simalliance.openmobileapi.jar file within its apk file.
If it does, it will prevent the backward compatibility.
Thanks,
Danny
Original comment by danny.w....@gmail.com
on 15 Feb 2012 at 3:34
Correct, PerformanceTester links with org.simalliance.openmobileapi.jar to
ensure the tool also works with MSC_SmartcardService where no shared library is
available.
Close case?
Original comment by Daniel.A...@gi-de.com
on 21 Feb 2012 at 4:57
Yes, case closed.
Original comment by danny.w....@gmail.com
on 22 Feb 2012 at 7:35
closed
Original comment by Daniel.A...@gi-de.com
on 8 May 2012 at 2:03
Original issue reported on code.google.com by
danny.w....@gmail.com
on 10 Feb 2012 at 4:29