I have created an account on Xtify for receiving push messages via BIS on Blackberry. Sample application that ships with Xtify SDK works fine and registration requests' responses are successful(As shown on the sample app screen). Finally it prints to the screen that it is listening for incoming messages. When I send a notification from web console it says "Notifications were sent to blackberry users:". but no push message is received. Also note that I have used BlackBerry server SDK to receive push messages which I was writing for another application and it worked really well.
Since I am sure that the client application works, I tried with this service "http://notify.xtify.com/api/1.2/pn/push" to send push messages programmatically. Still it keeps giving this error whatever the value I put in there. I tried device pin, and other keys too. But still the same error.
Any help?
Related
I'm using "twilio_voice" for a flutter application for generating and receiving call from app to real number and vice versa.
When I'm trying to call to a real number from app it's working fine. But when i'm trying to receive call within the app, it's not working.
When I checked at Twilio console I found "Error 52134 Invalid APNs device token".
I have already created the VOIP certificate in Appstore console and also generated a Push Credential in Twilio console. The SID also used in the backend.
In my applog I also found "Successfully registered for VoIP push notifications." as a confirmation.
But still not working.
After your app has register for the push notification, you will need to create a binding with the Push Token to the Twilio server. For that you will need an intermediate server of your own(Can be a Node js/PHP/Python server application). First you will make a rest api request to your own server from the app. The server application will send a binding request to Twilio server. Once that is done, you will receive push notification every time there is an incoming call via didReceiveRemoteNotification() delegate in AppDelegate.
For the server application sample and Rest api sample for iOS app, follow this documentation from Twilio:
https://www.twilio.com/docs/notify/register-for-notifications-ios
Got the solution.
The issue was in the registering device. I was sending fcm token to the server for registering device. But after changing it device UUID, it worked.
Also point to be noted that, you will need a different SID from Twilio for development and Testflight. SID from Sandbox credentials won't work if you running app from TestFlight.
I am working on one VOIP-based application where one user calls another user everything works fine like calling and all.
But whenever I didn't log out from the application and directly uninstall the application at that time any another user tries to call the user who already uninstalled the application. At that time backend get a successful response from apple (i.e. 200 Success). Why won't give an error if that app is not installed
Actually, we need to give some specific alert to the user who called the person who already uninstalled the application but we are unable to find from backend too that the voip push failed.
One another thing just for testing : We tried to send FCM silent notification too which works synchronously with VOIP notification but in that too FCM gives success in backend while app already uninstalled from device.
If anyone facing same issue and having solution regarding that then please let me know.
In the short term, Apple doesn't know that the user has uninstalled the app, so it accepts the push.
Pushes are delivered asynchronously (Since a device may be offline when you send the push; it will be queued for delivery later).
The APNs cannot provide immediate feedback on the delivery of your push. The 200 status simply means that the push was successfully accepted for delivery.
Eventually Apple will determine that the push token is invalid and return a 410 response. At that time you can remove the push token from your database.
In the short term you can detect if the device doesn't respond to the VoIP push in a reasonable time frame and return a "call failed" or "recipient unavailable" response to caller.
i am developing an application with ionic 5.
The application receives push notifications from firebase without any problems.
But every time I install the application on IOS it asks me to allow the receipt of push notifications, if I accept (as normal) a warning message is displayed.
The message informs me that if you select no, I will not be able to receive notifications, but I have selected yes.
Is there any way to handle this?
That message is handled by the operating system, did you have the same problem?
I am trying to implement web push notifications in my chrome browser using a .net MVC web application and service workers.
I am able to subscribe to the push service and get the subscription object from web app.
But when try to send a notification message from the server, the notification doesn't get displayed.
But if I debug the service worker by placing a break point inside the push event handler function, the break point is hit and if I step through the code the push notification is displayed.
I am not sure where the problem lies. Please help.
Finally found out what was causing the issue.
I subscribe from my local system, leave the browser open and send notification by connecting to a VM through MSRTC. The reason the notifications didn't get displayed was the MSRTC application was the active program and not my local system.
If I send notification from a different system, my browser receives and displays it.
Thanks for your replies.
I am building a very simple messenger app just to get my feet wet with this type of app. The general idea that I came up with is: Client 1 types a message, sends to client 2. Message goes to my tcp/http server, then the message is sent to Client 2. I am not sure however how this last step happens.
How can the server locate the phone and push the message to it? Should the app check every few seconds to see if they have a message waiting? How would you do this if the app is suspended (background)?
Would this qualify under background fetch under UIBackgroundModes?
The app regularly downloads and processes small
amounts of content from the network.
You can do it remote push notifications using apple's APN (apple push notification). Essentially, once the server receives the http/tcp message, it has to do a push notification to the device 2 thru apple's apn server. More information here