I'm getting a weird issue since last night testing with Parse. I was able to send push notifications just fine but now none of my push notifications are being delivered when I send them via the parse push notification tool online.
Edited Ok so it seems this is only an issue for local environment. When I test push notifications going to my test app installed via test flight it seems ok. I checked and I have both the prod and the dev apple certificates in my account...
The delivery report is not very helpful either. Here is the message it gives me
Any idea what is going on? Is anyone else experiencing this? Below is my payload
Ok this was a certificate issue. Seems like Apple revoked my certificate for some reason (no clue why since it had over 11 months left on it).
I went through and created a new development certificate and the rest as covered in this article and boom it works!
https://www.parse.com/tutorials/ios-push-notifications
Hans
Related
I am using Laravel and am trying to send email using Mailgun and Laravel's native Mailable class. The emails are generated as a result of submitting one of several forms. I have been developing my features for a couple of days, and have successfully been receiving emails from my local machine (using homestead) throughout this time.
I have uploaded my code to a server, tested the forms, and everything is still good. Additionally, a colleague of mine has downloaded the code and tests are still successful. So in short, 2 local homestead environments and one ubuntu server are all working as expected.
Suddenly, this functionality has stopped working in all three environments. Upon submitting any form, I get the following error message:
GuzzleHttp \ Exception \ RequestException
cURL error 60: SSL certificate problem: self signed certificate in
certificate chain (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
This has started happening without any changes being made to the code, and is happening on both the local environments and the server - all at the same time.
I have absolutely no idea what could cause this. Is this mail related and something to do with Mailgun? Is this really a certificate issue and maybe something to do with a corporate certificate that allows traffic to leave the network? I am at a loss.
Is anyone able to offer any advice?
Thanks
Well, after a good night's sleep, I returned this morning and found all my forms working again. I have no idea what the problem was, but it seems to be a problem with an external service, not my setup.
Thanks
I am using Amazon SNS service to send push notification.
But today, it suddenly stopped working.
I can't create another Application endpoint, it says -
APNS Sandbox certificate is invalid
and I can't update credentials, the error is -
Request could not be completed (Service: AmazonSNS; Status Code: 500; Error Code: InternalError)
I am able to send push notification using the same p12 file with another software i.e. https://github.com/noodlewerk/NWPusher
What could be the problem?
How can I troubleshoot this issue?
Please help.
Thank you!
The reason for the problem was that (this is my guess) - I sent push notification with incorrect format.
That must have returned error code and because of that the connection between Amazon SNS to Apple server was closed. (It should be kept open always)
Because Apple thinks this as some kind of an attack.
The only remedy is wait for few hours and try again.
This is mentioned in the Technical Note here - https://developer.apple.com/library/ios/technotes/tn2265/_index.html
Even i had the same issue yesterday, it started working few hours back. can you confirm?
I spent whole day generating and testing certificates without any luck, and its working now with the same certificate.
I am trying to enable push notifications, but for some reason I am getting this error. The notification gets sent to parse, but not to the user.
Recently Apple changed how APNS Certificates work - you'll notice that newly created push certificates have the name "Apple Push Services:" and not "Apple Production IOS Push Services:". Apparently production certificates can be used for Sandbox and Production now: "Establish connectivity between your notification server, the Apple Push Notification service sandbox, and production environments to deliver remote notifications to your app."
I'm not sure how much they need to change on the backend side on Parse's end, but I noticed adding to AWS SNS didn't work for me last time I tried.
I am using the APNS for my app in development mode. I integrated with the Urban Airship as per the getting started document they provided on their portal:
Created the certificate in Apple provisioning portal. Imported the .p12 file to Urban Airship app(in dev mode with debug enabled)
Now when I open the application, it shows me the alert and asks me for the permission to enable notification. Once that is done and I try to test push a message from the Urban Airship portal to my device using the device token generated, I get the common error:
Apple Push service rejected device token "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
I searched on google and found this to be a very common problem; however with no solution. Most answers mention that the prod and dev environment conflict is the cause, however that is not the case in my case as I did not create the prod app in Urban Airship nor in the APNS dev certificate. The settings in my AirshipConfig.plist are:
APP_STORE_OR_AD_HOC_BUILD : NO
Development_App_Key: XXXXXXXXXXX
Development_App_secret: XXXXXXXXXX
(not master secret, just the dev app secret.)
Nowhere did I find the response from any user who asked the question and later got it resolved. So, I am not sure how people resolved it when they got stuck. All suggests to recheck the environment conflicts, which is not there in my case.
If anyone has any idea, please suggest the possible solutions as this is a blocker for our release. Pls also respond if this is a generic error which almost everyone gets with Urban Airship, and if Free UA account is not a feasible service for testing.
I've been fighting with these issues the last few days. The thing that fixed it for me was creating a non-wildcard identifier that was using a development provisioning profile.
Until I did this I was only able to have APP_STORE_OR_AD_HOC_BUILD : YES
Things worth checking:
Provisioning profile is set to development
Application bundle ID matches the Urban Airship bundle Id.
You can check the Urban Airship bundle Id that is used by going to:
Settings
API Keys
(See the right hand side and there should be a box that contains the iOS Bundle ID.)
Finally make sure your keys in the plist all match.
Also as you probably know, you cannot test push notifications with the simulator. I Hope this helps.
I have to set up push cloud notification server. I decided to use: http://pypi.python.org/pypi/pyapns/
The question that i have is how to test the server if i don't have an app which will be connected to the server? Is there any sample apps or services that would display the push notification? I just want to send payload using some sort of script and see if sending is successful or not. How people debug such things? Aren't there any kind of virtual env for such tasks?
I do have certificates and ID's of the app, but not the app it self, since the other people are making it. I do not use MAC, or have iOS device. I did read docs from apple.
So eventually i got the right .pem certificate and token of phone with the app-under-dev, phone had to registered as testing one for that app. I just pushed messages and waited for answer unit i got it. Apple do not provide any "easy to use" testing grounds, logs or messages for debugging. Best you can do is to separate pushing service and getting token as much as possible and when you got your hands on app do the raw testing.