RIM Push at all

Similar Questions

• RIM Push Notifications - connection limit

  Hello

  I send the rim push push through my BES BlackBerry.

  I received notifcation to another server. This server another wait notification.

  It works well, but it stops to work every day.

  The BES stops to send notifications to the other server. (even if the push message has been successfully delivered).

  I think that there is a connection limit or something like that.

  You have an idea?

  Looks like I'm wrong, we do not see a response from the device:

  <2011-01-28 10:35:36.095 CET>:[45819]:::
  

  But logging still does not show an attempt to notify the server and yet some information is missing. Could you please allow both verbose and logging HTTP? Also please let me know:

  -What size of shoot you send

  -The frequency that they are sent

  -Are there many instances of MDS - CS in your environment?

  -Try to push to another user, after that this problem occurs, you receive a response?

  -You send all right pushing every time during this test?

• PAP pushing against RIM Push

  OK so I have read the guide to development of the browser and I noticed that RIM supports push PAP and implementation of the Push RIM. For me, they seem to do the same. The two support Cache, push as well as cancellation and requests by State channel. The only difference I see is that PAP Push uses the XML format isn't the case to push the rim.

  Anyone can make comments as to why we have to choose one over the other.

  The characteristics are very similar.  It depends especially if you prefer to use HTTP or XML headers when creating the push.

• Question on the RIM push service

  (1) is available all over the world, as long as you have a BB?

  (2) don't yet get it even if you do not have BIS?

  Hello

  (1) Yes

  (2) push button a only works for devices with a BIS connection.

  Paul

• FilePicker crashes NDEF NFC push for all current application registered NDEFMessageBuilders

  Using Blackberry 7.1, in a variety of devices:

  We have an application with some screens recorded as NDEFMessageBuilder and NDEFPushStatusCallback. They correctly return the NDef message and it all works perfectly and wonderfully in all devices. Once you start using a FilePicker and navigate to any folder inside the filepicker, the application starts to be unable to pass anything througt NDEF/NFC, even the "buildNDEFMessages" is not called.

  I tried to cancel the registration and re-registration of the NDEFMessageBuilder, placing the NDEFMessageBuilder in another class or same bundle... At tried all combinations possible on register/unregister, in all moments of possible timeline at the opening of the FilePicker. But nohing help, the application cannot send NDEF/NFC after opening the filepicker and access to a folder.

  Once I Close / restart the app it sends NDef perfectly but, once you re - open the filepicker and access a folder inside the filepicker he keeps failing.

  Curiosity: After the FilePicker breaks the NFC/Ndef, it starts sending the packages throught NFC LLCP FRAME_REJECT and all other applications work fine... but whoever opened the FilePicker aren't...

  After a lot of research... it seems that the LLCP was a senior associate with two connect packets inside... one for the transfer and the other for the connection of the snep.

  Maybe opening the filepicker here where the posibility to use nfc conncetion transfer or use the registered app snep connection, that is why the blackberry device returned an aggregated setting...

  Some devices implement these packages aggregated and not others...
  obiously I don't have he put up in my library nfc...

  I will implement as soon as possible.

  Sorry for the inconvenience...

• Don't get is not to push the checks on the server

  Hello

  I have a server that uses the BlackBerry push format https://developer.blackberry.com/devzone/develop/enterprise/enterprise_blackberry_push_format.html to send push messages to our customer. It works very well.

  I've added the following headers to POST messages when sending from the shoot:

  X-Rim-Push-reliability: the value 'transport' and

  X-Rim-Push-NotifyUrl: point to a POST method on a web service, I have running. This is the signature of this method:

  [OperationContract]
  [WebInvoke(UriTemplate = "Feedback", Method = "POST")]
  [CorsEnabled]
  void PostFeedback();
  

  Now, even if outbreaks are sent fine to the device, the notifyURL never is called from our MDS Server. I checked that the service is accessible from the BES.

  Inspect newspapers MDAT on the BES I see these lines:

  Notify the URL = , pushId = 3, 2b0a9a9e, result code = 400 net.rim.protocol.iplayer.e = destination: Connection Timed Out, State = timeout >

  Is the 400, indicating that the surge has expired or that the HTTP request to my service has expired?

  What do I need to configure something on the BES? The BES is running 10.2.4.14 version and the unit is a Q10 running latest OS 10.3.1.

  OK, I realized that things went wrong:

  1. all docs BB (https://developer.blackberry.com/devzone/develop/enterprise/enterprise_blackberry_push_format.html) that the service must expose a POST method for push notifications. I inspected newspapers monitoring WCF and, to my surprise, I discovered that the SDM actually makes a GET request!
  Then, that it is a GET request, I changed and I started to receive notifications.

  But now, I was faced with a different problem. I've been putting X-Rim-Push-reliability in transport, which suggests that no acknowledgement of the thrust is required by the app, but I was still getting 400 on the push notification, which suggests that the push has never reached the device (even if she did).

  2. I updated the client application to acknowledge receipt of the push notification, and now my service becomes 200 for the status of push.

  You should really update your documentation on this! I spend several hours trying to figure what was wrong on my side until I realized that the docs were outdated or false! This is not the first time that I'm having problems with your API... And the fact that I almost never get all the answers here is discouraging... Please fix this

• Notifications push and wifi

  Hello

  I have two test devices (the two Torch 9800) to the Agency, one with a data plan and the other without.

  The one with the data plan receives notifications of type push very well. But without, even when connected to wifi, does not push at all.

  It doesn't bother me too much that I'm guessing that most of our clients have a data plan (which I assume is required for growth), but my question is:

  If someone with a data plan is connected to wifi, will they get notifications of type push? No matter what message transport is used when registering the client machine for the BIS push? Or the mode of transport importance only when it receives impulses? Maybe both?

  Any help would be greatly appreciated.

  Hi pg1181,

  It's my understanding of the case. To get push notifications, you must have access to the BlackBerry network, which you can do with a BlackBerry data plan. But as long as you have an active BlackBerry data plan, you will continue to receive push notifications if you are connected via the cellular network or wifi.

  Without a BlackBerry data plan, there is no way for RIM push messages on your phone, and so the apps will rely on polling to get new notifications. Then you will be informed of updates, messages, etc. on the scheduled polling period only (depends on the application refresh interval).

  I hope this info helps!

• onNotification not called (SDK to push at low altitude)

  Finally my notification of base URL has been saved

  Thanks to [email protected]

  no more error that the base url is not available if the ppgNotifiedRequestedTo parameter

  My basic notification url: http://my-server.org:nnnn /

  My ppgNotifiedRequestedTo: /pushnotify

  I extended PapServiceImpl and implemented onNotification:

  public class PapNotificationService extends PapServiceImpl {
  
      @Override
      public void onNotification(ResultNotification resultNotification,
              Map notificationParameters)
              throws PushSDKException {
          logger.debug("On Notification ###################");
      }
  }
  

  I extended BasicNotificationServlet and implemented the getPapService simply return a new PapNotificationService (see above):

  public class PushNotificationServlet extends BasicNotificationServlet {
  
      /* (non-Javadoc)
       * @see net.rim.pushsdk.pap.web.BasicNotificationServlet#getPapService()
       */
      @Override
      protected PapService getPapService() {
          return new PapNotificationService();
      }
  
      @Override
      public void doPost(HttpServletRequest req, HttpServletResponse resp)
              throws ServletException, IOException {
          logger.debug("doPost called");
          super.doPost(req, resp);
      }
  
  }
  

  I tested this Servlet of the browser:

  http://my-server.org:nnnn / pushnotify

  and as expected make me:

  16:40:38.208 DEBUG [o.e.b.p.b.i.PushNotificationServlet] doPost called
  16:40:38.224 INFO  [net.rim.pushsdk.pap.PapServiceImpl] PushSDKException caught while receiving result notification:
  net.rim.pushsdk.commons.PushSDKException: No XML content to parse; document is empty
  

  If the servlet is working

  but its never called so by pushing. shoot is done properly with QualityOfService DeliveryMethod CONFIRMED and ppgNotifiedRequestedTo has the value

  PapService papService = new PapServiceImpl();
  papService.setHttpClient(client);
  papService.setPushSDKProperties(pushProperties);
  .....
  pushMessageControl = new PushMessageControl(
      idGenerator,
      PUSH_APP_ID,
      PPG_NOTIFY_REQUESTED_TO_URLPART,
      addresses);
  .....
  response = papService.push(
      PUSH_APP_ID, // BIS username
      PUSH_APP_PW, // BIS pw
      PUSH_APP_ID, // BIS port
      pushMessageControl, // PUSH msg attributes
      papContent); // the content
  

  questioning of the State, I get in WAITING and a few seconds later CONFIRMED

  but I don't get any Notification

  no idea what could be the problem?

  THX

  GOD

  BTW: I'll publish my JavaSE whole - solution of low level as Open Source (EPL) for easy start with PushServices without installing springsoftware etc. all running inside the eclipse.

  the problem is now solved

  thx for help - RIM problem was

  ...

  My basic notification url: http://my-server.org:nnnn /

  ...

  where I am listed as notification to the RIM base url:

  http://my-server.org:8081 /.

  Important notice to evaluate all Push Service Plus: only Ports 80 and 443 are allowed as base URL of notification .

  otherwise the notification messages find a way out of RIM Push Server

  According to RIM documentation is added for this

• Impossible to get notifications of type push on BlackBerry using the HttpPushDemo application

  Hi all

  I'm currently running client application HttpPushDemo Simulator and I'm able to get notifications sent from the server application successfully.

  Now, I run the client application even on my Blackberry which is active BES but I'm not able to get push notifications.

  I did due to changes on the application server
  -DEVICE_PIN = device PIN No. ("26DEA1CF");
  -DEVICE_PORT = "100";
  -MDS_PORT = 8080;

  Domestic GetPushURL()
  -_pushURL = new URL ("http", the address IP of BES or host name, MDS_PORT, "/ push?") ("DESTINATION =" + DevicePin + "& PORT = ' + DEVICE_PORT + ' & REQUESTURI = address IP BES or host name");

  Domestic PapPush()
  -String mdsHost = BES IP address or host name.

  When I run the server application it gives me an IOException with response code 400.

  I also checked the MDS status page using http://: 8080.

  Can someone tell me who supplied the information is correct, and what else should I check to make sure that the application will run on the device.

  Thanks in advance.

  Hello

  I am now able to receive notifications on my mobile client.

  Just "X-RIM-Push-reliability-Mode" property has commented on or changed its value to 'APPLICATION' in order to 'TRANSPORT' inside the postData() method.

  for example conn.setRequestProperty ("X-RIM-Push-Reliability-Mode", "TRANSPORT");

  Note: this works for the push RIM only format. Yet I am not able to receive notifications on device with push PAP format.

  Thank you all.

  -Kone

• BlackBerry Smartphones Can I have a blackberry and not pay for all the internet services?

  Hi I'm new on this and my t-mobile phone that I broke and I looking to upgrade to something that will help me to stay a bit more organized, but are unwilling to pay for the service package that comes with the purchase of a blackberry from t-mobile. I know that I could get one on craigslist or ebay or something and I was wondering if I could just put in my Sim Card and it would have all the functions without the internet and emails. All I really want to the phone is easy navigation, good organizer, easily send SMS and calls. Thanks for the help! -Sully

  Sully, Hello and welcome to the Forums of Support BlackBerry.com.

  Sorry, no. Without the BlackBerry data Plan, you will get very little data from the device functions... voice and SMS, Yes. Calendar, contacts, etc., Yes. No RIM push email.

  You can use the Opera Mini browser for the internet with the setttings TCP active for a browser for free... just watch your billing and ensure that you are not charged.

  http://www.BlackBerryFAQ.com/index.php/What_are_the_TCP_and_APN_settings%3F

• Contacts/Mac OS x Server Push Notifications and macOS strange behavior Sierra Server

  I have Sierra macOS Server 5.2 and the same "user01" account configured in Contacts.app on two computers of macOS Sierra 10.12 and a device unique 10.0.2 iOS (iPad). My expectation is that change on a device (for example to add a new contact) is in a few seconds on all other devices that are configured with the same account. However, this is not always true.

  Invocation of manual synchronization (quit Contacts.app, start it again) still works correctly. However the changes on a device (for example to add a new contact) are not pushed to all devices. Usually, the change is pushed and data are synchronized immediately only to the last device configured with the account. Other devices configured with the same account are not automatically updated.

  There are certificates valid push (push works on all devices, it's just seem to depend on which is configured earlier and who later).

  The same applies to the Calendar.app calendar events using the Protocol CalDAV, push calendar notifications and server for macOS.

  In the newspaper of apsd, on Mac OS processes, can even be considered that push message arrived at the apsd process, he was in the process of Contacts. The difference is, however, that AddressBookSourceSync process is not upload all the changes from the calendar server and macOS Contacts. Sometimes, the push message does not seem to happen Server NPP (based on the apsctl for the apsd log tool).

  The problem has been caused with a single device by push-topic Subscribe APNS.

• Acceleration of approval of push notification service

  I wonder if there's a place I can reach out to the acceleration to the top of my push notification service application. Five days seems a bit long to test the existing integration with my Android build.

  Anyone has any advice to help get things moving?

  I checked with the team to push and all pending requests have been processed.  Then you should be all set.  If you have not received notification, check your spam filter in case the message was taken there.

• Detect programmatically push browser string

  
  

  You can do so by setting the monitoring of the push.  To do this, you will need to use the X-Rim-Push-priority header.  You can read about it in the browser BlackBerry - the content found here Developer's Guide:

  http://NA.BlackBerry.com/eng/support/docs/subcategories/?usertype=21&category=BlackBerry+browser

• push does not work after about a month

  Hello

  I may receive the push on the device a month ago. But when I try today, I couldn't get the push on the device no more.

  Server side, I saw this response from your server push:

  "" http://www.openmobilealliance.org/Tech/DTD/pap_2.1.DTD"> <> push-id ="pushid"- sender address ="http://cp4348.pushapi.eval.blackberry.com/mss/PD_pushRequest " -nom_expediteur =" RIM Push-Data "response-time Service =" "2013-12 - 20 T 18: 58:21Z" > "

  But I can't receive the thrust on the device.

  Thank you.

  VNet wrote:
  Furthermore, is it possible to change background app before or auto-start the app and bring it to the front once the application gets the push? I think that this can be done in 10.0/10.1, we can do it in 10.2? If so, is there an example of code to do this?

  No, applications are not capable of leading themselves. The preferred route would be to add a notification on the Hub, which the user can use to launch your application.

• notifications of type push (bb10) has not received

  Hello!

  After having my job to push service, he stopped.

  I can save the user, create the chanel and everything works fine, but when sending notifications, he said everything is ok, but nothing is received the alpha device.

  It worked, maybe it crashes after the latest OS update, not sure.

  Any idea on what is happening?

  This is the answer to push:

  http://www.openmobilealliance.org/tech/DTD/pap_2.1.dtd">http://pushapi.eval.blackberry.com/mss/PD_pushRequest" sender-name="RIM Push-Data Service" reply-time="2013-01-16T20:44:24Z">
  

  For the slog2, you will need to install the Momentics IDE which is installed with the native SDK 10 BlackBerry. Install this IDE will give you the tools you need to access the device.

  http://developer.BlackBerry.com/native/download/

  1. in the QNX Momentics IDE, based on the target browser, right click on the target of the device. ClickLaunch SSH Session.

  2. in the terminal that appears, do one of the following:

  a. to view logs of current slogger2, type slog2info.

  b. to display the output in real time for the processes that are being debugged (for applications that are running in development mode), type slog2info - w.

  c. to display help on slogger2, type slog2info h

  SSH to the machine and run it:

  slog2info >/tmp/slog2.txt, and then send the slog2.txt

  We are able to determine the root cause of the problem in this thread that was the bar needed to be updated to have XML descriptor:

  
        APPLICATION
         
             bb.action.PUSH
             application/vnd.push
         
  
  

  However, when the BAR file was generated META-INF/MANIFEST. MF was lacking the entrances to invoke target which led to the discovery of the root cause of the problem which was the SDK of AIR PlayBook instead of the SDK software BlackBerry 10. Once the correct SDK has been used push starts happening on the device.