I have a problem with my application. About sending notifications via GCM. My application saves on my server the user register_id, notifications work perfect, but after an hour I get error NotRegistered.
I have reviewed the documentation and in theory the REQUEST should return me a new register_id, but this does not happen.
Can I get help?
Based on your Manifest file, I suppose that you are using https://github.com/infobip/push-plugin-cordova-phonegap insted of https://github.com/phonegap-build/PushPlugin.
Here is a documentation for Infobip Push Library. Let's try to integrate it from scratch, but first of all, don't forget to register on Push Platform and get necessary credentials.
Related
I'm trying to generate alerts based on notifications from Taiga project management software (when a user creates a project for example). These alerts will arrive to a specific Rocket.chat channel.
For this I am using the incoming Rocketchat webhooks: https://docs.rocket.chat/administrator-guides/integrations/
So I created the incoming webhook and entered the data into Taiga:
Configuring the webhook in Taiga
Once all this is done I check that the message arrives at the destination correctly:
Example of a notification message
Indeed, the message is received but it doesn't show any information. When a user history, an issue or any modification that leads to an alert is created, it is received in rocketchat but it doesn't show any information (empty message).
Payload sended by Taiga to Rocketchat
Does anyone know why he won't show me any information?
Thank you very much in advance
Greetings.
Do you really want to post notifications to a Rocket Chat channel, when a taiga user created a project in taiga? I would not know, how you can do that. But, as far as I can see, your screenshot shows the configuration of a generic webhook in a project after that project has been created. Therefore, I hope it is sufficient to post notifications from that project to your Rocket Chat channel. Here is my answer for this case:
I observed a similar behavior. Using the generic webhook, I could only trigger empty posts in my Rocket Chat channel by clicking on "test" for that webhook.
However, the Rocket Chat API seems to be compatible with the Slack API, cf. https://github.com/RocketChat/Rocket.Chat/issues/1728#issuecomment-166669379.
In contrast to the generic webhook, the Slack plugin for taiga (https://github.com/taigaio/taiga-contrib-slack) worked out of the box (https://tree.taiga.io/support/contrib-plugins/slack-integration/).
Only my browser gave me some hassle, because it cached the taiga webpage and after installing the Slack plugin a simple page reload was not enough to display the "Plugins" entry in the "Admin" menu of the project. "Shift+reload" did the job. But apart from that standard issue, everything worked.
We are unsure what exactly will happen with our existing apps that use GCM after 10.04.2019.
We have updated the server-side of our apps
We have new FCM-based versions of our Android apps.
However:
We cannot force the existing users to update their apps
Corporate clients might even continue to roll out outdated app
packages to new users
The information / documentation we found somewhat unclear to what will happen in such cases. Therefore, we decided to put our assumptions into 4 statement and we hope someone will be able to confirm them.
It will not be possible to put apps which use the GCM APIS into the Play Store after 10.04.2019
It will not be possible to generate a new GCM tokens after 10.04.2019
Existing users with existing apps which have already have a GCM token will be able to use their apps normally without being forced to update. E.g. Push notifications and related things will work for them.
A user of an existing app which never created a GCM token will not be able to create a GCM token and thus not be able to use any GCM related functions (e.g. Push notifications and related things). Such a user would need to update to the apps in order to e.g. receive push notifications.
I hope someone can confirm above assumptions.
I've implemented Safari Push Notifications both server-side and client-side. On the client, after asking for permissions, the callback function is called with permission "denied".
On the server-side, the logs show that a request for the push package has been made and returns a 200, but a few seconds later the /v1/log endpoint is called with no payload.
Does anyone have an idea how to debug this?
May help following guide and push package creator.
browser-push
A helpful tip is to look in the System Log, from the Console app. Safari shows messages in there.
Another reason for my issue is realted to Django, which as 1.5 doesn't show non-form data in request.POST, but in request.body.
Using v4.0.10 of Pushsharp (nuget package), I am getting error GCM Authorization Failed when sending push notifications to Android devices.
Seems the bug raised in issue 574 (https://github.com/Redth/PushSharp/issues/574 ) has been compiled into the nuget package, yet I'm still getting this error.
Could this be related to the introduction of Firebase Cloud Messaging?
Does anyone still have success using GCM?
As of right now, GCM is still usable. However, it is highly encouraged for new users to use FCM instead. Either way, for both GCM and FCM, you must use a Server Key generated from the Firebase Console. There is a visible note in the GCM docs saying:
Starting from Sept. 2016 new server key can only be created in the Firebase Console using the Cloud Messaging tab of the Settings panel. Existing projects that need to create a new server key can be imported in the Firebase console without affecting their existing configuration.
The Authorization error has been encountered by number of users, some also had an old project. See my answer here for more details.
The sender id used in the app code needs to match the sender id Firebase Cloud Message Console and its corresponding "Firebase Cloud Messaging token".
Thank you #AL for your help.
I am using gcm with appodeal in my app and when I am sending the push notification the for the first push was successful but phone is not receiving the notification and after that error is there while sending push that device is not register. What to do in this situation please help me.
Is it iOS or Android ? I had the exact same issue just yesterday with iOS and all I had to was to create a development provisioning profile and set it up properly in xCode. I hope that helps you.
I think for you to verify that your app can send and receive messages, client apps must register with GCM.
To register with GCM:
1.The client app obtains a registration token using the Instance ID API. The call to this API must have the authorized entity set to your app server's sender ID, and the scope set to the appropriate value for GCM (depending on your platform). Refer to the API reference for full detail on this API.
2.The client app passes the registration token to the app server.
3. The app server saves the registration token and acknowledges to the client app that the process completed successfully.
This thread may also provide further insight as to why you are receiving the device not registered error.