i'm trying to implement push notification for our Windows Phone apps. We have about 40, 50 games on Mobile Phones, each game we have about ~400.000 users on their device.
I read some tutorial about push notification for Windows Phone such as this (http://joashpereira.com/blog/2015/03/18/php-script-to-send-android-ios-and-windwos-phone-push-notification/), but there's a problem is that we can only send push notification to one device per request. If i use this method, our program will process very very slow.
It's not look like Android or IOS, where i can send notification to ~1000 devices per request. That's pretty easier.
Anyone know how i can deal with this problem? Pls Help, thanks.
[Answer to a comment in the question]
The send method of the NotificationHub returns a NotificationOutcome object. This object contains several informations. Also a TrackingId which is a unique identifier which has been generated by the Notification Hub. But at the moment you have no possibility (as far as I know) to get more informations.
You can use the TrackingId to contact the azure-support, when you have problems or questions.
The problem is, that azure don't send the notifications directly to the devices. Azure just sends it to the device specific notification server (APNS, GCM, MPNS), and this server decide about the time to send the notificaiton
Look at this page at the end (section 'Debug failed notifications/ Review notification outcome' or 'Review telemetry') for more informations.
Related
The logic of my project is that I have to send notifications from admin panel to users in web and mobile app at the same time! another meaning:
When the admin send a notification to John Doe I need John to receive the notification on website and mobile app at the same time!
Does FCM can do that ? or I have to send notifications for mobile app and do another thing for web to web which is admin to user on web??
FCM does not guarantee the timing of the receipt of messages. If you send two messages, they will very likely end up on the devices at about the same time, but there is no guarantee that they will. Also consider that one of the devices might not even be on at the time the message is sent - that message simply will not arrive until the device is turned on again.
But you can certainly write code to send as many messages as you need to as many devices as you want, and simply accept the results.
Yes, it's possible. That's the nice thing about Firebase services, so that you don't have to write entirely different code for the same functionality for each platform separately.
I am building my app using Ionic3 and Firebase. Here users can send eatch other messages. I want when a use sends a message to another ures he/she should get a notification in the phone even when the app is closed. I have no idea how to achieve this with Ionic3.
Any suggesions please.
I can see there are mainly 2 plugins for push notifications. cordova-plugin-firebase and cordova-plugin-fcm
At least I can fine some tutorial for cordova-plugin-fcm in the internet. There is no clear example of any wayout given for cordova-plugin-firebase.
You have to use the cordova-plugin-firebase and each time a user logs in using a device, a unique device ID will be registered with respect to that device. This device ID is used to send notifications. Make sure to handle this (device ID), every time a user logs in & logs out. If you do not remove the device_id from the database when a user logs out, he will continue to receive notifications.
You have to use a cordova-plugin for sending push notifications. One of the many available plugins is: cordova-plugin-firebase. This one is a good fit for Ionic 3 because there is an ionic-native wrapper available.
For sending the push notification you can use a third party service (there is also one offered by ionic) or you can send them yourself from your backend.
I have developed an android application with the Parse push notification service and I can send notification from the Parse website.
How can I send push notifications through my own website using ASP.net? Is there any way?
I checked the Parse documentation but i get confused, I would really appreciate it if someone would help me.
Thanks
I ran into similar confusion. I wasn't even sure how to properly setup the user so that I could send a push notification directly to them. Then I found the following post:
Channels and Targeted Push Notifications
Note the last item under the Channels heading:
Most apps might find it useful to have a channel for each user so that
they can send messages to a user across all their devices and have
users follow others in the app.
So, now I know that I should subscribe each user to a channel that uniquely identifies the user (e.g., the 'bobsmith#foo.org' channel).
After I have subscribed the user to their channel, I can call Parse's REST API via my ASP.NET application. See Sending Pushes in the Parse REST API Developers Guide.
For an ASP.NET/C# example of how to submit a push notification check out this answer.
the thing is that we already have a backend that handles all the push notification process. From device registration on our DB and notification handling on the device and notification sending to Apple and Google servers...Looking into Parse I saw that it has a lot of things that will take us a lot of time to develop but mostly on the process that sends the notification to the devices.
So...I need to know if devices can register in our backend, then from our backend to Parse and then send push trough Parse. Is this possible? Image below.
Thanks!!
Yes this is possible. You'll need setup your push certificates with Parse and register each device's push token with a Parse Installation object's deviceToken field for it to work. All this is documented on their web site. You'll need to setup a Parse User object for each user as well as each Installation is associated with a single User.
I want to collect device attributes and send them to the mdm server using push notification.
Steps involved are:
create a configuration profile with mdm payload
get device token
use apple push notification service to send a notification to the device.
get back device attributes
do same with multiple devices which the company manages
Questions:
Will the user always need to act on a message or I can send a message onto the device without user action and get the work done?
Do I need an app on the device to send back the token?
It sounds like you're trying to use push notifications to poll iOS devices and return information.
Push notifications do not provide a mechanism to execute code on a device without user interaction. You would have to have an application loaded on the device, and the user would have to click through from the notification to your app.
In iOS, applications generally don't run unless the user is actively interacting with them. There are a few exceptions (e.g. background audio.)
You do need to have an app running to get the device token. You call registerForRemoteNotificationTypes. See APNs docs for more information.
Edited to add more information:
Looks like the MDM protocol uses push notifications to do just what you describe. However, there's nothing about it in Apple's "Local and Push Notification Programming Guide" (linked above).
Apparently Apple keeps tight control over the MDM documentation (see here and here).
However, I did find this paper from blackhat describing how the system works.
My earlier point about not executing arbitrary code on a device without user interaction still applies. There's a finite set of commands that can be executed (see Appendix A).
I came across this question when searching for iOS push notification access payload without user interaction - Just want to add that, in iOS 7 and above, it is possible to send silent push notifications to app, and app can process them without user interaction.
However, I've also found some discussions saying that the silent push notifications are not delivered reliably, in this SO post. That's why I'm still looking for alternate ways to retrieve payloads of the normal remote push notifications. Doesn't look like there's a way.