I am using parse's latest SDK with android and i implemented it with my project which also using MaterialViewPager framework from github but for some reason, when i send a push from the web interface (dashboard), it says recipient found but "Push Sent 0".
Your code seems to right but this are many issues with Parse Push for Android. I have experienced same kind of issue many times. Sometimes, push notification arrives late. There are many questions about these problems on SO. Unfortunately, there isn't any solution that works for these situations. The clear solution I found is to use GCM.
instead of trying to solve a problem which i don't really know if it's from my app or parse itself as i tried so many things and wasted 2 weeks on that. I moved from parse to Google Cloud Messaging and it works fine. Push notification sent like instantly.
Related
So I am compiling Rocket Chat to use my own Firebase server so I can server notifications without worrying about hitting the notification limit. I've followed the steps here and gotten a working Experimental version of the app on Android, but I can't seem to get the notifications to work. Checking Firebase shows no users of my app, though sometimes it will register a single user but that's it. I've got to be missing something simple, but I can't figure out what. Any help or tips would be greatly appreciated! Thanks.
If you need any more information just let me know.\
UPDATE: I can send test notifications from Firebase and they show up on the device, however they are not marked as read in Firebase when clicked. It seems as if notifications work from Firebase, but it has no way to communicate back to Firebase.
FINAL UPDATE: It turns out that Rocket Chat server needs the legacy version of the FCM keys. By replacing the existing google-services.json file with the one provided by Firebase and following the instructions to get the legacy keys caused notifications to work. Hopefully someone else can benefit from this insight.
FINAL UPDATE: It turns out that Rocket Chat server needs the legacy version of the FCM keys. By replacing the existing google-services.json file with the one provided by Firebase and following the instructions to get the legacy keys caused notifications to work. Hopefully someone else can benefit from this insight.
i am using phonegap-plugin-push to receive notifications.
The very first part, the registration step, works fine on android and ios. I`m saving the registration token on my server and that part is pretty ok.
However, when my server generates an notification, only android version gets notified.
For each device i created a specific api key, as shown in the docs.
But what works for android isn't working for ios.
On android, if my app isn't open i get correctly the notification (vibration+notification)
Is there a way to achieve the same behavior on ios using GCM?
In the end there is no easy solution for that.
As pointed out by #Daniel, the better way to do it is to configure both GCM and APN. a brief discussion can be found here
I can successfully push notifications to an app, and they show up on my Androids notifications, but I can't get the payload into the app.
I've found this plugin: PushPlugin, but I can't seem to get it to work with Parse, since it asks for a GCM ID, and I don't know what to give it from Parse. Also, the plugin doesn't seem to offer a way to register to certain channels, or even get an installation ID from Parse.
If I include this plugin: phonegap-parse-plugin to take care of the installationID/channels stuff, then I get a runtime error that randomly pops up (adb logcat) saying it can't find com.parse.GcmBroadcastReceiver, and the app crashes.
I just want an Ionic app that can receive a push notification from Parse, and simply display it.
I was in the same boat a week ago and trudging through it here's what I've found:
Here's the best fork I could find for the integrating with parse on cordova(ionic) on android and iOS
https://github.com/grrrian/phonegap-parse-plugin
Make sure to rename the ionic plugin add in the instructions to the grrrian repo not the avivais one in the READ.ME
(He wanted to merge the branch, but I think avivais has finished maintaining it, so the PR is sitting dead)
There will be a compile error brought on by the new ionic Crosswalk feature which is trivial (heh.. ) to fix. Follow these instructions:
https://github.com/katzer/cordova-plugin-local-notifications/issues/426#issuecomment-113166439
Lastly, you need to create an Application Class manually as per the instructions. I didn't know how to do it so I made a comment here about it that should be helpful
https://github.com/grrrian/phonegap-parse-plugin/issues/8#issuecomment-118955744
I'm in the midst of trying to figure out why the notification isn't being received while its in the background though..
Hope this helps someone
EDIT:
Turns out it works fine in the background. All the notifications came in overnight. My thought is that Parse throttles if you send too many messages to one user at once
I have an android application where push notifications are implemented by GCM.
I need to change this. I need that with the new release (the app is already in the Store and people already use push with GCM) all the mechanism will be handle from Parse.
Can I simply delete everything concerning GCM and implement everything concerning PARSE and then upload the version of the application and be sure that everything will run the same?
Has anybody an idea if there will be conflicts with doing this? I'm thinking about devices that already have a GCM token for example.
You should try it and see. I think when implementing Parse, the registration ID (unique to every app <--> device) will be generated again. I've written a couple of articles on the topic which are not directly useful but can help in other ways.
Just make sure you follow this thoroughly.
I've just added GCM pushes to my Android app, and developed Rails backend for it. When I tested it the system worked good. Later I tried to send pushes from my server again but my app got nothing; after 30 minutes it got 3 notifications at the same time. What's the trouble? Does GCM have some restrictions? For example, count of notifications per houror something else. Is it possible to fix it? Thanks in advance.
It's probably just a bug of GCM they got the same thing.