Signing Apps for Sprint
Has anyone delivered an off-deck, signed applicaton using restricted APIs
I have read a number of posts on signing, and I have read the Sprint
Developer PDF tutorial on signing apps. I signed an app using the Sprint's
But, I do not yet understand why I have to enable the developer root on my
device. I want to deliver signed apps using restricted APIs to devices off
deck. My customers will not have enabled a developer root on their devices.
Downloading a signed app to my own phone is no different than the
experience I want to give my customers.
The PDF tutorial on signing is very ambiguous. It says I need a Certificate
from Verisign, but it also says I don't need one-- I can use a 3 year
certificate built into the WTK.
It would make sense if the root developer certificate was only for testing,
but I need the Versign Certificate for deploying off deck to my customers.
Is that the case? The PDF doesn't make this clear one way or another.
Or, is the whole signing issue only applicable to apps that will be hosted
on Sprint's deck. For off deck apps, the only option is to go untrusted,
and forego access to the restricted APIs?
Sprint's tutorial PDF is really great for the mechanics of creating a
signed app, but it doesn't address any of the deployment issues.
Thank you for your reply.
To unsubscribe, send email to firstname.lastname@example.org and include in the body
of the message "signoff KVM-INTEREST". For general help, send email to
email@example.com and include in the body of the message "help".