GCM Push Notifications not getting recieved on Lollipop devices - android

Ok,
I'm developing an android app which is enabled with GCM for Push Notifications.
I was having trouble getting push notifications on any device (lollipop / pre-lollipop) when on college wifi. I researched about it and found that the port 5228, 5229, 5230 on my college's firewall (Cyberroam) were closed. So the administrator opened them and now I am receiving push notifications, but only on pre-lollipop devices. Lollipop & Post-lollipop devices still aren't receiving push notifications.
No problem occurs when i use the app on cellular data or on private wifi (at my place).
I'm not able to understand why this is happening.
NOTE: Interesting thing is that all MI devices are receiving push irrespective of their Android version.
Can someone explain what might be happening and solution to this problem.
Thanks.

I found out that the Cyberroam was blocking all requests from the GTalk service. That is why push notifications were not getting through. It is resolved now.
Thanks

Related

Firebase : Devices below Lollipop is not receiving notification from my local server

I am following androidhive's tutorial. I am having weird problem if I try sending notification from console everything is fine. But if I try sending notification from web app devices below lollipop is not receiving any notification. What might be the possible problem
This is first time I hearing this type of issue and have you tested with other device other than your development devices. If a device is registered with the gms then it should receive the message. Try to clear the cache data of your app might be helpful.

Google Push Notification Does Not Work In some Networks

I have an android application (not in the google play) and it is being used by a company (in their building) right now. It uses Google Push Notifications and actually notifications mean everything. Simply customers press buttons of our own developed device when they need someone and we send notifications to someone authorized.
So we developed and tested it and it works fine here in our network (our office wifi).
Then we tested it in thier network. it works fine, too. So they started to use it.
But sometimes it stops getting notifications (in customer's building) suddenly. In this case if we connect tablet to 3G then it starts again.
To Sum up,
Push notifications work fine when android device is connected my Office Wifi,
Push notifications work fine when android device is connected to 3G,
Push notifications does not work sometimes when android device is connected to our customer Wifi.
and idea will be really helpful thanks.
Your customer WIFI needs some tuning. In order to work properly you need to open the following ports: 5228.5229.5230:
Check this out
The device accesses the GCM servers on ports 5228-5230. If your organization has a firewall that restricts the traffic to or from the Internet, you'll need to configure it to allow connectivity with GCM. The ports to open are: 5228, 5229, and 5230. GCM typically only uses 5228, but it sometimes uses 5229 and 5230. GCM doesn't provide specific IPs. It changes IPs frequently. We recommend against using ACLs but if you must use them, take a broad approach such as the method suggested in this support link.
Hope it helps

GCM push notification does not work correctly when using Wifi network

I successfully integrated my app for receiving push notification using GCM. Its working correctly, I just saw a strange behavior while receiving push notification on one of my android set which is using my wifi network, in the same time others whose are using EDGE or 3G network are receiving notifications correctly. When I try to switch off and switch on the wifi, it receives the pending notification.
I tried opening the ports which normally used by GCM i.e 5228,5229 and 5230 in my router's firewall however with no success.
NB: After seeing this, I tried to configure the app for Parse API and its working as same as GCM so I think it depends upon the network packet receiving or something.
I believe, what you're facing is a known issue about TCP connection between GCM servers and your handset is timing out because of inactivity. Network devices (like your Wi-Fi router, your ISP hardware, etc.) between your handset and GCM servers could kill the TCP connection if no packets are sent every now and then.
There are some workarounds for this which you might try. For example, there are apps on Google Play that modify the default Android behavior and make it update this connection more often, increasing chances that it will not timeout. You could try them and see if it fixes the problem for you.

Push notification don't recieved on some device

I am implemented push notification in APP using Google cloud message
http://developer.android.com/google/gcm/client.html
but I faced problem.
On some devices we receive push on another not. I testing two the same devices on one working on another no. But after "Back up and reset" settings on doesn't working device he start receive Push messages. Does anybody have this problem? Or there are some restrictions on GCM (maybe with accounts on devices or GCM conflict with some program).

Android GCM doesn't work with wifi networks when 3G network is available

I am developing app on Android GCM push notification. Everything works fine .But I am not able to get the notification message when my device is on wifi rather than on data plan of service provider. In my case data plan is 3G but and notification comes as usual to devices but when device is connected through wifi I am not able to get any notifications.
Well this should not be the case, I have an android app that receives GCM push notifications regardless it is connected via 3G or Wi-Fi.
What I would suggest to troubleshoot this problem:
When you send the push notification from the server make sure to NOT include delay_while_idle, so the notification get delivered right away. Also make sure you have set time_to_live to a reasonable value (default is 4 weeks)
Try to hold a Wi-Fi lock in your app
Test with different device and/or Android version (maybe it is a problem with certain hardware/API version)

Categories

Resources