Push notification certificate generation - cocoa-touch

We succesfully set up and tested the sandbox Push notification certificate, now we are going to test the production certificate. We generated it in the same way as the development, and changed the apple adrress to the proper push notification service. But we don't get the push somehow although we even builded the app for distribution. I've heard also that the device tokens should be different to test production, what does it mean? Do I have to test on other devices?? Thanks

The device token will be different for the distribution certificate so the app have to send new token to the server (the one you receive in didRegisterForRemoteNotificationsWithDeviceToken).
Also make sure your distribution mobileprovisioning profile does have "aps-environment" string in it set to "production". If not - recreate the mobileprovisioning profile for the app.

Related

pushnotification for Advertisement in iOS?

I have developed an iOS app which uses a third party framework for showing Ads inside the app.
I would like to know whether to enable push notifications for the AppId While submiting App?
its depends on how the Ads SDK works.
most likely it works without the APNS (apple push notification server), but its also possible that it does, and from that screenshot, there is a good chance.
I would recommend enabling push notification, just in case.
go to the apple's developer member center, go to your App, press edit, enable "push notifications" and create certificate for production, and also new provisioning profiles.
Don't forget to download the APNS certificate, create a PEM file to implement it on the server side (most likely they'll require that in case they do use APNS)
for more information on how it's done:
http://www.raywenderlich.com/32960/apple-push-notification-services-in-ios-6-tutorial-part-1
Enabling push notification is not required for Ad integration while submitting app to the App Store.

Apple Push Notification issue

I am trying to implement APNS for my App and am hitting a wall while trying to generate a provisioning profile. I followed the instructions to create an APP id and was able to generate an SSL certificate for my App (the type is shown to be APNs development IOS). However, when I try to generate a provisioning profile, following the screen where I choose the AppID of my app, I do not see the SSL certificate I generate for this app. In the certificates list, I only see a certificate of type 'IOS development' that was created previously. I have been stuck on this issue for a while. Can someone please help?
Thanks
I resolved my own query. we need to add iOS development certificate while creating profile for APNS. You should have the p12 of that iOS development certificate.

Device Token null when deploying app as ad-hoc (Urban Airship)

I implemented the Urban Airship library into my application and I can successfully send push notifications to a specific device in development mode. After startup I get the device token and save it into a mysql database. However, when I use the app in ad-hoc mode, the device token is always (null).
APP_STORE_OR_AD_HOC_BUILD is set to YES
and the APP Key and APP-Secret for both production and development are correct.
Any ideas how to get the device token in ad-hoc/appstore mode?
Edit:
Identical question has been posted in the Urban Airship Forum.
For me also same thing happened. What we did to solve problem is just recreated new adHoc provisioning profile. Then we got alert asking to install push notification. Its one of the major issue in iOS push notification. We must configure push nofitiation SSL certificate before creating provisioning profile.

Modal alert request for push notifications

debuggers,
I have created an app that embeds push notifications.
For one or other reason the user does not get asked for permission on the first load.
In the past I have used push notification and everything seemed to work, the code for is pretty much "copy-pasted".
I requested a certificate from a certificate authority (keychain)
I enabled push notification and downloaded a new certificate
Uploaded the certificate to apple and received a validated development and distribution certificate.
I downloaded a new development + production provisioning profile.
I signed the app with the provisioning profile.
When I open the provisioning profile in textedit I do see the following key:
aps-environment
I used this profile to sign the app and install it on to the device!
I have tried several methods like setting the time on my phone to days ahead, rebooting, re-installing.
I use urban airship as a push service!
Does anyone have any idea what is going wrong?
Do you have [UAPush setDefaultPushEnabledValue:NO] set by any chance?
By setting this value to NO UrbanAirship delay prompting users to enable push notifications until you are ready to ask. This gives you a chance to explain what they are used for instead of it popping up right when the app starts.
Then later you can enable them by calling
UIRemoteNotificationType notificationTypes = [[UIApplication sharedApplication] enabledRemoteNotificationTypes];

Push notifications not asking permission when user loads app

Hi I have just released my app update with push notifications added into it. I was worried that it would not work properly so I did a bunch of testing. First with just a development certificate and then a production certificate using adhoc. Both ended up working and I was pleased when the adhoc worked.
Anyways the update has been live for about 8 hours now and for some reason push isn't working. I checked with my friend and have realized that the user is not being asked whether he wants to accept push notifications from my app. Which means when the token gets sent to my server, its appearing as (null). I have no idea why this is happening. When he goes into device settings --> notifications ---> my app does not appear on any of the lists (receiving push notifications or not receiving).
This is the code in my delegate that should trigger the request:
[[UIApplication sharedApplication] registerForRemoteNotificationTypes:
(UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
If anyone knows why this is happening, input would be much appreciated. Thanks!
We thought we were having this same issue but found out that the app was actually working correctly. The user is only prompted once even if they uninstall and reinstall the app.
We were testing it by uninstalling the app and then reinstalling. iOS would remember how we had responded previously on that device and would not prompt again leading us to think there was a problem.
We found the best way to test is with the simulator and doing a "Reset Content and Settings".
After configuring your app for push notifications and generating your SSL certificates you must also generate new provisioning profiles.
The developer portal displays this message on the App ID configuration page:
After you have generated your Client SSL certificate, create a new provisioning profile containing the App ID you wish to use for notifications.
If you did not update your App Store provisioning profile after setting up push the OS will not provide you with a push token.
If this is your problem you just need to generate a new App Store distribution profile and submit a recompiled version signed with that profile.