I've come to the point where I would like to install my BT-enabled
MIDlet to a cell phone. The packaged MIDlet runs well on the WTK 2.2
emulator. When i try to install it on a Nokia 6630, it gives me
(after going through all of the installation steps-"accept
installation","nevermind if it is not signed") an error-
AUTHORISATION FAILED (and, as it has just hit me, with an "s" - not
authoriZation failed - which might explain the no-search-results
anywhere on the topic...grin)
I have tried to canibalise the application to the point of excluding
the jabwt-related parts from the application for test purposes. The
problem dissapears-so it lays somewhere in the devices acceptance of
the Bluetooth API-enabled apps.
Here's my JAD file:
MIDlet-Vendor: Active Tools
MIDlet-Name: Blue Bridge
I experienced 'authorization failed' on installation as well, but not with JABWT.
In my case, third party source was including an interface from the com.sun.cldc package. Unfortunately, the WTK and nokia emulators support this package, which is not officially part of J2ME. The phones I tried do not support the package.
To solve the 'authorization failed' problem, I replicated the interface from com.sun.cldc in my own package.
I'm not sure if I have understood what you have said.
Do you mean that if I sign the application, I will be able to use classes that has package javax.microedition.sip (the JSR 180 Reference Implementation has classes that have (belongs to) package javax.microedition.sip)??
I'm not sure where I'm declaring permissions (Do you mean by including JSR 180 RI classes in the jar?)
you declare permissions without singning the app, which is theorically forbidden.
Where is this said? You can (and should) declare permissions even as untrusted 3rd-party. The MIDP device is then able to reject your MIDlet, when there are not enough permissions (ever).
The thread from activetools is one year old and probably fixed. This thread was hijacked by AlfredoRU. Do not think they are related in any way.
Originally Posted by AlfredoRU
I can't replicate the interface javax.microedition.sip because I don't have RI JSR 180 Source Code.
When your preverifier is configured correctly, the classes will move out of this namespace automatically. Nevertheless, make sure to check with Nokia first as using a RI often needs a different license to fulfill.