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

Android™ Runtime Development

Reply
New Contributor
Posts: 8
Registered: ‎07-23-2013
My Device: Dev Alpha B
My Carrier: BB
Accepted Solution

PUSH Eval Vs. Production URL

The application ported the Android need to register device on GCM to send the PUSH. This works with Eval URL, but on Production Fail! 

 

The android.cfg eval

<?xml version="1.0" encoding="utf-8"?>
<android>
   <push>
      <appid>XXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</appid>
      <ppgurl>http://cpXXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.pushapi.eval.blackberry.com</ppgurl>
	  <tokenprefix></tokenprefix>
   </push>
</android>

 

and the android.cfg production look like: 

<?xml version="1.0" encoding="utf-8"?>
<android>
   <push>
      <appid>XXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</appid>
      <ppgurl>https://cpXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.pushapi.na.blackberry.com</ppgurl>
	  <tokenprefix></tokenprefix>
   </push>
</android>

 this have a https and 3 digits in appID.

 

 

To production work need to publish on App World Black Berry or I can testing on my device?

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: PUSH Eval Vs. Production URL

Hi there!

 

3 quick things that should help:

1) You should only use CPXXXX in your URL, it looks like you may be using the full APP ID in the below examples which is incorrect

2) The client should always be 'HTTP'. Using HTTPS is only of the server side, using HTTPS on the client will preevnt the client from registering

3) If you have any other apps on the device using these push credentials (EVAL or PROD) please delete them then reboot the device before retesting

 

Hope the above gets this fixed for you!

Garett
@garettBeuk
--
Goodbye everybody!