GOOGLE Cloud messaging works fine for me. I've sent many push notifications in a day and it works fine suddenly it stop sending me notification next day.It's not working anymore not a single notification after a long delay. What is the issue? Is there any defined limitation about GCM? Is GCM works for a time being?
Related
I am building a tvOS app for the new Apple TV that needs to get notifications from a server every time that a chat message is sent. This notification is also to be displayed on the Apple TV. As much as I understand push notifications are not allowed with tvOS.
With this being said, are there any alternatives to what I need?
To clarify: This is a chat app that needs to display a notification to the user on the TV screen every time a message is received by the user. The app stays running indefinitely, while showing instant notifications. - I cannot use push notifications.
Please let me know if this makes sense, and thank you in advance for your help!
We recently built an app for apple TV that shows instant messages from different clients connected to our server. A good library that will answer your requirements is socket.io-client
Just google socket.io and learn how it works. Basically, you wait for a connection on your server and then you can send messages to your clients. On the client side (tvOS in your case) you specify what methods to run as response to the different event coming from the server.
Good luck.
I am using Google development sample codes to receive GCM notifications. I have spent nearly a week to find why I receive notifications after 25~30 seconds!!! did not find any answer.
I receive other apps' notifications (such as Viber, Line and WhatsApp) almost instantly!
It has the same slow behaviour in both emulator and my Samsung Galaxy S5.
I receive respond with message ID from Google GCM server instantly when I send a notifications so it means the problem is from Google GCM server to my app.
Any help would be much appreciated.
I'm creating an instant messaging application. imagine something like skype or yahoo messenger.
Now our server only sends push notification(for new messages) on when the app is on background/multitasked/minimized. But sometimes the server fails to detect that our app is on background, so sometimes it doesn't send push notification even if the app is on background.
Now I'm thinking that our server should just always send push notifications to device even if it is in foreground(so all messages will have a push notif), but we won't show it(the apns) when in foreground. This way, the server won't need to detect if the app is on background or not.
Do you think it's okay, or there will be a sideeffect of always sending apns, you see, if you are chatting whole day on foreground, the client will receive apns but won't show it?
No problem to send lots of notification without reading it, if the payload is different.
You are not forced to show notifications with an alert when a notification is received in foreground.
ok, I've been recently playing with GCM and it seems that when you force close your app, the GCM messages cannot be received anymore.
so the question is that how does FB app works? that even though I force close it, it still send the GCM notifications?!!! any idea?
I have been able to successfully create push notifications and I have also received responses from the feedback service, so I am confident that my configuration is correct, but I was wondering, how long after a device has been made inactive, will it be picked up by the Apple Push Notification Service.
When I first polled the feedback service, I received details on devices which were inactive several days ago. Now, while testing, when I uninstall the application and occasionally poll the feedback service, I'm not receiving any results.
Any idea on how long it takes to update would be useful, as I'm no longer sure if the issue is else where in my code or if I'm just testing too soon.
Issues with Using the Feedback Service
If you remove your app from your device and then send a push notification to it, you would expect to have the device token rejected, and the invalidated device token should appear on the feedback service. However, if this was the last push-enabled app on the device, it will not show up in the feedback service. This is because deleting the last app tears down the persistent connection to the push service before the notice of the deletion can be sent.
You can work around this by leaving at least one push-enabled app on the device in order to keep the persistent connection up. Just install any free push-enabled app from the App Store and you should then be able to delete your app and see it appear in the feedback service.
source:
http://developer.apple.com/library/ios/technotes/tn2010/tn2265.html#TNTAG34
After further investigation elsewhere, I discovered people suggesting that for testing feedback service, there should be two instances of the app on the iPhone. Test the feedback service by removing 1 of these and then attempt to send notifications to this removed app.
When I do this, the feedback service responds very quickly.
I do not have exact timings, but on my system, it feels like it is responding straight away after I make a call to attempt to push a notification and then immediately make a call to the feedback service.