There is a bug in the RIM Code Module Manager installation APIs that causes newly installed apps to have no permissions until the next reboot.
The suggested fix is to be working for a company that does around $100m a month of business with RIM; this worked wonderfully, and ensured my problem was fixed by developer support in no time.
Seriously? Ok the actual solution (found via above method) is to use some private RIM APIs for which you need special JAR goodness; contact dev support and ask them nicely about it.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment