No I started use push notification in my project (it worked sometime ago), but can't make it work. I downloade sample-messages project and changed my account and application settings. But messaged don't delivered to receiver. Registration of device is ok. I see my subscribtion. No errors from response when sending notification. What I only got is the json description from logs, when i click my message from queue (but it's in status "sent") Can't get it work. Please, help.
{"notification":{"registration_ids":["APA91bEsqEY2OcaQpgU6Nmk6P7P0fSEdnGuXHSOnUwMJ3ZCAuZC0hGiE_7DX-TlvuAnivJ3Bt4nSM7eEN3AR2Qg2jjCGC8RRT7GbDJgpuy25plCohb23CpD5hLaHo7l-TZvgZhpXjCM0"],"delay_while_idle":false,"data":{"message":"fgjkkkkllkleddxccvvvcxfffffjhghvfg I was ","collapse_key":"event5711312"},"time_to_live":86400},"log":[{"device_token":null,"created_at":"2016-02-23T18:21:42Z","delivered_at":null,"failed_at":"2016-02-23T18:21:47Z","error_code":401,"error_description":"Unable to deliver notification 11778569, received error 401 (Unauthorized, check your App auth_key.)"}]}
I redid all the configuration steps in the link:http://quickblox.com/developers/SimpleSample-messages_users-android#Setup_GCM
Now it is back to work!
Attention to some details:
The API key you have to use in Google cloud console is of the SERVER type
Use the same package name on Android manifest and Google cloud console
Use your application ID from developer console to get GCM token on your Android application
don't forget to copy the google-services.json (generated when you enabled Google services for your app) to app/ directory on your project (the same directory of your src/)
Related
I follow these steps in google cloud console :-
Google Cloud Console-> Select Our project -> Select API & Services -> Select Enable API & Services -> Search Android Device Verification API -> it gives "No Result Found"
why it gives this message while I want to enable Android Device Verification API feature. By Default Android Device Verification API does not show in API List on page Enable API & Services page and i want to include this feature in our project.
For another project when I search "Android Device Verification API" with above process it gives following error:-
There was an error while loading /apis/library/androidcheck.googleapis.com?project=chatme-342307. Please try again.
Request ID: 9929714032143206958
Kindly support above two problems.
First of all thanks for all viewing my question.
My problem has solved but i do not know it is exact answer or not.
I just remove app from project setting of my app in Firebase console then again create app in project setting and add with SHA1 and SHA256 then I search Android Device Verification it show in Result
I followed the instructions in the Rocket.chat documentation:
Removed the check mark from the gateway
added GCM keys from firebase
rebooted the server
Pushs seem to come, but the listener "pushnotificationreceived" is triggered only if I open the application immediately after the push should come or I am in the application during the push, if I have minimized the application and send myself a message, then there is no push.
If I throw the push myself through the firebase API, then the push works out as needed.
There is a suspicion that this is due to the fact that Rocket.chat sends push data in the data key, not notification (https://github.com/RocketChat/Rocket.Chat/blob/develop/app/push/server/gcm.js).
I also have an error in the Rocket logs.Chat:
"For devices running Android 8.0 or later, you need to specify the android_channel_id identifier. See https://github.com/raix/push/issues/341 for more information", but even with this error, push writes that it was sent successfully.
Please, checkout this post:
https://forums.rocket.chat/t/apple-push-notification-service-update-from-legacy-binary-protocol/12425/4
Also, consider asking dev questions at:
https://open.rocket.chat/channel/dev
Trying to implement push notifications with Flurry for our app we are getting the flowing message:
"Could not save push notification credential ValidationFailedException: Certificate environment mismatch. Your certificate for unknown does not match with production you are uploading for"
The message it self is very clear but we just can't understand what is wrong.
Yahoo Docs are not updated So we do not know if something changed or what.
It is not and issue with the p12 file password because then there is a deferent message.
we created an intermediate cert file in the key change with push notifications enabled
In the Apple developer console -> Certification -> we created a new certification for "Apple Push Notification service SSL (Sandbox and Production) in the Services section.
3.Downloaded it and opened it
In the flurry console in Admin -> Apps -> Flurry Push -> Push Credentials we tried to add the certificate to either dev or prod and got the message I wrote above.
Anyone can help with this.
We can't find any sort of documentation for this on the web and it is weird!
This might be a lead for the issue but can't figure it out: Your certificate for unknown does ???
10x
I am not able to send push message to iOS device from FCM console. I receive error message "Check APNs certificates in settings". My configuration is the same as in FCM guide:
I generated Auth Key in Apple Developer Account.
I uploaded auth key in Firebase project, put Key Id and prefix (Team Id).
I added FCM SDK to my iOS project (added Google-service.plist as well).
I saved registration token in Firebase Database.
Finally, I can send a message to all devices with my App ID (but cannot receive this message, I do not know why), but I cannot send a message to selected device with token.
Any ideas?
If the bundle ID that was used to generate the FCM token does not match the bundle ID in your Firebase App you will receive the error code: 'messaging/invalid-apns-credentials' even if your Auth key is configured correctly.
This seems like the most likely cause of this error ever occurring. Double and triple check that the FCM token was created by an app with the exact same bundle ID as what is listed in your Firebase console.
The GoogleServices-Info.plist does not verify that it contains the same Bundle ID as the app it is attached to so it is easy to make this mistake.
On the Android side you will get a compilation error if the appId is not present in your google-services.json thus preventing this issue.
Please check the app name in GoogleServices-Info.plist and Bundle ID in your app.
And also check you put the plist file in proper directory.
Uploaded auth key in Firebase project to both Dev and Prod ones.
This are the only reason for not having the push notfications to your app.
I've followed the iOS getting started tutorial here, registered my device but the notifications don't seem to arrive. What am I doing wrong?
It would be helpful to:
Check the exact reason in the statistics page of that notification
Did you compile the app with the correct provision profile? In order to test with production certificate, you'll need to compile the app with AdHoc provision profile.
For easier debugging, please add our error delegation method as shown in our wiki here