Step-by-Step Guide to Publishing in the Apple App Store Using a Mac


Requirements

To publish an app through the Apple App Store, you need to have an Apple Developer account and be a member of the iOS Developer Program. Your app also needs to meet Apple's App Store guidelines.

Files Needed for iOS Publishing:

  1. Identity - a unique ID for an app  that maps to the Bundle Identifier in the Apple Developer Center
  2. Distribution Certificate & Private Key (generated in Apple Developer Center)
  3. Distribution Provisioning Profile 
  4. Optional: Push Notification Certificate
  5. Icons
  6. Loading Screen


Setting up an Identity

  1. To Set up an Identity, go to the Apple Developer center iOS Provisioning Portal, and click the App IDs tab. 
  2. Click the New App ID button (top right), give the app id a name, and give it a Bundle Identifier (by convention, these take the form com.domain.appname, so for example, com.brightcove.myfirstapp)
    note: copy and save the Bundle Identifier you created because you will need to enter it into the App Cloud Studio when publishing your app
  3. Click Submit within the Apple developer center and it will create an App ID

Creating a Distribution Certificate & Private Key (on a Mac)

  1. Now you need to set up a distribution certificate. To do this, you will first need to generate a certificate request from your computer. On a Mac, you should do this by opening the Keychain Access application found in the Utilities.
  2. Go to Keychain Access - Choose Keychain Access -> Certificate Assistant ->Request a Certificate from a Certificate Authority.
  3. Enter your email address and name, and select Request is Saved to disk to save the file CertificateSigningRequest.certSigningRequest to your desktop.
  4. Now go back to iOS Provisioning Portal and click the Request Certificatebutton on the Distribution tab.
  5. Click Choose File to select the certificate request file on your desktop, and then click Submit. You will see your certificate appear with the status Issued.
  6. Refresh the page, and additional information will appear: the Expiration Date, and Download and Revoke under Actions.
  7. Click the Download button, and save the certificate file.
  8. After the file downloads, locate the distribution_identity.cer file in your downloads directory, and double-click it to import it to Keychain Access.
  9. Now return to Keychain Access and locate the certificate with the name beginning iPhone Distribution.
  10. Expand it to reveal the attached private key, and select both the certificate and private key
    note: it is very important to select both files
  11. With both items selected, right click to export them to a .p12 file that you can save on your desktop or elsewhere. You will need to upload this file to App Cloud during the app submission process.
  12. As you save the file, you will have the option of adding a password to protect the file - if you do, just be sure to remember what the password is. You will also be asked to enter your machine password, as you are for many Keychain Access actions.

Creating a Distribution Provisioning Profile

  1. In the Apple Developer Center, go to the Provisioning tab > Distribution and select new profile
  2. Leave the Distribution Method as App Store
  3. Give it a profile name
  4. Select the App ID that you created for this app and click submit
  5. Wait for the provisioning profile to be created (refresh the page)
  6. Click to download the file to your machine. You will need to upload this file into the App Cloud Studio.

Setting Up Push Notifications

  1. If you are going to use Push Notifications in your app, you will now need to set up another SSL certificate for push notifications. Unlike the distribution certificate, this one is specific to the app, so you will work from  the app id you created.
  2. Go to Keychain Access - Choose Keychain Access -> Certificate Assistant -> Request a Certificate from a Certificate Authority.
  3. Enter your email address and name, and select Request is Saved to disk to save the file CertificateSigningRequestPush.certSigningRequest to your desktop.
  4. Now return the iOS Provisioning Portal in the Apple Developer Center, go to the App IDs section, find the ID you created earlier, and click Configure.
  5. In the new page that opens, check the box beside Enable for Apple Push Notification service. Now you will be able to click the Configurebuttons, and since you are going to submit this app, you will need a Production Push SSL Certificate.
  6. Click configure, and a dialog will open up with instructions
  7. Click Continue to go to the next screen
  8. Click the Choose File button and select the CertSigningRequestPush.certSigningRequest file you just created, click Generate
  9. After the certificate is generated, click Continue.
  10. Click Download to download the file to your computer and click the show in folder option to navigate to where the file is located
  11. Copy the file and save it to your Desktop or some other location
  12. Find the downloaded certificate file, and double-click it to import it into Keychain Access.
  13. In Keychain Access, again expand the certificate to reveal the private key, selectboth items, and right click to export them to the desktop as a .p12 file
  14. Now you will need to convert the .p12 file to a PEM file using OpenSSL. OpenSSL is included in the Mac OS
  15. To start OpenSSL open Terminal and type OpenSSL at the command prompt and press return to get an OpenSSL command prompt.
  16. Now type: pkcs12 -in <your p12 with full path> -out <the PEM filename> -nodes
    note: Where it says <your p12 with full path> you can drag and drop your .p12 file into Terminal to easily enter the full path of the file
    note: Where is says <the PEM filename> you can use a file name such as PushCert.pem
  17. The PEM file that is generated is what you will need to upload into the App Cloud Studio

Icons

An iOS app uses icons to represent the app in the Apple App Store and to launch the app on the device itself after it's installed. You can upload an image file and App Cloud will create these icons for you. All images should have a square aspect ratio (equal width and height) and be in PNG format. Image files may be not more than 1 Mb in size.

Loading Screen

When a user launches your app, the iOS device displays a fullscreen graphic. Upload an image file that the app can use for this purpose. For an iPhone app, this file must be 640x960 exactly. For an iPad app, provide two loading screen image files, one with portrait orientation (768x1024 pixels) and the other with landscape orientation (1024x768 pixels)
Remember that you can resize images using the App Cloud image transcoding service.
You can Follow this for more info

Comments

  1. hellanadamJuly 31, 2017 at 3:51 PM

    I wondered upon your blog and wanted to say that I have really enjoyed reading your blog posts. Any way I’ll be subscribing to your feed and I hope you post again soon.
    ios App Development Company
    mobile App Development Company

    ReplyDelete

Post a Comment

Popular posts from this blog

Launch iPhone simulator without Xcode.

To launch simulator you have to way. 1. Using Terminal 2. Using UI. 1 Using UI. ->    Open Finder and then press   shift +  cmnd + g   or Go -> Go to Folder then enter this address /Applications/ Xcode . app / Contents / Developer / Platforms / iPhoneSimulator . platform / Developer / Applications the double click on simulator.app. 2 Using Terminal  Open terminal and then press this command open / Applications / Xcode . app / Contents / Developer / Platforms / iPhoneSimulator . platform / Developer / Applications / iPhone\ Simulator . app or open `xcode-select --print-path` / Platforms / iPhoneSimulator . platform / Developer / Applications / iPhone\ Simulator . app To run application follow this, http://cocoamanifest.net/articles/2011/12/running-your-ios-app-in-the-simulator-from-the-command-line.html
Read more

How to Make REST api call in Objective-C.

We can call using this. NSString * twitterUrl = @ "YourUrlString" ; NSString * resp = [ self makeRestAPICall : twitterUrl ]; and method is -( NSString *) makeRestAPICall : ( NSString *) reqURLStr { NSURLRequest * Request = [ NSURLRequest requestWithURL :[ NSURL URLWithString : reqURLStr ]]; NSURLResponse * resp = nil ; NSError * error = nil ; NSData * response = [ NSURLConnection sendSynchronousRequest : Request returningResponse : & resp error : & error ]; NSString * responseString = [[ NSString alloc ] initWithData : response encoding : NSUTF8StringEncoding ]; NSLog (@ "%@" , responseString ); return responseString ; } 1 2 3 4 @ interface ViewController : UIViewController < NSURLConnectionDelegate > {      NSMutableData * _responseData ; }
Read more

id vs NSObject

There's often confusion about the difference between the following three declarations in Objective-C: id foo1; ->   It simply declares a pointer to some Objective-C object,  If you don't want (or can't have) any type checking, then use   id . if you do want compile-time type checking, you must decide between the second and third cases.. NSObject *foo2; ->  declaring a generic pointer of type NSObject* id<NSObject> foo3; ->   pointer to  any  object that behaves like an NSObjec , "foo3 is a pointer to an object of any type that behaves like an NSObject" , ( you really don't care what class the object is, you only care that it  behaves  like an NSObject.) The first one is the most common. It simply declares a pointer to some Objective-C object (see  /usr/include/objc/objc.h ).  id  gives the compiler no information about the actual type of the object, so the compiler cannot do compile-time type ...
Read more