Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry Push Development

Reply
New Contributor
Posts: 5
Registered: ‎09-14-2013
My Device: SQN100-1
My Carrier: Rogers

BIS Push Service with WebWorks SDK - INVALID_PROVIDER_APPLICATION_ID

[ Edited ]

Hi,

 

I'm trying to build a simple bb10 app using the webworks SDK. We already have an ios app using urban airship for the simple purpose of displaying notifications based on different types of alerts & warnings from our systems, so we're trying to duplicate the functionality as I just got a Q10 (and am so glad to be back on a proper physical keyboard with a great OS!)

 

The pushCapture sample sources (https://github.com/blackberry/BB10-WebWorks-Samples/tree/master/pushCapture) were used as my starting point and I've basically just hard wired my config into it. I'm trying to register for BIS push service.

 

Everything goes fine up until I call createChannel. The callback receives INVALID_PROVIDER_APPLICATION_ID as the error.

 

I find the nomenclature & documentation provided in the email that I got when I registered for my evaluation quite confusing. So, first can someone take a peek at my options being passed to blackberry.push.PushService.create:

 

{
    invokeTargetId: sample.pushcapture.invokeTargetIdPush,
    appId: "NNNN-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    ppgUrl: "http://cpNNNN.pushapi.eval.blackberry.com"
}

 In the email I received it says:

 

Application ID:

NNNN-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

 

PPG Base URL**

http://cp(your App ID ).pushapi.eval.blackberry.com

 

Push Port:

33940

 

This is where I get confused as I've seen another post on this forum that says after http://cp you should use just the CPID, but the email says app ID?

 

I'm also unclear on the push port. No where in the pushCapture sample is there a reference to port.

 

When I setup the service on Urban Airship I used the App ID for the Name, as their help text it was also called the App ID, the password that was provided in the email in the server section, and the PPG URL same as above. The service saved successfully and there's no errors listed.

 

Does anyone have any insight into the INVALID_PROVIDER_APPLICATION_ID error that I receive in response to createChannel?

 

Thanks!

Developer
Posts: 6,473
Registered: ‎12-08-2010
My Device: PlayBook, Z10
My Carrier: none

Re: BIS Push Service with WebWorks SDK - INVALID_PROVIDER_APPLICATION_ID

I think you should probably edit your post to remove the values that are specific to your own app, as private data. You could replace with things like NNNN-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx to represent the appid, etc.

To answer your question: I have a PPG url of http://cpNNNN.pushapi.eval.blackberry.com where the NNNN is the first four digits from my app id, and it's working fine.

Also the push port is irrelevant for BB10, so you can ignore it. (I asked that in another thread in the last month or so, if you want to search to find the post that answered it.)

Peter Hansen -- (BB10 and dev-related blog posts at http://peterhansen.ca.)
Author of White Noise and Battery Guru for BB10 and for PlayBook | Get more from your battery!
New Contributor
Posts: 5
Registered: ‎09-14-2013
My Device: SQN100-1
My Carrier: Rogers

Re: BIS Push Service with WebWorks SDK - INVALID_PROVIDER_APPLICATION_ID

Thanks. The values are available in plain text in the .bar file so I figured they weren't that private.

 

With the PPG URL just http://cpNNNN.pushapi.eval.blackberry.com I still get INVALID_PROVIDER_APPLICATION_ID.

 

I've tried both "NNNN-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" and just "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" for the appId too, but both ways return INVALID_PROVIDER_APPLICATION_ID.

 

Any other ideas? Might there have been an error during the setup of the eval account?

Developer
Posts: 6,473
Registered: ‎12-08-2010
My Device: PlayBook, Z10
My Carrier: none

Re: BIS Push Service with WebWorks SDK - INVALID_PROVIDER_APPLICATION_ID

I doubt there's an error, but have you verified the data by going to the admin portal? I think there's a link to that in the email as well.

The appid should definitely have the NNNN- in front as well. At least, mine has that and works.

(As for the private data thing, I'm not sure it matters but was just playing it safe. And .bar files are not available to anyone when the app is downloaded through BBWorld, so other than for your side-loading testers (if any) it is still private data.)

Peter Hansen -- (BB10 and dev-related blog posts at http://peterhansen.ca.)
Author of White Noise and Battery Guru for BB10 and for PlayBook | Get more from your battery!
New Contributor
Posts: 5
Registered: ‎09-14-2013
My Device: SQN100-1
My Carrier: Rogers

Re: BIS Push Service with WebWorks SDK - INVALID_PROVIDER_APPLICATION_ID

Turns out there was an error on my test account provisioning!

I replied to their initial email asking them to take a look and got a response today with updated details/credentials. I am off to the races now. Smiley Happy
Developer
Posts: 6,473
Registered: ‎12-08-2010
My Device: PlayBook, Z10
My Carrier: none

Re: BIS Push Service with WebWorks SDK - INVALID_PROVIDER_APPLICATION_ID

Borgstrom, good to hear that. Can you tell us how you discovered it and/or what the specific issue was, in case it happens to anyone else?

Peter Hansen -- (BB10 and dev-related blog posts at http://peterhansen.ca.)
Author of White Noise and Battery Guru for BB10 and for PlayBook | Get more from your battery!
New Contributor
Posts: 5
Registered: ‎09-14-2013
My Device: SQN100-1
My Carrier: Rogers

Re: BIS Push Service with WebWorks SDK - INVALID_PROVIDER_APPLICATION_ID

Your question about signing into the admin URL was the key.

 

I had tried when the Push eval email first arrived in my mailbox but couldn't even load the login form (I guess the site was having problems or undergoing maintenance), and I never retried after that.

 

After your last reply I tried again and found that my password they provided for the admin URL didn't work, so I replied to the email I received with the push credentials, 4 days later and here we are.