BlackBerry Push Development

[tbahr99]

I am trying to initiate a push from my debug-portal web site, but I get the following error.

code 2000

Invalid Notify URL: a notify URL is provided for a Push Service without a base notify URL 

I have my notification url set to /pushsdk/notification.  I have also tried just /notification as well as the full url to my site. 

Any ideas?

[tbahr99]

the url used when registereing for the app id needed to be modified to use new https and  port number.

[mdicesare]

 tbahr99, this means when you registered with RIM to use Push Service you didn't specify a base notify URL with them.Contact RIM to get a base notify URL specified for your application. Notification is only supported for Push Plus.

Basically when you register with BlackBerry Push Service you give them some base notify url like:

http://mycompany.com

Then when you setup your app in the DebugPortal you specify the relative part of the notify url like:

/notification

When the BlackBerry Push Service sends you a result notification it will combine the two pieces to get:

http://mycompany.com/notification

[mojiiz]

I have gotten same problem about "Invalid Notify URL: a notify URL is provided for a Push Service without a base notify URL". 

I can not understand about this. When I typed "/notification" in the URL notification with debug-portal, I still get the above error.

I use BIS type.

Please help me! Thank you so much

[massimo_olive]

I'll echo what someone previously said. When you signed up to use BlackBerry Push Service on the website - if you signed up for Push Plus service level then you were given the option to specify a base URL with the RIM servers, did you do that? To quote above: Basically when you register with BlackBerry Push Service you give them some base notify url like: http://mycompany.com Then when you setup your app in the DebugPortal you specify the relative part of the notify url like: /notification The error you are getting indicates the RIM push servers do not have a base notify URL setup for your push app. Contact them to get that setup.

[sneg]

Greetings!

I've encountered the same issue.

When was registering I specified the Source IP Adrees for Pushes and at first I thought that IP address will be used as a prefix for the Notification URL so I have to specify only suffix and BB Push service will get something like this:

http://45.64.123.54/sample-push-initiator/notify

where '/sample-push-initiator/notify' is the Norify URL field value when I send push messages with delivery confirmation.

So I wrote an e-mail to the address from which I got the BlackBerry Push Service Evaluation Credentials (pushservicesATrim.com). But I tend to think that I got auto-generated message with credentials from bot so noone will read my e-mail message on that address.

Could you please suggest any e-mail address where I can get help with this situation?

[massimo_olive]

Yes you mis-understood how it works - the source IP is different than the notify url. You are correct that you have to email them (unfortunately don't have an email address to give you) to specify a proper base notify URL.

[ekke]

just run into the same issue

as I registered for the Plus service there was no field to enter a base-notification-url

(made a screenshot)

credentials were correct for Service Type Plus

spent some time trying to specify the base notification url

now will send an email to RIM

thx

[sneg]

greetings!

ekke, please, keep up to date in your progress.

As for me I wrote a letter with my problem description to the person who asked me for more information about my app while I was registering for Push evaluation. That person redirected me to the devsupportATrim.com. At the devsupport  there was auto-response bot which asked me to purchase a developer support subscription. So, I currently stopped testing delivery notification feature hoping that on production account there will not such kind of problems.

[pouteau]

Hi ekke

Did RIM solved your problem with the base notification URL?

I've the same problem in 3 different evaluation accounts with push-plus.

Is this problem documented somewhere? I can't believe RIM could provide the credentials for using it's SDK with missing information.

Thanks so much!