I am working with AWS SNS Implementation in My iOS app and I followed all SNS documentation to create platform in SNS Dashboard.
I am getting an error like "Invalid parameter: Attributes Reason: Platform credentials are invalid " When creating new platform application and please anyone guide me to sort this issue.
Amazon SNS differentiates between the production (APNS) and development (APNS_SANDBOX) versions of apple's push notification services. The error you are encountering is typical to developers accidentally attempting to create an APNS platform application with APNS_SANDBOX credentials, or vice-versa. Can you confirm whether you are using the correct set of credentials for the given platform?
Regards,
-Sid
For people who are configuring Apple Push Notification in AWS Mobile Hub, remember it now (since late 2015) has simplified the APNS certificate to take a single Universal (Production + Sandbox) certificate, so when you generate APNS certificate, remember to choose Sandbox & Production:
and upload the generated .p12 file to AWS.
Related
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 have an issue with receiving notifications on Twilio Chat with Production APN Certifications, i get the error:
Error - 52131
Invalid APNs credentials
Possible Causes
Credential (certificate and private key) is invalid.
Certificate expired.
Possible Solutions
Make sure you have valid certificate and private key provided in your Credential.
When I test my sandbox APN certifcates the push notifications work perfectly.
However when I create APN PUSH SERVICES Certification and upload these and link them to my programmable chat function I get the error message: 52131 - Invalid APNs credentials... https://www.twilio.com/console/runtime/debugger/NOf2857a6c1db54e27984dd8fa9ff5100f
Just to clarify, the push notifications work perfectly on my development project. I use a Sandbox APN certificate, and selected the Sandbox tick box
However in the production version, where I am using:
Specific APN Apple Push Services Certificate, for a unique APP ID I
get the 52131 error.
I did not tick use for sending to Sandbox credential. As it is a
push credentiual
I followed all the instructions perfectly for exporting the
certificate keys.
I also use separate API Keys and a separate Programmable chat.
I get registration of bindings but no notifications as the
certificate is invalid, which I cannot see why as I checked by regenerating a certificate many times
I read in some responses to similar issues having the Sandbox and PUSH SERVICES APN certificate in the same App ID? Or not using the same CertificateSigningRequest to generate the Sandbox and PUSH? Why would this make a difference?
This was the thread: https://github.com/twilio/voice-quickstart-objc/issues/101
Finally after several weeks of emailing Twilio support I found the answer.
Basically the issue was probably because I extracted the Keys from my distribution certificate somehow and not the Push one. So make sure you are extracting the correct keys from the correct certification. Also because I was deleting and removing the push credentials from Twilio so often the bindings to my users were pointing to old Push Credentials that did not exist, so I removed the bindings allowing new bindings to be regenerated connecting to the new Push Certificate SID.
Other things that are important for production notifications on twilio programmable chat:
Make sure your environment entitlements file is set to "production"
Don't check the sandbox option on your production certificate (of
course)
Sometimes there can be issues when creating a Push Certificate using
a certsigningrequest that was used on a sandbox certificate. Try
creating a new Cert Signing file just for production
When you test your Production notifications these will only work on an appstore build built with your distribution certificate. You cannot receive notifications on the simulator (obviously). You cannot receive notifications from an app built using development certifcate...so you need to build and upload your app to testflight to test the notifications then preferably test between two real devices...or just send notifications from the simulator to a device with an appstore/adhoc build on it
I cannot thing of anything else for now that I came across. Twilio support is very good and will try and answer your question if you need help.
I've been trying to use AWS SNS service to send notifications to Apple Sandbox environment . I think I setup everything ok and my dev iPhone can get notification without trouble.
But when I start to send notifications to others who install the test app , I keep seeing error message state that
Platform token associated with the endpoint is not valid
With a messageId :147975e0-8a09-5223-8537-256320ab3733
From what I understand , if one device can success, others can success too.
Could anyone tell me how to debug this probelm.
Thanks.
I believe that the apps that the other people are installing were not built with a dev cert (probably built with an adhoc or production provisioning profile), so you probably should use the production certificate.
You could try adding another application on SNS using the production certificate (or the same one, but not using Sandbox, depending on how you generated it), if it works, that this is it.
Also make sure you are using the correct bundle id associated with the certificate.
Not finding anything here:
https://console.ng.bluemix.net/docs/services/mobilepush/index.html
I'm looking for a web console for sending messages to apps - similar to what is offered by UrbanAirship and Parse (rest its soul).
Yes the IBM Push Notification service has a Push Dashboard where you can author messages, customize the notification payload, specify the target audience and send notifications to both iOS and Android in both Production and Sandbox modes.
Here's a screenshot of the Push Dashboard:
The docs go into it a bit here: https://console.ng.bluemix.net/docs/services/mobilepush/enablepush_ios.html#t_push_send
To access it you'll just need to create a Bluemix application using the MobileFirst Services Starter Boilerplate, and then navigate to the IBM Push Notifications instance from your application dashboard at which point you will be prompted to provide your .p12 certificate and/or GCM credentials.
This link says Configure Worklight to use the correct credentials for sending push notifications.
That sentence is not talking about a Worklight license.
In order to send push notifications you need credentials from the vendor from which the notifications will be sent.
In the case of Google, those will be the GCM key and project number.
In the case of Apple, you'll need to supply a certificate and its password.
Please follow up-to-date guides instead of articles from 2013...
To familiarize yourself with push notification in MobileFirst Platform/Worklight, read the Getting Started tutorials: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-0/notifications/
How to setup your Apple Developer account and the push certificate is unrelated to Worklight/MFP. You can find many guides on the web (that are more up to date) explaining how you can do that.