What are the application packaging requirements for signature services?

Application packaging requirements for signature services

PARTIAL LIST: REVIEW DOCUMENTATION FOR COMPLETE DETAILS.

All these requirements are already listed in existing documentation. They outline what is expected of developers when submitting a build for signage.No new requirements have been created. The generic packaging instructions are located at:

Smart Operation Panel – Start Guide – Installation – Packaging Process.

developerCD_location/doc/en/start_ml/120-03-0100.htm?ssdk_v3

1. Build must be UNSIGNED.
2. No developer signatures.
3. No other signatures present.
4. .dalp file name and application names MUST be the same.

Example:

myScanApp.dalp

myScanApp.apk

1. On dalp tag, href definition must match the .dalp file name. Please also be mindful of dalp spec designator. Some SmartSDK functions depend on this designator. Please consult existing documentation as you may need to change to a higher dalp spec than 3.0.

<dalp spec="3.0" version= "1.0" href="myScanApp.dalp">

1. On the resources tag, child tag apk href, the application .apk must match the name given in the .apk file.

                <resources>

                               <apk href="./myScanApp.apk" />

                </resources>

1. Ensure builds have proper versioning as they are updated.
2. Use ssdkpkg_checker app tool to check your application build is compliant, the ssdkpkg_checker application is available on the developer CD.

Developer CD location – Tool: ssdkpkg_checker.exe

YourDevCD_location\obj\tool\obj

Developer CD location – Doc: ssdkpkg_checker_e23004.pdf

YourDevCD_location\obj\tool\ssdkpkg_checker\doc

• Please always use the latest developer CD documentation as names, versions, and directory location may change. Retrieve the updated developer CD files accordingly.