I have a small question about iTunes connect beta testing.
So for this we have to upload a build to the app store and then enable internal tester. As Xcode does not allow us to sign an app with Ad Hoc provisioning profile to upload it to app store and it has to be the distribution profile to upload it to app store.
So my question is that when i sign it with distribution profile the push notification use the production server, and may be my production server is not ready at that time so how should we can get around this issue.
So there are two thing one the production server for the push notification and other is the production server for API calls. I can always use development server URLs but when i sign with distribution profile. I Think it will automatically use the production server for the Push notifications
Use the distribution certificate, and in your development server use the same distribution push certificate .PEM (you can re-use this .pem later on your distribution server).
Related
I have an app ,that is live on App Store, which uses Push notification as one of its features. While using development mode device token is successfully created but when I use production provisioning profile device token is not generated.I am using old production provisioning profile on which the app is live. So should I create new Production Provisioning Profile or am I doing something wrong.
I am depending on push notification services in my iPhone app, and tested with development and ad-hoc production certificates it is working fine. But when I submit the app to the App Store, I have to create Appstore production certificate, is there any way to test APNS with this certificate before publishing the application to Apple.
I have been able to Package an Ad Hoc distribution which provides an .ipa for iOS devices that I have specified in the Apple Developer Center.
I then send the .ipa to the specified devices using Diawi.com (which is an awesome service like test flight), but can be used prior to submitting to the app store (like the old test flight)
Here is the actual problem. Using the Appstore production profile, we can create an .ipa file but we cannot install it on the device directly, it has to come from Appstore. It can only be uploaded to the App Store. So, the problem is as we cannot install the package on iPhone we cannot send the push notifications to test it before submitting the package to Appstore. So, technically it is not possible to test the set-up. I was just curious to know if somebody cracked it.
The APNs production certificate is universal, so it does work in both development and distribution, see Apple documentation here.
For the AppStore distribution certificate:
Before uploading your app to iTunes Connect, optionally distribute it for testing on registered devices using an ad hoc provisioning profile or team provisioning profile.
Here's the whole run-through on how to achieve this: App Distribution Guide.
Another option is using TestFlight, details can be found under the previous link.
I am about to submit my app and not sure what I should do about the certificates used for the push notifications. I am using Parse.com for my backend. Do I need to update the certificate for the database to production for when Apple review the app or do I leave it as development and do it after release?
Submit it with Development Certificate.
And When Your App Is Approved then Update it to Production Certificate.
Apple requires you to have your backend set up production ready for review, otherwise your app is likely to be rejected.
See dot 2.9
Before the new build distribution system rolled, you can either signed your apps with development or adhoc certificates.
Now it seems the new Testflight only accepts IPA files signed with AppStore provisioning files only.
Can I still have a separate environment for sandbox push notifications?
Thanks!
You can still have a separate environment for sandbox push notifications, just not through the new TestFlight. You need to use an alternate service such as Beta by Crashlytics or Hockey App. And these services have the same limitations of the old TestFlight e.g. having to add your testers on to your developer account.
My app is not released yet, so you couldn't find it in the App Store. But it is being used by a group of private beta users (through the iOS TestFlight service). And it is hitting my production server, which is the reason for the question.
In the situation described above, what .p12 do I use? the Dev certificate or the Distribution certificate? I am asking because I am not clear on whom the distinction is for. As far as my server is concerned I don't care which one is used. I just need to send push notifications, and as long as the users get them, I am happy. And since I am using my production server, I figure I should use the production/distribution certificate. But I have a suspicion that my server -- dev or production -- has nothing to do with it. And which certificate I use may entirely have to do with the App Store. So will someone please clarify for me? Thanks.
From http://www.raywenderlich.com/32960/apple-push-notification-services-in-ios-6-tutorial-part-1
Development If your app is running in Debug mode and is signed with the Development provisioning profile (Code Signing Identity is “iPhone Developer”), then your server must be using the Development certificate.
Production Apps that are distributed as Ad Hoc or on the App Store (when Code Signing Identify is “iPhone Distribution”) must talk to a server that uses the Production certificate. If there is a mismatch between these, push notifications cannot be delivered to your app.