Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Curious are you behind a firewall by any chance?</p> <p>To consider adding firewall exceptions to have access for the eval/prod PPG then need to add the IP addresses below:</p> <p><strong>Eval:</strong></p> <p>68.171.224.57</p> <p>68.171.224.59</p> <p><strong>Production:</strong></p> <p>74.82.67.65</p> <p>74.82.67.66</p> <p>74.82.67.70</p> <p>74.82.71.70</p> <hr> <p>Another high level check before diving deeper; are you able to login into the <a href="https://cpadmin.pushapi.eval.blackberry.com/mss/CP_login" rel="nofollow">EVAL CP Portal URL</a> Your credentials might have been reset/expired, if so contacting blackberrypushservices@rim.com to help with access to the portal.</p> <hr> <p>On the application level, the app needs to connect to the InvokeManager signal at the beginning. </p> <p>onInvoked() function would first check to see the bb::network::PushService instance exists and the appID is stored. </p> <pre><code>connect(m_invokeManager, SIGNAL(invoked(const bb::system::InvokeRequest&amp;)), SLOT(onInvoked(const bb::system::InvokeRequest&amp;))); </code></pre> <p>The application will extract the push message from the invoke request by passing the invoke request into the PushPayload constructor if the action property of InvokeRequest matches the string constant BB_PUSH_INVOCATION_ACTION from the onInvoked() function.</p> <hr> <p>Do any of these suggestions work? Otherwise please explain more in depth which client/server code you have implemented and the bar-descriptor file's properties.</p> <p>Curious to know where are you located as there might be the likelihood of Push Service outage if Push Notifications suddenly stopped working.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload