search

frc1983 / seek-for-android

Automatically exported from code.google.com/p/seek-for-android
0 stars 0 forks source link

App compiled with Smartcard v2.2.2 cannot run on a device with v2.3.2 #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create an android app on Eclipse
2. Compiled with Smartcard 2.2.2 jar file
3. Run on an ICS device with Smartcard 2.3.2

What is the expected output? What do you see instead?
The APIs are backward compatible, and the app compiled with older jar file 
should be able to run on a device with Smartcard 2.3.2.

I'm suspecting the issue is caused by the change of the package name of 
android.smartcard.  

The problem was found on a real device.  I am not sure if the problem can be 
re-produced on an emulator.

Thanks,
Danny

Original issue reported on code.google.com by danny.w....@gmail.com on 10 Feb 2012 at 4:29

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
Yes, case closed.

Original comment by danny.w....@gmail.com on 22 Feb 2012 at 7:35

GoogleCodeExporter commented 9 years ago 
closed

Original comment by Daniel.A...@gi-de.com on 8 May 2012 at 2:03