For some reason, in ios9, in the methods:BOOL ParseCheckPermissionForRemoteNotifications(void) and void ParseRegisterForRemoteNotifications(BlockBoolAction completion), I cannot reach the parse servers. In ios8, it works perfectly fine. I've tried remaking the SSL certificate and provisioning profile and adding exceptions to NSapptransportsecurity. Does anyone have any idea why this is happening?
Related
I have a very unique situation here, I have to test devices with same specification. The application i have developed has push notification capability enabled. All configurations are done in server side i.e added device as development device, the device is added into provisioning profile, the provisioning profile is installed in phone and development machine as well. Now the problem is the application is installed in both the device in one device everything works perfectly fine the notification appears for every event, however in another device it doesn't.
I tried everything i.e checking the setting in device if for some reasons notification is not allowed or may be some settings. I compared all the settings in both the devices everything is same.
The error I get in server side is Bad Device Token for one device. I tried to delete the token from server side and got it again still same situation it works for one device but not for other.
Any help or pointer would be really appreciated.
I am using APNS service in my universal app (iPhone/iPad) and i am not geting notifications on device. Previously i was getting notifications perfectly but now a days with the same code at server side and client, it is not working.
On server side notification status is delivered but i am not receiving it on my device.
I have checked most of the questions on stackoverflow but i was unable to find my question. one guy said that in development environment it may have delays, but my problem is that i am not receiving notifications at all.
Note: i am using sandbox environment not production.
Just in case you haven't found a solution yet, one additional thing you could check is if your device's date and time is properly set (in the OS). If your iPod, iPhone or iPad isn't set to the current date, we found that notifications are ignored silently. Of course, there are many other possible explanations as to why your service stopped working, but this is a simple thing to check when everything else appears to be fine.
Following are the things you can check
Check the entitlements while codesigning the app. (They can be seen in Xcode build log).
Check whether notifications are on for the device in the settings menu.
If you are using corporate network on the iOS device, the push notifications might be blocked. Try using a different network.
After launching the app, check the organizer for any logs with the reason why push notifications can not be enabled.
I hope some of this helps you out.
I just revoke my certificates
Uploaded new certificates deleted all provision from my organizer
and then created new provisions and installed them on my system.
At the same time I got my APNS working.
We are developing an iOS Application that connects to a server over https using nsurlconnection sendsynchronousrequest
We are getting the following error in the iPod Touch 3.2. However, the exact same code does not give any error on iPhone 3.1
Error message:
The certificate for this server is invalid. You might be connecting to a server that is pretending to be “xx.xx.xxx.xxx” which could put your confidential information at risk
We are trying to connect to a server https: subdomain.domain.com and the certificate actually belongs only to https: domain.com Could that be the reason of the above inconsistency? Any idea why it works on iPhone and not on the iPod Touch. The certificate is signed by GoDaddy. Could it be that the iPod Touch does not have GoDaddy's root certificate?
We need to find a way around this problem without preferably using private APIs. Any help will be appreciated. Thanks.
We had almost this exact problem: A certificate error on a particular device running the same code that worked on multiple other devices. It turned out that this had to do with the internal date of the problem device not being current. Our SSL certificate was up to date, but the device was set outside the valid date range. It's worth checking because it could happen to anyone - even the iTunes app reviewer rejected the app for this reason. Luckily we were familiar with the issue, appealed and got a quick approval.
I'm trying to send push notifications to an app. The program, PushMeBaby, which a co-worker of mine used does not seem to work anymore. I get an -909 error from the SSLwrite command. I couldn't figure out the meaning of it.
Does anyone know a good tool/program that sends push notifications to the APNs-server?
or has anyone know, what the error code means?
Yours
Bujtor
Well... as it turns out the problem was the certificate.
Apparently it's not that easy to get the correct and valid push-certificate. My boss's third attempt succeeded. The Certificate Signing Request had to be made using the MAC i'm working on, where PushMeBaby is running. Otherwise there was no private key associated with the certificate. In addition the provisioning profil had to be made to only work for that one application.
I hope it helps others having the same problem.
I have some code which runs fine in simulator, but when I try to build for iPhone, I get a cryptic error:
CodeSign /Users/.../myApp.app (1 error)
error: CSSMERR_DL_MISSING_VALUE
That's it. No other references.
Sounds like it's something about my code signing privileges, but what exactly? My private key, certificate and provisioning profile should be OK, but this happens with all apps, so it's not app specific. I tried reinstalling the provisioning profile, but to no avail. What should I do to get rid of this error and make code sign work again?
Ok, this is a weird one:
I had a smart card reader connected, with a smart card with a private key and certificate on it, that I use for some signing and authentication operations. It has nothing to do with Xcode, but apparently this smartcard confused Keychain enough to spit out this error. Disconnected the card reader and signing works again as expected.