I can now get the Registration ID from the mobile and the push notification is working properly. I can access the list with the help of REST APIs but what I want to know is how to access the Registration ID list in the Bluemix itself where I'm not creating any tag.
As you stated above, with the Bluemix Push Notification Service you can use REST APIs in order to gather the deviceIds from registered devices. We also provide a document that allows you to test these APIs directly in the browser:
https://mobile.ng.bluemix.net/imfpushrestapidocs/#!/devices/get_apps_applicationId_devices
Currently we do not provide a list of registered deviceIDs via the Bluemix dashboard, but you can use the Monitoring tab in the Push Notification dashboard to gather some statistics on the number of registered devices.
Related
I am building an admin app for woocommerce site, i want to send a push notification from WordPress to my application when new order is placed on website with orders details ,
I didn't find any way to do it is there any salution you can give ne ti achive it.
I have tried onesignal plugin with firebase but it allow only to send push notifications for post update etc, other way also give this service for other task but not for orders receiving.
you can grab the order from Woocommerce with This package
then create your notification function with Local Notifications
and also FCM firebase messaging
after that you can create a function in your Firebase to push notifications to your devices
with the right method it is symple.
I was using an instance of the Push service in my app, but now I want to move my app to a different organization.
I found this link that saying that the Push service is discontinued: https://developer.ibm.com/bluemix/2015/12/15/important-mobile-services-announcement/, so I have migrated from the Push service to the IBM Push Notification service. After making the change I have the following problem.
I am not able to see my registered devices in the monitoring area of Bluemix yet I can fetch the list of registered devices using a REST API. Why is that happening? Screenshot
I am not able to find a REST API to send a notification to a particular deviceID like I was doing before with the Push service. How can I do that with the new service? Alternatively, is there a way to create an instance of the original Push service in my new organization?
The registered devices list was removed in the move to the new push service as you note, I'll reach out to the push team to see about the possibility of reintroducing it and add a comment with their reply. Right now you are correct in that the only way to grab the list of devices and their deviceIds is through the REST API.
You should be able to use POST /apps/{applicationId}/messages, specifying any number of deviceIDs in the 'target' array . You can see the full json model for the call by clicking the "Model" tag under the "Response Class" header rather than "Model Schema" as shown:
I am running into a small issue in my unity app after adding the OneSignal plugin. I can receive push notifications if I send them from the web server and everything is fast. However, my concern is that OneSignal assigns one ID to the device not to the user.
My question is: there is any way to create an ID after my login?
The only problem in the actual state is if the user has multiple accounts or if a friend connects from that device. Both users would have the same ID and therefore both would receive the same notifications.
Thanks.
I would recommend using OneSignal.SendTag in your app to tag the user with your userId when they login. Then when they logout call OneSiganl.DeleteTag to remove it.
This will allow you to send a notification with the tags field on the OneSignal create notification REST API POST call.
I am not able to get actually how push notification works in worklight.
how to pass my device details for the server after registration with GCM,APNS.
how can I toggle with on/off of push notification within the app.
You need to:
Read both:
Knowledge Center: http://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.dev.doc/admin/c_push_notification.html?lang=en
Developer Center: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-0/notifications/
The Worklight/MobileFirst Platform Foundation framework takes care of that for you.
In the case of Event Source-based notifications, a notification can be sent by the userId or other types of identifications. This information is stored automatically in the server's database. On your end, when implementing the adapter logic to send the notifications, you can use various APIs (see the Knowledge Center link above) to decide to whom/how notifications are sent.
Also in Tag-based notifications, you can either auto-subscribe or have the user tap a button to subscribe; this sends the data to the server's database, and again in the adapter logic you can then iterate on this list of users/devices to send the notification(s).
To toggle notifications on and off you can use the subscribe/un-subscribe API methods. Review the developer canter tutorials and their accompanying sample applications.
I am considering switching from pushwoosh to gamethrive / onesignal but am a little confused. I am using the Unity SDK and cant see anywhere in the documentation that I am able to sund push from one unit to a specific othe unit. Can anyone help me clarify if this is possible
Thanks in advance
Yes this is possible.
The OneSignal API supports delivering notifications to individual users or groups of users in several ways. In your case, the best way is probably through the device's OneSignal ID (through the include_player_ids field in the OneSignal API).
You can send notifications from one device to another by interacting through the OneSignal API either on your own backend server or from the code running in your app. However, in either case, you will need to have a backend server to store a list of the OneSignal ID for each one of your users.
Here's a rough outline of the process:
Part A (First getting the OneSignal ID):
A device runs your application for the first time
You initialize OneSignal in your application and you receive a new unique OneSignal ID for this new device in a callback
You then must store this OneSignal ID on your own backend server somewhere.
Part B (Delivering a message):
You wish to send a message to a specific user
You ask your backend server for the OneSignal ID of the user who you wish to send a message to.
You use the OneSignal API to send a message to the user.
Related links:
OneSignal Homepage
OneSignal Documentation Home
OneSignal Notification Delivery API Documentation