 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The SDK certificates are for development or test purposes only.
Users will never have SDK certificates installed on their devices.
Therefore, when an application is ready to be released to users, it
must be signed with a certificate that is on the user's device. All
OEMs and mobile operators currently include the Mobile2Market
normal certificates on the devices they ship. Most OEMs and mobile
operators also include the Mobile2Market privileged certificates.
Therefore, unless your application needs to run privileged on a
device that does not have the Mobile2Market privileged certificate,
you should have your application signed with one of the
Mobile2Market certificates. For more information about the
Mobile2Market Program see this
To run your application on a device that does not have the Mobile2Market privileged certificate, you need to ask the OEM or mobile operator to sign your application.
 Note: |
|---|
| If the device security configuration requires signed binary files and the application binary files are unsigned, the application will not run. |