I've recently started developing iphone applications for a project at school and I've been having some problems testing push notifications. I've read I need to get some SSL certificate from the program portal, but I cannot find the link AppID where I am supposed to get them. Is it really necesary even though I am just starting out making some tests in XCode? What else do I need to run push notifications?
I've started coding the client side, but I cannot register for remote notifications. (I run registerForRemoteNotificationTypes:..., but it cannot register) I think it is because I don´t have the certificates, but I really don´t know.
Thanks!!
you need to be enrolled in developer programe.you can not test push notification for free.
Related
I'm quit new in iphone developing and I used to test my apps on my jailbreaken iPhone 3Gs without enrolling in the developer program.
However, I needed to implement push notifications from my server but all the tutorials I found refer to logging in the provisioning portal to obtain App ID which I can't access without the developer program.
So here is the question: Can I implement the push notifications without enrolling in the developer program ?!
No, the required certificates and profiles for your server need to be generated by Apple, so you can't forge them.
No, you wont be able to do that kind of communication while your app is closed. It will work only when the user is running your app thus making it useless.
I am developing an iOS App with Push Notifications. I am able to successfully test the push notifications using the Developer APN Certificate but it does not work with the Production APN Certificate.
I have ensured that the profiles in the iOS Developer Portal (adhoc / distribution) are generated after Push Notification is enabled for the APP ID and have taken care to use the correct UA_KEY and UA_SECRET in AppDelegate.m.
Can anybody please provide insights on as to what could be the possible reason(s) why Push notifications are failing using Production Certificate but working fine with Development Certificate.
I finally seemed to have sorted this out and posting back here in hope that it may help.
The key point which helped me to identify the problem was to turn on 'Debugging' in the UA Console to see the details errors. (This was actually the suggestion provided by their support team)
Most probably you have figured that out by now. Anyway, I think the problem caused by not including your Production UA_Key and UA_Secret in your UAConfig file. It's better to follow up with the sample they provide in their Resources page as you can't go wrong with their sample.
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.
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.
The iPhone i'm developing with (building the application to, not installed via ad-hoc) receives push notifications as it should. I've got an application that just sends dummy push notifications on command, and the dev iphone receives them consistently. However, I've distributed a beta build under the release configuration to several co-workers, and none of these builds of the app have received a single push notification. I've confirmed that the app prompts the user on first run for permission to receive push notifications, and I've also confirmed that everyone has answered "yes" to this prompt. Has anyone else experienced this problem? I feel like it has something to do with provisioning, but the apple developer portal is so vague about things, I very well could be missing something important.
Looks like I missed the part in apples push documentation where it states that apps distributed via ad-hoc use the apple production push gateway, not the apple dev push gateway. I was under the assumption that while developing the application, I always wanted to use the "development" push gateway...but that's what I get for using common sense.