08-01-2013 03:37 AM
I have created an app. its works well in most devices , but in a single device when i do some online registration it gives error: - The protocol specified is not supported by the handheld please try a different URL.
Actually on registration i have hit a url , after hiting this url it gives error.I cant understand what kind of problem is this.
Any guidence will be helpful.
Thanks in Advance.
08-01-2013 04:40 AM
You will need to find out the exact URL, including the connection string, that the device is trying to use in this case. Let us know what it is. You can blank out the company name if that is a security issue for you, so I expect you to tell us something like
I would guess here that your code is adding the connection string and has added one that is not actually supported on device.
08-01-2013 08:03 AM
Thanks for your response.
My code is here,could you please tell me what is wrong in this, this works fine on other devices:-
String urlFinal = url+";ConnectionTimeout=300000"
httpConn = (HttpConnection) Connector.open(urlFinal+ CS.getConnectionString());
08-01-2013 08:11 AM
I use the getConnectionString code from here in my CS class :-
08-01-2013 08:33 AM
Like I said, we need to know the exact URL you are using for the failing connection - the same URL and connection string can be valid on one device and not on another.
There are two things wrong with the connection processing you are using
a) You are not supposed to use the 'magic string' without approval from BlackBerry. The way to get approval is to apply for push service. Have a look at this page:
and specifically, these instructions:
"To use the BlackBerry Internet Service transport, you must sign up for the Push Service. For more information, visit http://developer.blackberry.com/devzone/develop/pl
b) the suffix
is only supported when using MDS and BIS-B connections. I suspect the problem you are having is that you connection string is retuning something other than one of these in this case, and then the processing is objecting.
But as noted, we really need to know the full failing URL to diagnose this problem. If we don't have that, then we are guessing.