I'm really puzzled about to get the whole chain of sending a push from my .NET backend to my android app using Amazon SNS.
I'm using JustSaying on my backend to send my messages to SNS which is working when I tested it with a email subscriper. This is the code I'm using to send the push:
var publisher = CreateMeABus.InRegion(RegionEndpoint.EUCentral1.SystemName)
.WithSnsMessagePublisher<Push>();
publisher.Publish(new Push("Hello"));
And push class looks like this:
public class Push : Message
{
public Push(string body)
{
Body = body;
}
public string Body { get; set; }
}
Now my problem is, how to I send this push to my specific device?
I created an app on https://developers.google.com for google cloud messaging and have a applicationkey and senderid.
I also set up an API project/app on http://console.developers.google.com and enabled the API for cloud messaging.
In AWS SNS console I also created an application and supplied the above mentioned applikationkey which generated a ARN for the Google Android Platform.
In my android app I'm running this code:
try{
GoogleCloudMessaging gcm = GoogleCloudMessaging.getInstance(this.getApplicationContext());
String regId = gcm.register("my-sender-id ");
} catch(IOException e){
}
I'm fumbling in the dark here and can't find any good turtorial on how to set this up. AWS documentation seems to cover only small parts and seems to be outdated.
Any help on pointing me in the right direction is greatly appreciated.
Thanks!
See the developer guide of SNS http://docs.aws.amazon.com/sns/latest/dg/mobile-push-gcm.html. In short:
Get GCM device token (or regId) as in your code
Register your device to SNS by calling CreatePlatformEndpointRequest with your device token. You will get a platform endpoint ARN which is the identifier of this device in SNS.
Send notification to the device. Use Publish to publish notification to the platform endpoint ARN
Alternatively, you can subscribe your device to a particular SNS topic. Then you will be able to publish a notification to the topic, and SNS will broadcast it to all subscribers.
Related
I need to send SNS notification from an Android mobile device targeting another specific Android device endpoint. I could do this last year with the code below. Now it just doesn't work any more. Does anyone have similar issues with sending SNS notification to specific mobile endpoint and how can it be resolved?
AmazonSNSClient snsClient = new AmazonSNSClient(identityManager.getCredentialsProvider());
PublishRequest publishRequest = new PublishRequest();
publishRequest.setMessage(message);
publishRequest.setSubject(subject);
publishRequest.withTargetArn(mobilePhoneEndpointARN);
snsClient.publish(publishRequest);
I have resolved the problem. I added a custom "sns:Publish" permission to my authenticated mobile user policy group.
-Problem solved-
I am using AWS resources for my android project, I am planning to add push notification service for my project with AWS SNS.there are few questions bothering me much. I did not find any questions regarding these, except one or two but with unclear explanations.
1.Does AWS support FCM? SNS work with GCM. But Google recommends to use FCM instead of GCM. I did not find AWS supporting FCM.
2.Do AWS store messages (or data) into their databases even after sending push notifications?
3.I tried putting FCM api key in SNS application platform, it is showing invalid parameters why?
FCM is backwards compatible with GCM. The steps for setting up FCM on AWS are identical to the GCM set up procedure and (at least for the moment) FCM works transparently with GCM and SNS with respect to server-side configuration.
However, if you are sending data payloads to the Android device they will not be processed unless you implement a client side service that extends FirebaseMessagingService. The default JSON message generator in the AWS console sends data messages, which will be ignored by your app unless the aforementioned service is implemented. To get around this for initial testing you can provide a custom notification payload which will be received by your device (as long as your app is not in the foreground)
There are GCM-FCM migration instructions provided by Google however the changes you need to make are predominantly on the App side.
The steps you need to follow to test GCM/FCM on your app with SNS are:
Create a Platform Application in SNS, selecting Google Cloud Messaging (GCM) as the Push Notification Platform, and providing your Server API key in the API key field.
Select the Platform Application and click the Create platform endpoint button.
Provide the InstanceID (Device Token) generated by your app. You must extend the FirebaseInstanceIDService and override the onTokenRefresh method to see this within your Android App. Once you have done this, uninstall and reinstall your app and your token should be printed to the Debug console in Android Studio on first boot.
Click the Add endpoint button.
Click on the ARN link for your platform application.
Select the newly created Endpoint for your device and click the Publish to endpoint button.
Select the JSON Message Format, and click the JSON message generator button.
Enter a test message and click the Generate JSON button
Now comes the "gotcha part".
The message that is generated by SNS will be of the form:
{
"GCM": "{ \"data\": { \"message\": \"test message\" } }"
}
As we mentioned earlier, data payloads will be ignored if no service to receive them has been implemented. We would like to test without writing too much code, so instead we should send a notification payload. To do this, simply change the JSON message to read:
{
"GCM": "{ \"notification\": { \"title\": \"test title\", \"body\": \"test body\" } }"
}
(For more information about the JSON format of an FCM message, see the FCM documentation.)
Once you have done this, make sure your app is not running on the device, and hit the Publish Message button. You should now see a notification pop up on your device.
You can of course do all this programmatically through the Amazon SNS API, however all the examples seem to use the data payload so you need to keep that in mind and generate a payload appropriate to your use case.
Now you can go to your firebase console (https://console.firebase.google.com/) select your project, click the gear icon and choose project settings, then click on the cloud messaging tab...
You'll see the legacy Server Key which is the GCM API Key and you'll have the option to generate new Server Keys which are the FCM versions
SNS will accept both versions but their menu option is still categorizing it under GCM
Here is picture for your reference:
Note that you can "accidentally" remove your Server Keys but the Legacy server key is not deletable. Also, if you click the add server key button, you'll get a new server key BELOW the first one, WITH NO WARNING! ...Nice job Google ;)
One more additional note to Nathan Dunn's great answer.
How to send data with the notification from SNS to Firebase.
We need to add data to the Json (inside the notification):
{
"default": “any value",
"GCM": "{ \"notification\": { \"body\": \”message body\”, \”title\”: \”message title \”, \"sound\":\"default\" } , \"data\" : {\”key\" : \”value\", \”key2\" : \”value\” } }”
}
In your FirebaseMessagingService implementation (Xamarin example)
public override void OnMessageReceived(RemoteMessage message)
{
try
{
var body = message?.GetNotification()?.Body;
var title = message?.GetNotification()?.Title;
var tag = message?.GetNotification()?.Tag;
var sound = message?.GetNotification()?.Sound;
var data = message?.Data
foreach (string key in data.Keys)
{
// get your data values here
}
}
catch (Exception e)
{
}
}
I tried to use solution with notification payload instead of data, but I did not receive push notifications on the mobile device. I found this tutorial https://youtu.be/iBTFLu30dSg with English subtitles of how to use FCM with AWS SNS step by step and example of how to send push notifications from AWS console and implement it on php with aws php sdk. It helped me a lot.
Just an additional note to Nathan Dunn's Answer: to add sound use the following JSON message
{
"GCM": "{ \"notification\": { \"text\": \"test message\",\"sound\":\"default\" } }"
}
It took me a while to figure out how to send the notification with the right payload (publish to topic). So I will put it here.
private void PublishToTopic(string topicArn)
{
AmazonSimpleNotificationServiceClient snsClient =
new AmazonSimpleNotificationServiceClient(Amazon.RegionEndpoint.EUWest1);
PublishRequest publishRequest = new PublishRequest();
publishRequest.TopicArn = topicArn;
publishRequest.MessageStructure = "json";
string payload = "\\\"data\\\":{\\\"text\\\":\\\"Test \\\"}";
publishRequest.Message = "{\"default\": \"default\",\"GCM\":\"{" + payload + "}\"}";
PublishResponse publishResult = snsClient.Publish(publishRequest);
}
Amazon does support FCM as all previous code has been migrated from GCM to FCM. Below article explains in detail.
Article Published by Amazon
To answer the questions:
AWS SNS does support FCM.
No AWS does not store messages after sending push notifications.
For a detailed tutorial on setting up FCM with SNS please read this article.
I want to send push notification to individual using android GCM. have created the app in SNS. I am using aws-sdk v1.4 for Ruby.
When I send through Amazon web interface I receive the messages, but When I publish it through using the code below, I get blank messages. what is the right message format to send?
sns = AWS::SNS::Client.new
endpoint = sns.create_platform_endpoint(platform_application_arn:my_token)
sns.publish(target_arn:endpoint:endpoint_arn, message: "GCM:{data:{message:"GCM:{data:{message:'hello'}")
Please help.
TIA
{"GCM": "{ \"data\": { \"message\": \"hello\" } }"}
Do not call to_json method also set the subject parameter in publish.
The message should be a valid JSON string if you want to publish a message to GCM. You can use to_json to serialize a hash object to JSON. Here is a article about using AWS SDK for Ruby http://blog.tryneighborly.com/amazon-sns-for-apns-on-rails/.
For more information about Amazon SNS:
Send Custom Platform-Specific Payloads in Messages to Mobile Devices
Getting Started with Google Cloud Messaging for Android
Ruby doc for Aws::SNS::Client
I have been trying to send push notifications to a Phonegap app deployed on iOS and Android. iOS works fine, but Android doesn't work when I send push notifications from any of the dev consoles from PubNub, Parse and Amazon SNS.
I did verify that I can send notifications if I use the GCM API, so I am using the correct Sender ID, API key and the device token.
I don't see any errors on PubNub console. On Parse dashboard I see that the push notifications have been sent. No error on Amazon SNS. Yet, no push notifications on the device.
I am out of ideas. Thanks in advance for any helpful advice.
With help from PubNub, figured out what the issue was. The sample on PubNub has the following format
{"pn_gcm": {
"data" : {
"GCMSays" : "hi" }
}
}
But the required format was
{"pn_gcm": {
"data" : {
"message" : "hi" }
}
}
After confirming using PubNub console, I updated my JSON object in the code and it all worked like a charm.
With Parse console, I tried to create a JSON object with similar format, but it didn't work. Haven't tried Amazon SNS.
This tutorial illustrates how to configure Android GCM with PubNub: http://www.pubnub.com/docs/java/android/tutorial/google-push-notification.html
[Parse developer] Parse doesn't provide 1st party support for PhoneGap; their product just works with the JS SDK, which doesn't have native Push support. I describe what is necessary to get Parse to recognize your device for push in an arbitrary language in a previous question. You may however be receiving the push but not creating a notification.
In Android (unlike iOS, WinRT, or WinPhone), push doesn't necessarily imply "notification." The native android SDK from Parse creates this automatically for you. You'll need to create your own BroadcastReceiver and wire it to handle the intents that the Play Store app is sending for pushes. You can find these in our Android Push Tutorial. In your BroadcastReceiver, you'll want to create and register your own Notification object when receiving a push.
For Firebase Cloud Messaging, I had to use this structure to receive a tray notification:
"pn_gcm": {
"notification": {
"title": push_title,
"text": push_message
}
},
I am trying to implement push notifications via StackMob on an existing Android app. I have gone through their tutorial and dev center to try to find a solution to my problem, but I cannot. In my app's BaseActivity I have my sender ID (actual id replaced with # for obvious reasons):
public static String SENDER_ID = "############";
from the Google API Console. I also have the init function (again, PUBLIC and PRIVATE keys replaced in this code):
StackMobAndroid.init(this.getApplicationContext(), StackMob.OAuthVersion.One, 0, "<PUBLIC KEY FROM STACKMOB DASHBOARD>", "<PRIVATE KEY FROM STACKMOB DASHBOARD>");
From what I understand, I also need to register any devices to recieve the notifications, which is just below the init:
try {
final String regId = GCMRegistrar.getRegistrationId(this);
if (regId.equals("")) {
registerForPush();
} else {
Log.e("BaseActivity", "User already registered for push notifications");
}
} catch (UnsupportedOperationException e) {
Log.e("BaseActivity", "This device doesn't support gcm. Push will not work");
}
private void registerForPush() {
GCMRegistrar.register(this, SENDER_ID);
}
When I run my app, I get Registering app com.example.android of senders ############ in LogCat, so AFAIK my device is registered to get push notifications. But when I try sending a push notification from the StackMob dashboard and check the Log from that push, I see
Failed to send message {"alert":"deadbeef"} because there is no C2DM ClientLogin token for version=0
Can somebody explain what that log message is actually telling me?
There are two versions of Android push: the old one C2DM and the new one GCM. You can register tokens for either of these and StackMob will send a message using the appropriate credentials. C2DM has been deprecated, so all the SDKs register tokens as GCM by default and that's what the push instructions have you configure with the sender_id and all that.
Your token has accidentally been registered as C2DM somehow. When we go to push we see you have no credentials there and print that message. The solution is to remove the token via the push console and register it again as GCM.
https://dashboard.stackmob.com/data/console
The real question is how you ended up registering a C2DM token in the first place. If any StackMob tool or demo doesn't have GCM as a default and C2DM clearly marked as legacy, let me know.