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

Web and WebWorks Development

Reply
Contributor
Posts: 11
Registered: ‎04-11-2014
My Device: Z-10
My Carrier: none
Accepted Solution

Debugging 10114 errors on push

[ Edited ]

I'm brand new to Blackberry development and am trying to get the pushCaptureBasics example running using WebWorks 2.0 and a Z-10 device.

 

When I run the pushClient and click "Force Register", I see:

 

[13:44:13] Failed to create Push Channel: 10114

 

I'm connected over wifi and the device has never had a SIM in it (but I know I can talk to Blackberry because the device downloaded the update to 10.2.1.2102.)

 

I'm using the following URL in pushClient.js and pushInitiator.js:

https://cp4668.pushapi.eval.blackberry.com

 

My application ID starts with the same 4668 and is valid from April 7, 2014 through August 7, 2014 according to the content provider admin portal.

 

It looks as if pushInitiator works fine using the same URL that causes the error in pushClient. At least, I get a:

[14:14:52] PushInitiator success:200

when I press "Send Push".

 

How do I diagnose this error? (And how do I move this message over to the push forum, which seems more appropriate? :-)

 

Retired
Posts: 1,561
Registered: ‎04-12-2010
My Device: BlackBerry Z10
My Carrier: Bell

Re: Debugging 10114 errors on push

[ Edited ]

Hi there, according to the docs this is an "Invalid PPG URL" error:
https://developer.blackberry.com/html5/apis/v2_0/blackberry.push.pushservice.html#jbo1385148936274

Can you please try with the HTTP protocol? (The URL you are referencing is HTTPS.) Note the differences in the URLs in Step 8 and Step 9 here:

https://github.com/blackberry/BB10-WebWorks-Samples/tree/master/pushCaptureBasics#how-to-build


Erik Oros | @WaterlooErik | eoros@blackberry.com | Developer Issue Tracker

If a reply has answered your question, please click Accept as Solution to help other visitors in the future.
Contributor
Posts: 11
Registered: ‎04-11-2014
My Device: Z-10
My Carrier: none

Re: Debugging 10114 errors on push

[ Edited ]

Thanks, Eric. I replaced the https: URL in pushClient.js. (I note that the URL is https: in pushInitiator still, according to the docs.)

 

In pushClient.js, I'm now using:

'ppgUrl': 'http://cp4668.pushapi.eval.blackberry.com'

 

And in pushInitiator.js, I'm using:

'ppgUrl' : 'https://cp4668.pushapi.eval.blackberry.com'

 

Then I deleted the two apps on the device and rebuilt using WebWorks 2.0 in Debug mode (pushInitiator first, then pushClient).

 

Sadly, I still see the same error from pushClient - "Failed to create Push Channel: 10114".

 

My application ID also starts with 4668 and is valid from April 7, 2014 through August 7, 2014 according to the content provider admin portal. This was generated by my manager (who has a different email address than I do; might the fact that I'm using his credential cause a problem?)

I have read (on https://github.com/blackberry/BB10-WebWorks-Samples/issues/60) that the push permission is required for my signing key. Is there a way to verify that I have that?

 I've got the following plugins in my pushClient:
com.blackberry.invoked
com.blackberry.push
com.blackberry.utils

I've also disabled web security and added _sys_use_consumer_push to the config.xml for pushClient.

Thanks again for your help!

Retired
Posts: 1,561
Registered: ‎04-12-2010
My Device: BlackBerry Z10
My Carrier: Bell

Re: Debugging 10114 errors on push

You shouldn't need to add any extra permissions. When you import the extensions into your WebWorks project, these should be automatically set. For reference, I have the following in plugins added:

* com.blackberry.identity

* com.blackberry.invoked

* com.blackberry.push

* com.blackberry.utils

 

utils is added automatically, I believe, and identity is to be able to initaite pushes to the device (it's not needed for the actual configuration of the push service.)

 

So really, invoked and push are what would be required. For reference, importing is through the webworks command:

webworks plugin add com.blackberry.push

webworks plugin add com.blackberry.invoked

 


Those two should account for the configuration part; though you do need to manually fill-in the values of your pushclient.js with your own credentials, which it sounds like you have.

 

	'ops': {
		'invokeTargetId': '@@@@@@@@',
		'appId': '@@@@-@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@',
		'ppgUrl': 'http://cp@@@@.pushapi.eval.blackberry.com'
	},

 

Can you fire this issue as an email to BlackBerryPushServices@blackberry.com and CC me (eoros@blackberry.com) on there?

 

Let them know that the push server is identifying your PPG URL as invalid, and ask whether there are any expiries or flags on your account. I'm not expecting there will be, but it's good to rule that one out. Let them know which PPG URL you are using and that it is for the client side specifically.

 

If we find that the issue still persists, I'll ask the team to re-create the credentials because the extensions/JS configuration is all that really should be needed. You don't need extra permissions on your keys to perform this type of BIS push.


Erik Oros | @WaterlooErik | eoros@blackberry.com | Developer Issue Tracker

If a reply has answered your question, please click Accept as Solution to help other visitors in the future.
BlackBerry Development Advisor
Posts: 4
Registered: ‎08-17-2012
My Device: 9790
My Carrier: Telus

Re: Debugging 10114 errors on push

Andrew,

Were you able to get this working?

As Erik mentioned i would contact that DL and see if there are any issues on the server.

 

In the mean time, maybe you can recheck that the PPG url you are providing is correct?

Please see the description below and ensure you are inserting the correct "content provider ID" you received when registering into the <cpid> portion of the URL.

 

// This matches the URL used to register with / unregister from the BlackBerry Push Service (BIS) PPG.

// For eval, this would be http://cp<cpid>.pushapi.eval.blackberry.com.

// For production, this would be http://cp<cpid>.pushapi.na.blackberry.com

// Replace <cpid> with your content provider ID (that you received when registering).

// This applies to consumer applications only and will be null for enterprise applications.

 

As a side note, i would ignore the fact that the PushInitiator shows "success" with the same URL. From what i recall, that sample push Initiator shows success no matter what you enter. I would focus more on the client for now and registering before you attempt to send a push with the Initiator.

Contributor
Posts: 11
Registered: ‎04-11-2014
My Device: Z-10
My Carrier: none

Re: Debugging 10114 errors on push

[ Edited ]

Hi!

 

I haven't been able to get this working yet. I have contacted BlackBerryPushServices@blackberry.com (sent email on Tuesday), but haven't seen a response from them so far.

 

I'm guessing that my CPID is the same as the first four digits of my app ID (before the dash). That's the number I was sent, so I believe I'm using the correct CPID in the URL: http://cp4668.pushapi.eval.blackberry.com.

 

BlackBerry Development Advisor
Posts: 4
Registered: ‎08-17-2012
My Device: 9790
My Carrier: Telus

Re: Debugging 10114 errors on push

Might be worth it to try and track down the email you would have received when you registered, just to be sure.

Otherwise, that DL should be able to help you.

Retired
Posts: 1,561
Registered: ‎04-12-2010
My Device: BlackBerry Z10
My Carrier: Bell

Re: Debugging 10114 errors on push

Just to confirm, every CPID I've seen has matched the first digits of the App ID (i.e. the digits before the dash - character.) These can be 3-4 characters.

 

I've followed-up on the email with our Push team to see if we can escalate a response.


Erik Oros | @WaterlooErik | eoros@blackberry.com | Developer Issue Tracker

If a reply has answered your question, please click Accept as Solution to help other visitors in the future.
Highlighted
Contributor
Posts: 11
Registered: ‎04-11-2014
My Device: Z-10
My Carrier: none

Re: Debugging 10114 errors on push

[ Edited ]

Thanks again, Erik. I have confirmed the CPID in my original email. Now I'm awaiting a response from BlackBerryPushServices... hopefully they can resolve this.