-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Notification is not shown on ios device #1121
Comments
I'm having a somewhat similar issue.... My personal device is receiving notifications but no one else in my team receives them. Their devices register and the notifications successfully send but they never appear on their phones. |
@Deadsoil is issue solved for your team mates? |
We're seeing the same issue here, with 1.8.0. We're testing with earlier versions at this moment. |
I have found the problem and it's described in below link, now it works fine for me [http://stackoverflow.com/questions/32690850/google-cloud-messaging-showing-success-message-but-not-sending-ios](reason and solution)
|
@RezaRahmati - Issue is still not resolved. I already had the priority as high. The strange thing is I receive them on my device but my team members don't. Even though the console log from my node app tells me it was successfully sent and their devices are registering and returning a token. It doesn't really make a whole lot of sense. I might try reverting to an older version of this plugin and see if it resolves the issue. Still doesn't account for why they are working for me and not them though. It's working for me on an iPhone5s and iPhone6s.... But not for them on a 6s and a 6+. Maybe an ios version issue. |
@RezaRahmati when sending to GCM on Android use:
when sending to GCM on iOS use:
advanced features like picture type messages are not supported on iOS. |
@macdonst Yes, as I mentioned even after changing message json to "notification" for ios, still I didn't received notification, until I add "priority: high" to message |
@Deadsoil Could it be "gcmSandbox" problem? all of you are using same ipa file? I mean debug or release mode. |
@RezaRahmati weird, there should be no reason why it wouldn't show up without priority set to high. |
Hi guys I have same problem, I'm using "gcmSandbox" and add "priority: high" to message. Can you help me please. Thanks |
@Setra-Esokia Do you see "sucess:1" in results? |
yes, I have sucess:1 but not receive notification |
@Setra-Esokia Can you put your message json and result json here? |
message json => {"message":"congratulations","content-available":"1","priority":"high"} result json = {"multicast_id":7264988913802171027,"success":2,"failure":0,"canonical_ids":0,"results":[{"message_id":"0:1470836861750262%b3dcc6a7f9fd7ecd"},{"message_id":"0:1470836861652114%b3dcc6a7f9fd7ecd"}]} |
@Setra-Esokia message should be something like
|
When I used this structure i have a failure with message "InternalServerError". {"to":"xxx","notification":{"sound":"default","title":"default","body":"Test Push!"},"priority":"high"} {"multicast_id":8572784144255206972,"success":0,"failure":1,"canonical_ids":0,"results":[{"error":"InternalServerError"}]} |
@Setra-Esokia As a rough guess, Did you connect GCM to APN? I don't remember the exact steps but you need to upload provisioning profile to GCM, so you will get GCM id (instead of APN) and behind the scene GCM send messages to APN |
@RezaRahmati Yes, i generate my developper and production certificate and upload this in google service GCM. I receive the valid APNS and GCM token. I have no idea why GCM push failed. |
Hi @RezaRahmati and @Setra-Esokia. Did you solve the issue? If so, could you tell how? Thank you. |
Hi @Assylkhan , i have not solve this problem. I have change my plugin with firebase and reconfigure all inside my application. |
This thread has been automatically locked. |
Hi guys
I am using GCN's APN, app is building for ios, it successfully gets token, and I can successfully can send data to gcm, but no notifications appear on device
My code is
and message body is
and message body is sent to
https://android.googleapis.com/gcm/send
and I added Authorization header tooI get this response which seems that it is successfully send
I have tried with both "gcmSandbox" true and false, I get different tokens for both, and for both response is success=1 but no notification appears
Cordova 6.0
ios-cordova 4.2.0
The text was updated successfully, but these errors were encountered: