DPS Publishing Companion Guide

DPS Publishing Companion Guide
Adobe iOS Publishing Companion Guide
Professional & Enterprise Edition
Last updated September 16, 2014
next Page ›
table of contents
In this guide
Legal notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
A checklist for building your first app . . . . . . . . . . . . . . . . . . . . . . . . . 5
A checklist for building your second app. . . . . . . . . . . . . . . . . . . . . . 6
Set up Apple push notifications (optional). . . . . . . . . . . . . . . . . . . . 42
Create a Development Push Certificate Signing Request . . . . . 42
Generate a Development Push Certificate . . . . . . . . . . . . . . . . . 46
Create a p12 Development Push Certificate . . . . . . . . . . . . . . . . 48
Create a Production Push Certificate Signing Request . . . . . . . 50
Generate a Production Push Certificate . . . . . . . . . . . . . . . . . . . 53
Create a p12 Production Push Certificate. . . . . . . . . . . . . . . . . . 55
Build your folios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Create mobileprovision files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Create a development mobileprovision file. . . . . . . . . . . . . . . . . 57
Create a distribution mobileprovision file. . . . . . . . . . . . . . . . . . 61
Use the right Adobe ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Create required assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Publish folios for multi-folio apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Create an iTunes Connect record for the app. . . . . . . . . . . . . . . . . 69
Certificates required for building apps. . . . . . . . . . . . . . . . . . . . . . . . 11
Create In-App Purchases for retail folios. . . . . . . . . . . . . . . . . . . . . 76
Enroll in Apple’s iOS Developer Program. . . . . . . . . . . . . . . . . . . . . 12
Provide bank and tax information to Apple (if you are
offering paid content). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Set up subscription apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Generate or view a shared secret. . . . . . . . . . . . . . . . . . . . . . . . . . 80
Create an In-App Purchase for a retail subscription . . . . . . . . . 82
Create an In-App Purchase for a free subscription app. . . . . . . 84
Enable Newsstand in iTunes Connect . . . . . . . . . . . . . . . . . . . . . 85
Set up a third-party entitlement server (Enterprise only). . . . . 85
Decide which type of viewer app to create. . . . . . . . . . . . . . . . . . . . 7
Read the App Store Review Guidelines for iOS apps. . . . . . . . . . . 15
Download and install Xcode on your Mac. . . . . . . . . . . . . . . . . . . . 16
Create certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Who creates the certificates? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Create a Development Certificate Signing Request . . . . . . . . . . 18
Generate a Development Certificate . . . . . . . . . . . . . . . . . . . . . . 22
Create a p12 Development Certificate . . . . . . . . . . . . . . . . . . . . . 24
Create a Distribution Certificate Signing Request. . . . . . . . . . . 26
Generate a Distribution Certificate . . . . . . . . . . . . . . . . . . . . . . . 29
Create a p12 Distribution Certificate . . . . . . . . . . . . . . . . . . . . . . 31
Test your certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Create an App ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
checklists
‹ previous
next
›
Build the app with DPS App Builder. . . . . . . . . . . . . . . . . . . . . . . . . . 86
Test the development app. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Test an app with free content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Test an app with retail content. . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Download the distribution app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Submit your app to the App Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Wait for approval from Apple. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Update an app. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
iOS publishing troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Register your test iPads/iPhones with Apple . . . . . . . . . . . . . . . . . 38
Page ~ 2
table of contents
Legal notice
THE CONTENTS OF THIS GUIDE is Adobe Confidential and subject to the Terms of Use, is furnished
under license and may be used or copied only in accordance with the terms of such license. No part of
this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means,
electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems
checklists
‹ previous
next
›
Incorporated.
Please note that the content in this guide is protected under copyright law even if it is not distributed
with software that includes an end user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and
should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated
assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational
content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be
protected under copyright law. The unauthorized incorporation of such material into your new work could
be a violation of the rights of the copyright owner. Please be sure to obtain any permission required from
the copyright owner.
Page ~ 3
table of contents
Introduction
IF YOU ARE READING THIS GUIDE, you are in the process of creating an iOS app with Adobe Digital
Publishing Suite.
checklists
‹ previous
First, let’s make sure you’re using the right guide. You should be either a Professional or Enterprise sub-
next
scriber to the Digital Publishing Suite. If you’re a Creative Cloud member or interested in purchasing a Single
›
Edition license, download the “Step-by-Step Guide for Single Edition.” It’s available from the Help menu of
the DPS App Builder. If you’re creating an app for Android devices, see this article: .
This process of submitting an app to the App Store can be completed by anyone willing to read directions,
pay attention to detail, and follow step-by-step instructions. Most of the steps do not require an understanding of Adobe InDesign. For this reason, you may choose to enlist the help of a co-worker or someone else in
your company to help you with this process.
Don’t wait until the last minute to read this guide. You can expect to spend two or three hours completing
all these steps. You may wish to break this into a couple of sessions. Once you have completed the steps, you
The DPS tools are
revised frequently.
will need to wait for Apple to approve or reject your app. As of this writing, this process is typically taking
This guide is up to date
about seven days.
for the March 2014
Apple governs the app submission process. Many of the steps in this guide describe processes that will take
place on various Apple websites. You must use a Macintosh computer to create the certificates required for the
version of the DPS tools.
submission and for the final upload of the app to the App Store.
Apple
STEP-BY-STEP
INFORMATION with a gray background
indicates that the task must be performed
on an Apple website. For more information about these tasks, refer to Apple
documentation at bit.ly/N9sNck and
bit.ly/N9fBUV or contact Apple.
Page ~ 4
A checklist for building your first app
table of contents
Creating your first app? Do these things ahead of time, while still working on your folios:
|
Enroll in Apple’s iOS Developer Program
Read the App Store Review Guidelines
|
Create certificates
|
|
page 16
These steps
are required by Apple Computer and completed on Apple websites.
‹ previous
next
›
page 33
Register your test iPads with Apple
|
|
page 17
Test your certificates
Create an App ID
page 12
page 15
Download and install Xcode on your Mac
checklists
|
page 38
page 34
Create mobileprovision files
Create required assets
|
|
page 57
page 65
Assign an Application role to an Adobe ID
|
page 9
Do these things when you’re ready to publish:
Build the app with DPS App Builder
Test the development app
|
|
page 86
page 87
Download the distribution app
|
page 90
Submit the distribution app to the App Store
Wait for approval from Apple
|
|
page 91
page 93
Page ~ 5
A checklist for building your second app
table of contents
Already created one app, and on to your second (or third)? There are less steps to complete the second time around.
Do these things ahead of time, before working on your folios:
Create an App ID
|
page 34
Create mobileprovision files
Create required assets
|
|
page 57
page 65
Assign an Application role to an Adobe ID
|
checklists
These steps
are required by Apple Computer and completed on Apple websites.
‹ previous
next
›
page 9
Do these things when you’re ready to publish the app:
Build the app with DPS App Builder
Test the development app
|
|
page 86
page 87
Download the distribution app
|
page 90
Submit the distribution app to the App Store
Wait for approval from Apple
|
|
page 91
page 93
Page ~ 6
table of contents
Decide which type of viewer app to create
THERE ARE FOUR BASIC TYPES OF VIEWER APPS: Single-Folio, Multi-Folio, Subscription, and
Enterprise-signed (for internal publishing).
Before you begin building your app, understand which type of app you want to create. Also decide
whether you want the folios in your app to be free or retail.
checklists
‹ previous
next
›
To learn more about the different types of viewer apps, see the article (and video) at adobe.ly/jtBEOs.
Page ~ 7
table of contents
Build your folios
YOU HAVE PROBABLY ALREADY BUILT, or begun to build, the InDesign files for your app, and have
created Digital Publishing Suite articles and assembled them into a folio.
You or a different member of your team will use the Folio Builder panel in InDesign to create one or
more folios. Creating a folio allows you to preview your completed app using the free Adobe Content
checklists
‹ previous
next
›
Viewer app on your device. This will let you view all of the content and interactivity in your app.
The process of creating and publishing folios and articles is beyond the scope of this guide. To learn
more about how to use the Folio Builder panel to create folios and preview them on your iPad, see the
Online Help at adobe.ly/PjSo8K.
When you create the folios that will appear in your app, you need to use the right Adobe ID, which we’ll
discuss next.
Page ~ 8
table of contents
Use the right Adobe ID
FOR EACH MULTI-FOLIO APP YOU CREATE, you must use a different Adobe ID. In fact, you’re better off using different Adobe IDs for each app, including single-folio apps, to avoid mixing analytics data.
Use the Account Administration tool to assign an Application role to an Adobe ID. Use this Adobe ID to
create and publish folios. In the App Builder, specify this Adobe ID in the Title ID field.
checklists
‹ previous
next
›
To learn more about assigning Application roles to Adobe IDs, see the article at adobe.ly/RqCOH1. In
addition, see the Adobe DPS Getting Started Guide at http://adobe.ly/156jmbh.
Folio Builder panel
DPS App Builder
Page ~ 9
table of contents
Publish folios for multi-folio apps
checklists
FOR EACH ISSUE THAT WILL APPEAR IN YOUR LIBRARY, you must publish a folio. Use the Folio
Producer Organizer to publish folios. You can publish folios before and after you create your app.
•
If you’re publishing a folio that doesn’t cost money, simply publish the folio as Public and Free. If
you publish the folio using the same Adobe ID that you use as the Title ID in DPS App Builder, the
‹ previous
next
›
folio will be available in your app library as soon as you publish it. No other action is required.
•
If you’re publishing a folio that costs money, you need to create an in-app purchase in iTunes Connect that has a unique Product ID. In Folio Producer Organizer, publish the folio as Public and Retail. Specify the exact same Product ID that you used for the in-app purchase. Details about creating
in-app purchases are explained later in this guide.
•
Use a different Product ID for each folio. Use the same Product ID for renditions of the same folio.
To learn more about publishing folios, see the article at http://adobe.ly/14yQPLa.
Folio Producer Organizer
Page ~ 10
table of contents
Certificates required for building apps
FOR EACH APP YOU CREATE, Apple requires various certificates and files. The primary purpose of
this guide is to help you create these required files.
•
Developer P12 certificate (and password)
•
Distribution P12 certificate (and password)
•
Developer mobileprovision file
•
Distribution mobileprovision file
•
Developer push P12 certificate and password (required only if push is enabled)
•
Production push P12 certificate and password (required only if push is enabled)
checklists
‹ previous
next
›
After you use the Apple Developer site to create these certificates and mobileprovision files, you use the
DPS tools to specify these files, along with image files and other app configuration details discussed later in
this guide.
For a more detailed checklist of each app type, see the help article at http://adobe.ly/15CWNHC.
Page ~ 11
Apple
STEP-BY-STEP
table of contents
Enroll in Apple’s iOS Developer Program
checklists
YOU MUST BE ENROLLED in Apple’s iOS Developer Program to submit your app to the
‹ previous
App Store. The iOS Developer Program costs US$99/year. You need to keep your enrollment current and paid for as long as you want your app to appear on the App Store.
If you have not already signed up for the iOS Developer Program, visit bit.ly/Rjz90j to
next
get started. For purposes of creating DPS apps, you can enroll as either an individual or a
›
company.
Someone else in your company may already be enrolled in the iOS Developer Program.
You may be able to ask your IT department to create the required App ID, certificates, and
mobileprovision files. If so, this will make the process much easier for you. No knowledge
of InDesign or Adobe DPS is required to create these items, so this is an easy task to dele-
adobe tip
gate to someone else.
As you move through the
After you enroll in the iOS Developer Program and submit your payment, Apple will
send you an email message that prompts you to activate your account.
Provide bank and tax information to Apple (if you are offering paid content)
If you wish to make your app or any of your app’s folios available for sale through Apple,
steps in this guide you will
create an Adobe ID and
password, Apple ID and pass-
you must agree to the iOS Paid Applications agreement. If your app and content is going
word, certificate passwords,
to be free, you can skip to page 15.
and a unique App ID for each
1. Go to itunesconnect.apple.com. You will need to sign in with your Apple ID.
2. Click on Contracts, Tax, and Banking.
app that you create. Don’t get
all these IDs and passwords
confused! Create a system to
help you keep all this straight.
Page ~ 12
Apple
STEP-BY-STEP
3. Click the Request button next to the iOS Paid Applications contract.
table of contents
checklists
‹ previous
next
›
4. If acceptable, accept the terms of the agreement, and click the Submit button.
Page ~ 13
Apple
STEP-BY-STEP
5. The iOS Paid Applications contract will appear in the Contracts in Process section. Click on the
Set Up buttons below Contact Info, Bank Info, and Tax Info, and provide the information requested.
table of contents
checklists
‹ previous
6. Once you’ve provided all the requested information, you will need to wait for Apple to approve the
contract. When the contract is approved, it will move to the Contracts in Effect section.
next
›
For more information, see the “Managing Contracts, Taxes, and Banking” section of Apple’s iTunes
­Connect Developer Guide at bit.ly/NtQgqX.
Page ~ 14
Apple
STEP-BY-STEP
table of contents
Read the App Store Review Guidelines for iOS apps
APPLE REVIEWS ALL APPS that are submitted to the App Store to be sure that the apps
meet the App Store Review Guidelines. Apps that do not meet these guidelines will be reject-
checklists
‹ previous
ed by Apple. With this in mind, it is good to review these guidelines before you get too far
into the process of developing your app. This will pay off in the end by ensuring that your app
passes Apple’s review process.
next
›
You can read more about the App Store Approval Process at bit.ly/RjAapd and the App Store
Review Guidelines at bit.ly/RjAe8i. You will need to sign in with your Apple ID.
Page ~ 15
Apple
STEP-BY-STEP
table of contents
Download and install Xcode on your Mac
CERTAIN STEPS IN THIS PROCESS require you to have Xcode installed
on your Macintosh computer. Xcode is Apple’s “development environment”
checklists
‹ previous
for creating Mac, iPhone, and iPad apps. But don’t worry, you aren’t going
to need to learn Xcode or any programming. It’s a good idea to install
Xcode. The latest version of Xcode can be downloaded from bit.ly/RjArsh.
next
›
If you are running an older version of Mac OS X, and need an older version
of Xcode, you can find previous versions at bit.ly/RjAyE5. To use Application Loader, Mac OS X 10.7 or later is required.
Xcode is an approximately 1.5 gigabyte download. Depending on your
Internet connection speed, this download may take awhile. Be prepared
to do this step well ahead of time so that you can afford to wait.
Although we recommend installing Xcode, it is not required. If
you install Xcode, the Application Loader utility and
a WWDR intermediate certificate are installed automatically.
If you don’t install Xcode, you’ll
need to install the Application
Loader and the WWDR certificate
individually.
One more note about Xcode.
If you refer to Apple developer
documentation when building DPS
apps, keep in mind that the DPS
App Builder performs certain tasks
that other developers use Xcode to
perform.
Page ~ 16
Apple
STEP-BY-STEP
table of contents
Create certificates
THE DPS APP BUILDER will generate two different apps—a development app and a distribution app. The development app is used for testing; the distribution app is what you’ll
checklists
‹ previous
submit to Apple once you’ve tested and approved the development app. Apple requires both
apps to be signed by a valid “certificate” before they can run on the iPad. In this section,
you will learn how to create two required p12 certificates.
next
›
Note: You can use the same p12 certificates for multiple apps. They are not tied to the App ID.
However, each app you create requires a separate App ID and separate mobileprovision files
(described later).
Who creates the certificates?
The steps in this guide assume you will create the required certificates. If you work for
an organization, someone else in your company might be responsible for creating the
required ertificates. If so, make the necessary arrangements to use those certificates for
building your app. Certificates and mobileprovision files can be created on one computer
and used on a different computer.
Overview
The process of creating a p12 certificate file might seem complicated, but it’s not that difficult if you follow the steps carefully.
Creating the certificates involves a back-and-forth process between the Apple Developer
site and the Keychain Access utility on your computer. You use the Keychain Access utility
to create a certificate signing request (a different one for each certificate), and then submit the signing request in the Apple Developer
site. Then you download the certificate (.cer) file and open it in the
Keychain Access utility, which you use to export the p12 file. You will
complete this process twice: once for the development (testing) app
and once for the distribution (submission) app.
Page ~ 17
Apple
STEP-BY-STEP
Create a Development Certificate Signing Request
1. On the Apple iOS Developer site, go to “Certificates, Identifiers & Profiles” at bit.ly/OVbhu5. Sign in
with your Apple ID.
2. Click Certificates on the left side of the window.
2
3. Click Development on the left side of the window under Certificates.
table of contents
checklists
3
Selecting the options on the left side displays the certificates of each category. At this stage, you
shouldn’t have any development certificates. You just need one development certificate for testing all
your iOS apps.
4. Click the Plus icon in the upper right corner of the window to start creating a certificate.
4
‹ previous
next
›
2
4
3
Page ~ 18
Apple
STEP-BY-STEP
5. In the “What type of certificate do you need?” section, select iOS App Development.
Click Continue.
table of contents
checklists
‹ previous
next
›
Page ~ 19
Apple
STEP-BY-STEP
As indicated on the Apple Developer site, you’ll now use the Keychain Access utility to
create a Certificate Signing Request (CSR).
table of contents
6. Open the Keychain Access utility, found in the Utilities folder in your Applications
folder.
7. Click on the My Certificates category on the left.
checklists
7
8. Click on an empty space in the window on the right to ensure that no existing keys or
certificates are selected. 8
‹ previous
next
7
8
›
During this process, you
are going to be creating
several files that you will
need to keep track of. It
9. Choose Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority.
is helpful to create a new
folder in an easy-to-access
location to store all of
these “bits and pieces”
that you will need later
in the process.
Page ~ 20
Apple
STEP-BY-STEP
10.For User Email Address, specify a valid email address.
10
11.For Common Name, enter the name of your company or division. This certificate can
be reused for multiple apps that you might create, so you don’t need to enter the app
name here. 11
12.Leave the CA Email Address field blank.
13.Select Saved to Disk.
table of contents
checklists
12
13
‹ previous
next
10
›
11
12
13
14.Click the Continue button.
15.Specify the name of the certificate signing request and
where the file will be saved, and click Save. You will use
this file to create a development certificate in the next
section.
16.When the certificate request is created, click Done.
Page ~ 21
Apple
STEP-BY-STEP
Generate a Development Certificate
Now that you’ve created the certificate signing request file, you need to submit it to the Apple Developer
table of contents
site to create the required development certificate.
1. In the Apple Developer site, click Continue to advance to the “Generate your certificate” screen.
Click Choose File, and double-click the certificate request file you just saved in the previous steps.
2. Click Generate.
checklists
1
2
‹ previous
next
›
1
2
Page ~ 22
Apple
STEP-BY-STEP
Your development certificate is generated.
table of contents
checklists
‹ previous
next
›
3. Click Download, and then download the certificate to a known location.
This development certificate is called ios_development.cer. This file is required to create your
p12 certificate in the Keychain Access utility. You’ll do that next.
Page ~ 23
Apple
STEP-BY-STEP
Create a p12 Development Certificate
table of contents
1. In the Finder, locate the ios_development.cer file you created, and double-click it.
This launches the Keychain Access utility and installs the certificate.
2. To see if the certificate was installed correctly, click on the Keys category on the left,
and then click the right-pointing arrow to open the private key. You should see the
certificate beneath the private key. If double-clicking the .cer file does not install the
certificate, launch Keychain Access and choose File > Import Items to specify the
.cer file. If that still doesn’t work, exit and re-start the Keychain Access utility and try
again.
checklists
‹ previous
next
›
adobe tip
If you forget the p12 certificate password you create
here, there is no way to
3. With Keys selected on the left, Control-click or right-click the private key associated
with your certificate, and choose Export “[name].”
Important: Control-click the private key (highlighted in red below), not the certificate.
retrieve it—you would need
to create your p12 certificates
all over again. So don’t forget
this password! You can use
the same password for the
distribution and development
p12 certificates.
Page ~ 24
Apple
STEP-BY-STEP
4. Save your key in the Personal Information Exchange (.p12) file format. Specify a name that distinguishes it from the p12 file you’ll create for the distribution certificate. For example, we’re naming
our development certificate Pluralist Design Development.p12. Later, we’ll name the distribution
p12 certificate “Pluralist Design Distribution.p12”. Save the certificate into a known location where
you won’t lose track of it. Do not use any characters other than a–z, 0–9, hyphens, underscores, and
spaces in the filename.
table of contents
checklists
‹ previous
next
›
5. When prompted, specify a password for your p12 certificate, and click OK.
Remember this password. Do not use a blank password. You will need this password later when
building your app in the DPS App Builder.
6. Specify the Administrator password for your computer, and click Allow.
Page ~ 25
Apple
STEP-BY-STEP
You now have one of the two p12 certificates you need. You can now delete the certificate signing request
file and the ios_development.cer file; they are no longer needed, and you don’t want to accidentally select
table of contents
the wrong file later. Keep your development p12 certificate in a safe place. Next, you will follow similar
steps to create the distribution p12 certificate.
checklists
‹ previous
Create a Distribution Certificate Signing Request
One p12 certificate down, one to go. You’ve created the development .p12 certificate for your testing apps.
Now you need to create the distribution p12 certificate for your production apps.
next
›
1. If the Keychain Access utility is still running on your computer, choose Keychain Access > Quit
Keychain Access to quit the program (leaving the Keychain Access utility running while doing steps
2–4 can cause problems).
2. On the Apple Developer site, click Production (under Certificates) on the left side of the window.
2
Again, you need only one distribution certificate.
3. Click the Plus icon in the upper right corner of the window to start creating a certificate.
3
3
2
Page ~ 26
Apple
STEP-BY-STEP
4. Under Production, select “App Store and Ad Hoc.” Then click Continue.
table of contents
checklists
‹ previous
next
›
5. Reopen the Keychain Access utility, found in the Utilities folder in your Applications folder.
6. Click on the My Certificates category on the left.
6
Page ~ 27
Apple
STEP-BY-STEP
7. Click on an empty space in the window on the right to ensure that no existing keys or
certificates are selected. 7
table of contents
checklists
‹ previous
next
7
6
›
8. Choose Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority.
9. For User Email Address, specify a valid email address.
9
10.For Common Name, enter the name of your company or division. This certificate can
be reused for multiple apps that you might create, so you don’t need to enter the app
name here. 10
11.Leave the CA Email Address field blank.
11
Page ~ 28
Apple
STEP-BY-STEP
12.Select Saved To Disk.
12
table of contents
checklists
9
10
11
‹ previous
12
next
›
13.Click the Continue button.
14.Specify the name of the certificate signing request and where the file will be saved,
and click Save.
15.When the certificate request is created, click Done.
Generate a Distribution Certificate
Now that you’ve created the certificate signing request file, you need to submit it to the
Apple Developer site to create the required distribution certificate.
1. In the Apple Developer site, click Continue to advance to the “Generate your certificate” screen. Click Choose File, and double-click the certificate request file you just
saved in the previous steps. 1
Page ~ 29
Apple
STEP-BY-STEP
2. Click Generate.
2
table of contents
checklists
‹ previous
next
›
1
2
Your distribution certificate is added to the Apple Developer site.
3. Click Download, and then download the certificate to a known location.
This distribution certificate is called ios_distribution.cer. This file is required to create your p12 certificate.
Page ~ 30
Apple
STEP-BY-STEP
table of contents
Create a p12 Distribution Certificate
1. In the Finder, locate the ios_distribution.cer file you created, and double-click it.
2. Double-clicking the certificate launches Keychain Access and installs the certificate. To see if the
certificate was installed, click on the Keys category on the left, and then click the right-pointing
arrow to open the private key. You should see the certificate added to the private key. If double-clicking the .cer file does not install the certificate as shown below, then launch Keychain
Access, and choose File > Import Items to specify the .cer file.
checklists
‹ previous
next
›
3. Control-click or right-click the private key associated with your certificate, and choose Export
“[name].” Important: Control-click the private key (highlighted in red below), not the certificate.
Page ~ 31
Apple
STEP-BY-STEP
table of contents
4. Save your key in the Personal Information Exchange (.p12) file format. Specify a name that distinguishes it from the p12 file you created for the development certificate. Do not use any characters
other than a–z, 0–9, hyphens, underscores, and spaces in the filename.
checklists
‹ previous
next
›
5. When prompted, specify a password for your p12 certificate, and click OK.
Remember this password. Do not use a blank password. You will need this password later when
building your app in the DPS App Builder. (You can use the same password for the distribution and
development certificates.)
6. Specify the Administrator password for your computer, and click Allow.
You now have both of the p12 certificates that you need to create apps for the App Store. Store these files
in a safe place. You can now delete the certificate signing request file and the ios_distribution.cer file, as
they are no longer needed.
Page ~ 32
Apple
STEP-BY-STEP
table of contents
Test your certificates
checklists
IT IS A GOOD IDEA to test your certificates at this point, to ensure that they are valid.
1. Open the Keychain Access utility, found in the Utilities folder in your Applications folder.
2. Select the Keys category on the left.
‹ previous
2
3. Click the right-pointing arrow next to each private key to reveal the certificate within. The certificate name must begin with the words iPhone Developer or iPhone Distribution. If you don’t see these
words, you will need to recreate your certificates. 3
next
›
4. Click on each certificate, and view the contents of the pane above the certificate. The phrase “This
certificate is valid” must appear in this area when you select the Developer certificate and the Distribution certificate. If you don’t see this phrase, you will need to recreate your certificates. 4
4
3
2
Don’t worry that the certificates are called iPhone Developer and iPhone Distribution, even though you
are developing an app for the iPad or for both the iPad and iPhone. This is normal.
Page ~ 33
Apple
STEP-BY-STEP
table of contents
Create an App ID
checklists
YOU WILL NEED TO CREATE an App ID for your app. This is a unique identifier required by Apple to
identify an app. You will use Apple’s Developer site to create an App ID.
‹ previous
A different App ID is required for each app that you create.
1. On the Apple iOS Developer site, go to “Certificates, Identifiers & Profiles” at bit.ly/OVbhu5. Sign in
with your Apple ID.
2. Click Identifiers, and make sure that App IDs is selected.
next
›
2
3. Click the Plus icon in the upper right corner of the window to create an App ID.
3
3
2
Page ~ 34
Apple
STEP-BY-STEP
4. Type a description, such as the name of your app.
4
table of contents
checklists
‹ previous
next
›
4
Page ~ 35
Apple
STEP-BY-STEP
table of contents
5. For App Services, leave Game Center and In-App Purchase selected (Apple enables these by default),
and do not select iCloud or Passbook. Select Data Protection only if you enabled secure content in
your Enterprise account (see http://adobe.ly/1hiafVc). Select Push Notifications if you want to enable
push notifications in a multi-folio app. Selecting this option is required for Newsstand apps. 5
6. For App ID Prefix (previously called “Bundle Seed ID”), leave the option set at Generate New (if this
is the first App ID you’ve generated) or Use Team ID (for additional App IDs). In other words, don’t
do anything here unless you really know what you’re doing. 6
checklists
‹ previous
next
›
5
6
Page ~ 36
Apple
STEP-BY-STEP
table of contents
7. Specify a Bundle ID. The Bundle ID (or Bundle Identifier) is usually specified in a form called reverse
domain name or com.domainname.applicationname. In other words, if you work for Pluralist Design, your website is www.pluralistdesign.com, and your application is called “Pluralist Lookbook,”
your App ID would be com.pluralistdesign.pluralistlookbook. 7
checklists
‹ previous
next
›
7
8. Click the Continue button.
9. If the settings look correct, click the Submit button, and then click Done.
The App ID will appear in the list. This same App ID will appear in various screens in later steps in this
process. For example, when you build the mobileprovision files for your app, you’ll specify this App ID,
and the App ID settings will be included in the mobileprovision files.
Page ~ 37
Apple
STEP-BY-STEP
table of contents
Register your test iPads/iPhones with Apple
checklists
When you build your app with DPS App Builder, you will have an opportunity to preview
‹ previous
the actual app on one or more iPads and iPhones before submitting the app to the App
Store. This preview will include your app icon, app name, and the fully functional app. To
preview the app, you will need to provide Apple with a list of UDIDs (sort of like serial
next
numbers) of each iOS device on which you will want to preview your app.
›
Here is one way to discover the UDID of your iPad:
1. Attach your iPad or iPhone to your Macintosh with a USB cable.
2. Launch iTunes.
3. Select your device in the upper right area of iTunes.
adobe tip
If you have several UDIDs
to record, it might be easier
to use one of the many free
UDID apps available on the
App Store. Search the App
4. In the Summary section, locate the serial number of your iPad.
Store for “UDID” to locate
these. Typically, these apps
will extract the UDID from
your iPad and allow it to be
emailed in text form to the
address you specify.
Page ~ 38
Apple
STEP-BY-STEP
5. Click the serial number, and it will change to the UDID.
5
table of contents
checklists
‹ previous
5
next
6. Press Command+C to copy the UDID, and then paste the UDID into a text file or an InDesign file
for safekeeping. (You don’t select the UDID before copying—just press Command+C and the UDID
will be copied to the clipboard).
›
7. Repeat for each iPad, iPhone, or iPod that you will use to preview your app.
8. Go to the Apple iOS Developer site at bit.ly/OVbhu5. You will need to sign in with your Apple ID.
9. Click Devices on the left side of the window.
9
10.Click the Plus icon in the upper right corner of the window to add a device.
10
10
9
Page ~ 39
Apple
STEP-BY-STEP
11.Enter a name and a UDID for one of the devices on which you will want to test your app. This is the
information you gathered in step 6, above. To enter the information for another device, click the plus
icon. When you have entered a UDID for each device that you need, click the Continue button.
table of contents
checklists
‹ previous
next
›
Page ~ 40
Apple
STEP-BY-STEP
table of contents
You should now have a list of each device on which you will want to test your app displayed in the
Devices section of the Provisioning Portal.
checklists
‹ previous
next
›
Page ~ 41
Apple
STEP-BY-STEP
table of contents
Set up Apple push notifications (optional)
checklists
If you enable the Apple Push Notification Service (APN) for your viewer app using the Adobe service,
you can indicate to your customers when a new or updated folio is available, and you can send text
notifications.
In non-Newsstand apps, the app icon displays a red badge that indicates the number of new or updated
‹ previous
next
›
issues.
If you’re creating a subscription app for Newsstand, setting up push notifications is required. When the
publisher sends a push notification to indicate a new or updated folio, only subscribers to the app see a
red badge on the Newsstand icon that indicates the number of folios downloaded in the background. In
iOS 7, a blue dot appears below the app cover in Newsstand until the subscriber opens the app. For both
subscribers and non-subscribers, the cover image is updated to reflect the newest folio cover.
For more advanced push notification, you can set up a third-party push server if you have an Enterprise
account. For details, see adobe.ly/yV5gZI.
The Apple process for creating .p12 push certificates is similar to the process for creating developer and
distribution .p12 certificates.
Create a Development Push Certificate Signing Request
Apple provides a couple of different ways to start creating a push certificate. You can either create a certificate through the Certificates tab or by changing the settings of the App ID you created. Both options do
the same thing. We’ll go through the Certificates tab.
1. Go to the Apple iOS Developer site at bit.ly/OVbhu5. You will need to sign in with your Apple ID.
2. Click Certificates on the left side of the window.
2
3. Click the Plus icon in the upper right corner of the window to start creating a certificate.
4
Page ~ 42
Apple
STEP-BY-STEP
table of contents
4
checklists
3
‹ previous
next
›
4. In the “What type of certificate do you need?” section, select Apple Push Notification Service SSL
(Sandbox). Click Continue.
Page ~ 43
Apple
STEP-BY-STEP
5. Specify the App ID you created. Make sure that you select the appropriate App ID. Then click
Continue.
table of contents
checklists
‹ previous
next
›
As indicated on the Apple Developer site, you’ll now use the Keychain Access utility to create a
Certificate Signing Request (CSR).
6. Reopen the Keychain Access utility, found in the Utilities folder in your Applications folder.
7. Click the My Certificates category on the left.
7
Page ~ 44
Apple
STEP-BY-STEP
table of contents
8. Click on an empty space in the window on the right to ensure that no existing keys or certificates are
selected. 8
checklists
‹ previous
next
7
›
8
9. Choose Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority.
10.For User Email Address, specify a valid email address.
11.For Common Name, enter the name of your app.
12.Leave the CA Email Address field blank.
Page ~ 45
Apple
STEP-BY-STEP
table of contents
13.Select Saved To Disk.
checklists
‹ previous
next
›
14.Specify the name of the certificate signing request and where the file will be saved, and click Save.
15.When the certificate is created, click Done.
Generate a Development Push Certificate
Now that you’ve created the certificate signing request file, you need to submit it to the Apple Developer
site to create the required development certificate.
1. In the Apple Developer site, click Continue to advance to the “Generate your certificate” screen.
Click Choose File, and double-click the certificate request file you just saved in the previous steps.
1
Page ~ 46
Apple
STEP-BY-STEP
table of contents
2. Click Generate.
2
checklists
‹ previous
next
›
1
2
Your distribution certificate is added to the Apple Developer site.
Page ~ 47
Apple
STEP-BY-STEP
table of contents
3. Click Done. Click the certificate you just created to view its settings.
checklists
‹ previous
next
›
4. Click Download, and then download the certificate to a known location.
This APN development certificate is called “aps_developer.cer.” Next, you will create the .p12 certificate for this certificate that you can specify in DPS App Builder.
Create a p12 Development Push Certificate
1. In the Finder, locate the ios_developer.cer file you created, and double-click it.
2. Double-clicking the certificate launches Keychain Access and installs the certificate. To see if the certificate was installed, click on the Keys category on the left, and then click the right-pointing arrow
to open the private key. You should see the certificate added to the private key. If double-clicking
the .cer file does not install the certificate as shown below, then launch Keychain Access, and choose
File > Import Items to specify the .cer file.
3. Control-click or right-click the private key associated with your certificate, and choose Export
“[name].” Important: Control-click the private key (highlighted in red below), not the certificate.
Page ~ 48
Apple
STEP-BY-STEP
table of contents
4. Save your key in the Personal Information Exchange (.p12) file format. Specify a name that distinguishes it from the p12 file you created for the development certificate. Do not use any characters
other than a–z, 0–9, hyphens, underscores, and spaces in the filename.
checklists
‹ previous
next
›
5. When prompted, specify a password for your p12 certificate, and click OK.
Remember this password. Do not use a blank password. You will need this password later when
building your app in the DPS App Builder. (You can use the same password that you used for other
certificates.)
6. Specify the Administrator password for your computer, and click Allow.
7. Exit the Keychain Access utility.
You now have one of the two p12 push certificates that you need to create iOS apps with push notification enabled. Store this file in a safe place. You can now delete the certificate signing request file and the
ios_developer.cer file, as they are no longer needed.
Page ~ 49
Apple
STEP-BY-STEP
table of contents
Create a Production Push Certificate Signing Request
Now that you’ve created the Developer push certificate for the test app, the next step is to create the Pro-
checklists
duction push certificate for the distribution app using essentially the same process.
1. In the Apple iOS Developer site (bit.ly/OVbhu5), click Certificates on the left side of the window.
2. Click the Plus icon in the upper right corner of the window to start creating a certificate.
‹ previous
4
3. In the “What type of certificate do you need?” section, scroll down under Production and select
Apple Push Notification Service SSL (Production). Click Continue.
next
›
Page ~ 50
Apple
STEP-BY-STEP
table of contents
4. Specify the App ID you created. Be careful to select the right App ID. Then click Continue.
checklists
‹ previous
next
›
As indicated on the Apple Developer site, you’ll now use the Keychain Access utility to create a Certificate Signing Request (CSR).
Page ~ 51
Apple
STEP-BY-STEP
table of contents
5. Reopen the Keychain Access utility, found in the Utilities folder in your Applications folder.
6. Click the My Certificates category on the left.
6
7. Click on an empty space in the window on the right to ensure that no existing keys or certificates are
selected. 7
checklists
‹ previous
next
6
›
7
8. Choose Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority.
9. For User Email Address, specify a valid email address.
10.For Common Name, enter the name of your app.
11.Leave the CA Email Address field blank.
Page ~ 52
Apple
STEP-BY-STEP
table of contents
12.Select Saved To Disk.
checklists
‹ previous
next
›
13.Specify the name of the certificate signing request and where the file will be saved, and click Save.
14.When the certificate is created, click Done.
Generate a Production Push Certificate
Now that you’ve created the certificate signing request file, you need to submit it to the Apple Developer
site to create the required production certificate.
1. In the Apple Developer site, click Continue to advance to the “Generate your certificate” screen.
Click Choose File, and double-click the certificate request file you just saved in the previous steps.
1
Page ~ 53
Apple
STEP-BY-STEP
table of contents
2. Click Generate.
2
checklists
‹ previous
next
›
1
2
Your distribution certificate is added to the Apple Developer site.
Page ~ 54
Apple
STEP-BY-STEP
table of contents
3. Click Done. Click the certificate you just created to view its settings.
checklists
‹ previous
next
›
4. Click Download, and then download the certificate to a known location.
This APN production certificate is called “aps_production.cer.” Next, you will create the .p12 certificate for this certificate that you can specify in DPS App Builder.
Create a p12 Production Push Certificate
1. In the Finder, locate the ios_production.cer file you created, and double-click it.
2. Double-clicking the certificate launches Keychain Access and installs the certificate. To see if the certificate was installed, click on the Keys category on the left, and then click the right-pointing arrow
to open the private key. You should see the certificate added to the private key. If double-clicking
the .cer file does not install the certificate as shown below, then launch Keychain Access, and choose
File > Import Items to specify the .cer file.
3. Control-click or right-click the private key associated with your certificate, and choose Export
“[name].” Important: Control-click the private key (highlighted in red below), not the certificate.
Page ~ 55
Apple
STEP-BY-STEP
table of contents
4. Save your key in the Personal Information Exchange (.p12) file format. Specify a name that distinguishes it from the p12 file you created for the push development certificate. Do not use any characters other than a–z, 0–9, hyphens, underscores, and spaces in the filename.
checklists
‹ previous
next
›
5. When prompted, specify a password for your p12 certificate, and click OK.
Remember this password. Do not use a blank password. You will need this password later when
building your app in the DPS App Builder. (You can use the same password that you used for other
certificates.)
6. Specify the Administrator password for your computer, and click Allow.
You now have both of the p12 push certificates that you need to create iOS apps with push notification
enabled. Store these files in a safe place. You can now delete the certificate signing request file and the
ios_production.cer file, as they are no longer needed.
When you use DPS App Builder to build your app, you indicate whether push notifications is enabled
for that app, but you do not specify the push certificates and passwords. Instead, you use the Push Notifications Service. To do this, sign in to the DPS Dashboard (https://digitalpublishing.acrobat.com), click
Notifications, and then click the Certificates tab. You use the Push Notifications Service to schedule or send
push notifications, send text notifications, and replace expiring push certificates.
Page ~ 56
Apple
STEP-BY-STEP
table of contents
Create mobileprovision files
checklists
THE MOBILEPROVISION FILES determine which iPads or iPhones can install and use
your app. You will create two mobileprovision files: a development mobileprovision file
‹ previous
and a distribution mobileprovision file. The development mobileprovision file includes a
list of iPad IDs called UDIDs. The distribution mobileprovision file does not include any
UDIDs, because anyone who downloads your app from the App Store can use it. Unlike
next
›
the p12 certificates, which can be reused for multiple apps, the mobileprovision files must
be re­created for each new app you design.
The mobileprovision file is tied to the App ID. If you edit the App ID—for example, if you
enable push notifications—you must re-create the mobileprovision files to include these
changes.
Create a development mobileprovision file
1. In the Apple iOS Developer site (bit.ly/OVbhu5), click Provisioning Profiles on the
left side of the window. 1
2. Click the Development tab.
2
3. Click the Plus icon in the upper right corner of the window.
3
3
1
2
Page ~ 57
Apple
STEP-BY-STEP
4. Select iOS App Development, and click Continue.
table of contents
checklists
‹ previous
next
›
5. Specify the App ID, and click Continue.
Page ~ 58
Apple
STEP-BY-STEP
6. Select your iOS development certificate.
7. Specify the devices you want to provision. The development app you create for testing
in DPS App Builder will work only on devices included in the development mobileprovision profile.
table of contents
checklists
‹ previous
next
›
Page ~ 59
Apple
STEP-BY-STEP
8. Specify a name. Include “Development” in the name to distinguish it from the distribution file, but
don’t include any special characters (such as asterisks) in the name. You can rename these files after
generating them. Then click the Generate button.
table of contents
checklists
‹ previous
next
›
9. Click Download, and then download the development mobileprovision file to a known location.
You have now created the development mobileprovision file that the DPS App Builder needs to build the
development and distribution apps. Store this file in a safe place. Next, you will create the distribution
mobileprovision file.
Page ~ 60
Apple
STEP-BY-STEP
table of contents
Create a distribution mobileprovision file
To create a distribution mobileprovision file, you do not specify any UDIDs in the Devices section. You
checklists
simply create the mobileprovision file.
1. In the Apple iOS Developer site (bit.ly/OVbhu5), click Provisioning Profiles on the left side of the
window. 1
2. Click the Distribution tab.
2
3. Click the Plus icon in the upper right corner of the window.
‹ previous
next
3
›
3
1
2
Page ~ 61
Apple
STEP-BY-STEP
table of contents
4. Select App Store under Distribution, and click Continue.
checklists
‹ previous
next
›
Page ~ 62
Apple
STEP-BY-STEP
table of contents
5. Specify the App ID, and click Continue.
checklists
‹ previous
next
›
6. Select your iOS distribution certificate.
Page ~ 63
Apple
STEP-BY-STEP
table of contents
7. Specify a name. Include “Distribution” in the name to distinguish it from the development file, but
don’t include any special characters (such as asterisks) in the name. You can rename these files after
generating them. Then click the Generate button.
checklists
‹ previous
next
›
8. Click the Download button, and save the .mobileprovision file to your computer.
You have now created the two mobileprovision files that
the DPS App Builder needs to build the development and
distribution apps. Keep these files in a safe place.
Page ~ 64
table of contents
Create required assets
checklists
When you build your app and submit it to Apple, you will need to include a variety of keywords, descrip-
‹ previous
tive text, icons at various sizes, email addresses, copyright information, etc. It is best to gather all of these
items well in advance of your app submission date, since some of them may require input from others in
next
your company.
›
These assets—along with the .p12 certificates and mobileprovision files—are required when you use DPS
App Builder to build the app or as part of the app submission process in iTunes Connect.
You can read more about these items in the iTunes Connect Developer Guide, at bit.ly/RMGpiP.
Type the following items in a text file stored somewhere you’ll remember, so that you can copy and paste the
pieces out of the text file later when needed:
App Title
adobe tip
To test if your app title will
The title that will appear under the app icon on the iPad. Limit to 12 characters if you want it to be
display correctly on the iPad
completely visible. Depending on the characters (an “i” being narrower than a “w”), you may be able to
without abbreviation, open
fit 13 or 14 characters. You specify the App Title in DPS App Builder.
App Name
The title that will appear at the top of the screen in the black bar when a user taps the screen. Max-
Safari on the iPad. Visit any
web page, and tap the
imum of 35 characters. You specify the App Name in DPS App Builder, in the Apple developer site
button at the top of the screen.
(when you create the App ID), and in iTunes Connect (when you create the app record).
Tap “Add to Home Screen,”
Keywords for the App Store
The number of keywords is unlimited, but there is a total character limit of 100 characters. Enter keywords separated by commas, without a space after the comma. The comma characters count towards
the 100-character limit. You specify keywords in iTunes Connect.
Description for the App Store
This can be anywhere from 10–4,000 characters. You specify keywords in iTunes Connect.
and then enter the text you
want for your app title. If the
text appears correctly on your
home screen, it will display
correctly in your app.
Page ~ 65
Primary and Secondary categories for the App Store
table of contents
The secondary category is optional. Apple occasionally adds new categories. Go to the App Store on
your iPad, and tap “Categories” to see the categories you can choose from. You specify categories in
checklists
iTunes Connect.
Price Tier for Single-Folio Apps
‹ previous
This is how much you plan to charge for a single-folio app. The price can be free, or $.99, $1.99, $2.99,
$3.99, $4.99, etc. In other words, you cannot charge $3.42 for your app—it must be either $2.99 or
$3.99. You specify the price tier in iTunes Connect.
next
›
Copyright
This should be in the form “2013 Acme Inc.” Apple adds the copyright symbol automatically. You specify the Copyright in iTunes Connect.
Support Email
This is an email address of someone Apple can contact if there are problems with your app. This
adobe tip
­address is not seen by the public. You specify the contact email in iTunes Connect.
Johannes Henseler has
Support URL
The URL of a support website for users having questions about the app. This link will be visible on the
App Store. You specify the contact email in iTunes Connect.
Marketing URL (optional)
created a handy Photoshop
template that ­automatically
creates all the required
A website for users to get more information about the app. This link will be visible on the App Store.
sizes of application icons
You specify this URL in iTunes Connect.
from a single I­ llustrator or
SKU number
A unique alphanumeric identifier for this app. You specify the SKU number in iTunes Connect.
­Photoshop Smart Object.
Download the free template
at bit.ly/RMJL5a.
Page ~ 66
Store the following files with clearly labeled filenames in a separate folder:
table of contents
Application icons of various sizes:
For iPad apps, create 29x29, 50x50, 58x58, 72x72, 100x100, 144x144, 512x512, and 1024x1024 pixel
8-bit PNG files. If your app supports iPhones, also create 57x57, 114x114, and 120x120 pixel icons.
checklists
Specify the app icons in DPS App Builder. One way to produce these is to create a 1024x1024 pixel
PNG file, open it in Photoshop, and use Save for Web to create the smaller PNG files. Do not round the
corners of the icon; Apple rounds the corners automatically. Apple will apply an optional “shine” effect
to the icon if you specify this option in the DPS App Builder.
Screen shots for the App Store
‹ previous
next
›
Take a screen shot of the best screens from your app. To take a screen shot on the iPad, just navigate
to the screen you want to capture, and press the power and home buttons simultaneously. The screen
capture will be saved into the “Camera Roll” album of your Photos app. Save these images as 8-bit PNG
or JPEG files at 768x1024 or 1536x2048 pixel resolution (portrait) or 1024x768 or 2048x1536 pixel
resolution (landscape).
If your app supports the iPhone, take additional screen shots. To determine the required sizes of
screen shots for the iPhone, check iTunes Connect when you create the iTunes app record.
Splash screen images
When your app is first started on the device, a splash screen appears for approximately three seconds.
For the iPad, create four 8-bit PNG images: two landscape splash screens at 1024x768 and 2048x1536
pixels, and two portrait splash screens at 768x1024 and 1536x2048 pixels. For the iPhone, specify
320x480, 640x960, and 640x1136 PNG images. You specify these images in DPS App Builder.
For best results, make your splash image different from your cover. If the cover and the splash screen
are identical, users may think the app is frozen when they first start it. You might want to add a message such as “Loading . . .”
Use your web browser to search for
“writing an App Store description”
to locate dozens and dozens of sites
that will help you write a concise,
compelling App Store description.
Page ~ 67
table of contents
Additional images and information for subscription apps
Create optional subscription tile images for subscription apps. Create 708x250 and 1416x500-pixel background PNG
images that describe the Apple subscription when the iPad is upright. Create 964x184 and 1928x368-pixel background
PNG images that describe the Apple subscription when the iPad is in landscape orientation. The entire tile is active as
a button. Specify these images in DPS App Builder.
If your subscription app is enabled for Newsstand, specify a Newsstand cover (portrait only). In DPS App Builder,
you’ll need to specify 96x128 and 192x256 PNG files. In iTunes Connect, you’ll need to specify a larger PNG file, such
checklists
‹ previous
next
›
as 1024x768.
For iTunes subscription apps, you need to use iTunes Connect to create one or more in-app purchases that identify
subscription durations. You specify these Product IDs in DPS App Builder. See “Set up subscription apps” section on
page 80.
If your subscription includes direct entitlement, you need to obtain an Integrator ID from your Adobe representative. Additional subscription assets and website URLs are required. Learn more about these subscription requirements
in DPS App Builder or by reading this help topic: adobe.ly/xHwqbP. The DPS Developer Center (adobe.ly/y3YOEv)
also includes detailed articles about building subscription and entitlement apps.
Certificates and mobileprovision files
Use the same .p12 developer and distribution certificates for all your company apps. Create a set of mobileprovision
files and .p12 push certificates (if push is enabled) for each separate app. See the previous sections in this document
for details.
Product IDs for retail folios
When you publish a folio, each folio requires its own Product ID. If the folio is retail, you need to use iTunes Connect
to create an in-app purchase Product ID and specify that Product ID when you publish the folio. Doing so ties the
folio to a store purchase. Free folios do not require in-app purchases to be created. See “Create In-App Purchases for
retail folios” section on page 76.
Page ~ 68
Apple
STEP-BY-STEP
table of contents
Create an iTunes Connect record for the app
BEFORE YOU CAN SUBMIT YOUR APP TO APPLE FOR DISTRIBUTION, you create a record of
your app in iTunes Connect. This record includes the information that appears on the store for the app,
checklists
‹ previous
the app languages you want, and the information required to manage the app. Once you set up the iTunes
Connect record for the app, you can create in-app purchases and submit the distribution app.
The iTunes Connect Developer Guide at bit.ly/N9fBUV explains how to submit files for approval.
next
›
However, the Developer Guide is written primarily for developers, so it can be somewhat intimidating.
We created this guide to provide specific information about submitting apps created with Adobe Digital
Publishing Suite.
Apple revises the iTunes Connect interface on occasion. The steps in this guide might be out of date on
occasion.
1. Go to itunesconnect.apple.com.
2. Sign in with your Apple ID (not your Adobe ID).
3. Click My Apps.
Page ~ 69
Apple
STEP-BY-STEP
table of contents
4. Click the plus icon and choose New iOS App.
checklists
‹ previous
next
›
In the screens that follow, you will be prompted to fill in details about your app and various icons
and assets. You should have already gathered up all these items, as listed in the “Create required
assets” section on page 65.
App Name: Enter the full name of your app. This is the “long name” that may be up to 35 characters in length.
Primary Language: Choose the language that you will be using to enter your app details for display
in the App Store.
Bundle ID: Choose the App ID you created earlier from the list.
Version: Enter a version for this app. Apple wants you to use the same version number here that
you use in DPS App Builder, but it isn’t required.
Page ~ 70
Apple
STEP-BY-STEP
table of contents
SKU Number: Enter a unique alphanumeric identifier for this app.
checklists
‹ previous
next
›
5. Click Create.
6. Under Versions, specify the information as follows:
App Preview Video and Screenshots: Click each device type and specify the screenshots that will
appear in the App Store. Include one to five 768x1024- or 1536x2048-pixel (portrait) or 1024x768or 2048x1536-pixel (landscape) screenshots of your app. Include one to five screen shots in the
Page ~ 71
Apple
STEP-BY-STEP
table of contents
required sizes if your app supports iPhone. For details, click the Info button next to this option, and
then Command-click the Learn More link to open the help document in a different tab.
checklists
‹ previous
next
›
Name: Enter the name of the app as it will appear in the App Store.
Description: Enter the description for the App Store. If your app includes auto-renewable or free
subscriptions, provide this information, and include a link to your privacy policy URL.
Keywords: Enter the keywords for the App Store, separated by commas.
Support URL: Enter the URL of a web page that offers information and support for this app.
Marketing URL: Enter the URL of a web page that offers marketing information for this app. This
URL will be visible in the App Store.
Privacy Policy URL: Enter the URL that links to your organization’s privacy policy. Privacy policies
are required for apps that are Made for Kids, offer auto-renewable in-app purchase or free subscrip-
Page ~ 72
Apple
STEP-BY-STEP
table of contents
tions, or as otherwise required by law. Privacy policies are also recommended for apps that collect
user data.
checklists
‹ previous
next
›
App Icon: Choose a 1024x1024-pixel 8-bit PNG image.
Version: Enter using a format such as 1.0, unless this is a revision to an existing app.
Primary Category: Choose the category you want the app to be displayed in on the App Store.
Secondary Category: If desired, choose a secondary category.
Rating: Click Edit, select rating information, and click Done.
Copyright: Enter the copyright information in the form of “2013 Acme Inc.” Apple adds the © symbol automatically when the app is published on the App Store.
Routing App Coverage File: This option is not required. To learn more, see Apple documentation.
Build: Shortly after you use Application Loader to submit the distribution .zip file, a plus sign
should appear in the Build section. This is usually the final step in submitting the app. For more
information, see the section about submitting apps later in this document.
Newsstand: If you are creating a subscription app, click the icon to enable Newsstand, and specify
the requested information, including cover art and Newsstand categories.
Contact Information: Enter the name, phone number, and email address of a person that Apple can
contact if there are problems with the app.
Page ~ 73
Apple
STEP-BY-STEP
table of contents
Demo Account: Enter the User Name and Password of a testing account so that Apple can verify
in-app purchases or direct entitlement. Specify additional accounts in the Notes field.
checklists
Notes: Specify additional information for your app to help the Apple representative during the
review process.
‹ previous
Version Release: Indicate whether you want the app to be made available on approval or if you
want to delay the release until you’re ready.
next
›
7. Click Save to save the version information. If required information or assets are missing, Apple will
display error messages. Resolve these issues and click Save again.
8. If your app is single-folio, fill in the pricing screen as follows:
adobe tip
One reason to limit the availability of your app to certain
countries is because Apple
only collects sales tax in some
countries. If you want Apple
to take care of all the sales tax
hassle, limit your app to sell
Availability Date: Leave this date as is, unless you wish to enter a future date to delay the release of
your app until after a particular date.
only in the countries in which
Apple collects sales tax.
Price Tier: Select Free or whichever price tier that you desire. Click on View Pricing Matrix to see
more pricing details.
Discount For Educational Institutions: Select this option if you want to offer a discount to educational institutions.
Page ~ 74
Apple
STEP-BY-STEP
table of contents
Custom B2B App: Do not select this. Custom business-to-business apps cannot be created with
Adobe Digital Publishing Suite, Single Edition. If you want to create a custom business-to-business app, purchase an Enterprise license to Adobe Digital Publishing Suite.
Specific Stores: Select this option if you want to limit the app to be available only in certain
countries.
checklists
‹ previous
9. Click Save.
10.If your app includes in-app purchases for folios or subscriptions, click the In-App Purchases
tab and specify the appropriate information. For details, see “Create In-App Purchases for retail
folios” section on page 76 and “Set up subscription apps” section on page 80.
next
›
Page ~ 75
Apple
STEP-BY-STEP
table of contents
Create In-App Purchases for retail folios
IF YOU WANT TO SELL FOLIOS IN YOUR APP, you need to use iTunes Connect to create an inapp purchase for each retail folio. You also need to submit each In-App Purchase to Apple for approval.
checklists
‹ previous
(Apple does not require free folios to be approved.) For each retail folio, it’s important to specify the same
Product ID when publishing the folio and when setting up the In-App Purchase. Doing so links the InApp Purchase to a specific folio. Create In-App Purchases only for retail folios, not free folios.
next
›
If you’re creating a retail subscription app, you need to create In-App Purchase subscription durations in
addition to In-App Purchases for retail folios. This process is described later in this guide.
Note: Apple reviews the contents of the In-App Purchase issue at its sole discretion. Many publishers
submit multiple In-App Purchases without publishing the corresponding folio, and Apple has approved.
In rare cases, Apple might require you to publish your folio before approval. A published retail folio does
not appear in your public app library until the In-App Purchase is approved and cleared for sale.
1. Go to iTunes Connect (http://itunesconnect.apple.com) and sign in.
2. On the iTunes Connect main page, click My Apps.
Page ~ 76
Apple
STEP-BY-STEP
table of contents
3. If you have already created the app record in iTunes Connect, click it. If you have not yet created the
app record, see “Create an iTunes Connect record for the app” section on page 69, and then return
to this section.
4. Click In-App Purchases.
If the Manage In-App Purchases option does not appear, you have not signed up for a retail account
by adding your bank info and tax info.
5. Click Create New to create a new in-app purchase.
checklists
‹ previous
next
›
6. Click the “Non-Consumable” Select button.
7. Specify the pricing and language of your issue.
•
Under Details, specify a Reference Name and Product ID. This Product ID must be identical to
the Product ID you use when publishing the folio. Use the “com.publisher.publication.folio” format, such as “com.sportsmag.kayaking.2013january.” For best results, use all lowercase letters—
avoid extended characters.
•
Add a language.
•
Under Pricing and Availability, select “Cleared for Sale” so that you can test the app. Choose the
price for your issue.
Page ~ 77
Apple
STEP-BY-STEP
table of contents
•
Under Screenshot For Review, specify an image when ready to submit your in-app purchase.
Apple will not review the in-app purchase until you include the screenshot.
checklists
‹ previous
next
›
8. Click Save.
If you did not specify a screen shot, your status is set to Waiting For Screenshot. If you specify the
screen shot, you can select the in-app purchase and submit it for review.
Page ~ 78
Apple
STEP-BY-STEP
table of contents
9. In the Folio Producer Organizer (https://digitalpublishing.acrobat.com), publish the folio as Public
and Retail using the same Product ID you used when creating the in-app purchase.
checklists
If your viewer app is already approved, the retail folio does not show up in the viewer library until Apple
approves the In-App Purchase. Retail folios do not appear in the Adobe Content Viewer—only in custom
viewers.
If your viewer app has not been approved, your first In-App Purchases must be submitted with a new
app version. Select them from the In-App Purchases section of the Version Details page in iTunes Connect,
‹ previous
next
›
and then click Ready to Upload Binary.
You can submit multiple in-app purchases to Apple for approval. Getting in-app purchases approved in
advance helps avoid delays in publishing your folio.
Understanding In-App Purchases and Product IDs
In-App Purchase
There are two types of In-App Purchases. One type of In-App Purchase is used to set a price for an
individual retail folio. The other type is used to set prices for different subscription durations. For
both types of In-App Purchases, you create Product IDs. For retail folios, you specify the Product ID
when you publish the folio. For subscription durations, you specify the Product IDs when you
use DPS App Builder to build the app.
Product ID
Apple uses Product IDs to assign products to retail content. For DPS, a product can be the app itself
(for a single-folio app), an individual folio, or a subscription duration.
The Product ID for each item—retail folio or subscription duration—must be unique,
such as “com.publisher.folkmusic.september2013.” Use the same Product ID
for a set of folio renditions (1024x768 and 1136x640), but use a different Product ID for
each different folio or set of renditions (such as the September and October issues).
Page ~ 79
Apple
STEP-BY-STEP
table of contents
Set up subscription apps
IF YOU SET UP A SUBSCRIPTION APP, you give users access to folios in your custom viewer for a
specified period of time. If you create a subscription app with retail (paid) content, you must set up In-
checklists
‹ previous
App Purchases for each retail folio, and you must set up an In-App Purchase for the different subscription
duration options (3 month, 6 month, 1 year, and so forth). Subscription apps can appear in Newsstand.
For each in-app purchase, you specify a Product ID. For example, a Product ID for an individual folio
next
›
should be in the “com.publisher.publication.monthyear” format. A Product ID for the subscription duration should be in the “com.publisher.publication.duration” format. For retail folios, you use that same
Product ID when you publish the folio using the Folio Producer Organizer. For subscription durations,
you specify the Product IDs when stepping through the DPS App Builder panels.
Additional information about subscriptions:
•
You can set up a free subscription for Newsstand apps. Do not use this option if you want to sell
content for your app at any time.
•
Your customers have the choice of purchasing your individual folios or purchasing a subscription.
If they purchase a subscription, they’re entitled to any folio published between the start date and
end date of their subscription. When customers first subscribe, they’re entitled to the most recently
published folio—free or retail—even if the folio was published before their start date.
•
If you publish a retail folio as public, it does not appear in the viewer library until Apple approves
the in-app purchase and makes it available. However, the Distribution Service does not look to see
whether the published folio is actually available. This creates a situation in which your customers
can purchase a subscription and not be entitled to any new content until the pending folio becomes
available.
•
The Publication Date setting in the Folio Producer Organizer determines which folios subscribers
are entitled to. For best results, edit the Publication Date settings of folios using a consistent date,
such as the first day of each month.
Generate or view a shared secret
Use the In App Purchase process on iTunes Connect to set up Apple subscriptions. When you create a
subscription, you generate or view a shared secret, which is a unique code that lets the app communicate
with in-app purchase receipts.
Page ~ 80
Apple
STEP-BY-STEP
table of contents
1. Go to http://itunesconnect.apple.com, and sign in.
2. If you have not already done so, click “Contracts, Tax, and Banking” and specify the necessary
information.
3. Click My Apps.
4. In the My Apps page, click the application in which you want to set up subscriptions
5. Click In-App Purchases.
checklists
‹ previous
next
›
6. Click “View or Generate a Shared Secret.” (If the shared secret appears, do NOT generate a new
one. Use the same shared secret for all your apps.)
7. If a Shared Secret section does not appear on the In-App Purchases page, it means you have not
filled out the necessary banking information or you have not accepted the terms of agreement.
Click Go Back, and then click the “Contracts, Tax, and Banking” option.
Page ~ 81
Apple
STEP-BY-STEP
table of contents
8. Copy your shared secret code. Use the Account Administration tool on the DPS Dashboard to edit
the Application account and specify your shared secret. After you specify the shared secret informa-
checklists
tion, open the Folio Producer Organizer to trigger the shared secret registration.
‹ previous
next
›
Again, once you generate a shared secret, do not re-generate it. Use the same shared secret code for all
your apps.
Create an In-App Purchase for a retail subscription
Apple calls a retail subscription an “Auto-Renewable Subscription.” If you’re creating a free subscription
for Newsstand, skip to the next section.
1. Go to iTunes Connect > My Apps, snd click your app.
2. Click In-App Purchases.
3. Click Create New.
Page ~ 82
Apple
STEP-BY-STEP
table of contents
4. In the Create New In App Purchase page, select “Auto-Renewable Subscriptions.”
5. Follow the prompts to fill out the rest of the subscription information.
You can create multiple durations. For each duration, specify a Product ID. We recommend that you
use the “com.publisher.publication.duration” format, such as “com.sportspub.kayaker.1year.” When
you use DPS App Builder to create your subscription app, you specify the subscription Product IDs
in the Subscription Details panel. Each duration you specify appears in the dialog box when your
users tap the Subscribe button or the subscription tile image.
checklists
‹ previous
next
›
Apple lets you create multiple subscription families. However, for viewer apps, create only one family
with multiple durations.
Page ~ 83
Apple
STEP-BY-STEP
table of contents
6. Use the Adobe Folio Producer Organizer to publish retail folios for your subscription application.
For best results, use a consistent Publication Date for your folios, such as the first of every month.
checklists
The Publication Date determines whether a folio is part of a subscription duration.s
If you have not already done so, use the in-app purchase method in iTunes Connect to assign a price
and Product ID to each folio. Customers can then pay for individual folios or pay for a subscription
that entitles them to a range of folios.
‹ previous
next
›
Create an In-App Purchase for a free subscription app
Use the In App Purchase process on iTunes Connect to set up a free subscription for Newsstand apps.
Note that you cannot add retail content to a free subscription app. Do not set up a free subscription app
if you plan to add retail content later—anyone who subscribes to a free subscription will continue to get
content free, even if you update the app from free subscription to retail subscription.
When you create a subscription, you generate a shared secret, which is a unique code that lets the app
communicate with in-app purchase receipts. Specify this shared secret using the Account Administration tool, and then open the Folio Producer Organizer to register the shared secret. You can use the same
shared secret for multiple apps.
In a free subscription app, you create only one In-App Purchase for the subscription. You do not create
In-App Purchases for your individual folios. Only retail folios require In-App Purchases to be set up.
1. Go to iTunes Connect > Manage Your Apps, snd click your app.
2. In the Manage Your Apps page, click the application for which you want to set up a free subscription.
3. Click Manage In-App Purchases.
4. If you have not already done so, copy and paste your shared secret code, as described earlier.
5. Click Create New.
6. In the Create New In App Purchase page, select “Free Subscription.”
7. Follow the prompts to fill out the rest of the subscription information.
For Product ID. We recommend that you use the “com.publisher.publication.free” format, such as
“com.sportspub.kayaker.free.” When you use DPS App Builder to create your subscription app, you
specify the Product ID in the Subscription Details panel.
Page ~ 84
Apple
STEP-BY-STEP
table of contents
Enable Newsstand in iTunes Connect
Apple requires you to use iTunes Connect to enable an app for Newsstand. Do this before you submit
checklists
your distribution viewer app to Apple.
Apple requires issues in Newsstand apps to be published at least quarterly. For example, if you state that
you will publish a new issue twice a year, Apple is likely to reject the app.
1. Go to iTunes Connect > Manage Your Apps, snd click your app.
2. Click Newsstand.
‹ previous
next
›
3. Enable Newsstand, and specify a cover image, such as a 1024x768 PNG file, and follow the prompts.
Note that the image you specify in iTunes Connect is not used in your app itself. The Newsstand image
you specify in DPS App Builder is used for the initial Newsstand image. Whenever you publish a new
folio, the portrait cover image replaces the initial Newsstand image.
However, the image you specify in the Newsstand section appears in the Apple App Store and the
iTunes Store. Whenever you publish a new folio, you can upload a new image in the Newsstand section of
iTunes Connect to update your app’s appearance in the App Store and in iTunes.
Set up a third-party entitlement server (Enterprise only)
If you’re an Enterprise subscriber to DPS, you can create a viewer app that uses a custom entitlement
server to determine which customers can download content. Customers can subscribe either through
your subscription service or through the Apple App Store. When you set up a custom entitlement server,
you can create an entitlement banner that appears at the top of the library.
Setting up a custom entitlement server is beyond the scope of this guide. Contact your Adobe representative for entitlement server requirements, API specifications, custom storefronts, custom libraries, and
related information. The Digital Publishing Suite Develeoper Center at adobe.ly/y3YOEv provides detailed
documentation for Enterprise app creation.
Page ~ 85
table of contents
Build the app with DPS App Builder
AFTER YOU CREATE the necessary files and certificates and build your folios using Adobe InDesign
and the DPS Folio Producer, you’re ready to create your app using the DPS App Builder.
1. Make sure that you are using the most updated version of DPS App Builder.
Choose Help > Updates, and install the DPS Desktop Tools if an update is available.
checklists
‹ previous
next
›
2. Launch DPS App Builder, and sign in with an Adobe ID that has a DPS App Builder role assigned to
it. Use the Account Administration tool to assign roles to Adobe IDs.
3. Follow the prompts to build your iOS app. Click the Info button next to any option to view a description. For more details about creating an iOS viewer app, see the help article at adobe.ly/xHwqbP.
Page ~ 86
table of contents
Test the development app
THE NEXT STEP is to test the development app to make sure that everything works as designed. In order
to complete the steps below, the iPad on which you wish to test the development app must be one that you
regularly sync with iTunes on your computer.
checklists
‹ previous
next
›
Test an app with free content
1. Open iTunes, and drag the developer-viewer.ipa file into your iTunes Library.
2. Connect your iPad, and sync the device.
3. The app should appear on your iPad. Test the app to ensure that it works as desired.
4. Do one of the following:
•
If the app needs to be changed, edit the folio, and then use the DPS App Builder to edit and create another development app. Delete the previous app from iTunes and from your iPad, install
the new app, and test again.
•
If the app works as designed, continue on in this guide to submit the distribution app to the App
Store.
Page ~ 87
table of contents
Test an app with retail content
While testing the app, you can create a test user that lets you download the folio using the development
checklists
app without actually paying for the issue. This sandbox testing process is explained in more detail in the
“Managing Your In App Purchases” section of the iTunes Connect Developer Guide.
1. In the Folio Producer Organizer, publish folios with statuses set to Retail and Public and the appropriate Product ID.
This product ID must be identical to the product ID you specify when submitting the In App Purchase. We recommend that you use the “com.yourcompany.yourmagazine.yourissue” format for your
Product ID—the App ID name followed by the issue name.
‹ previous
next
›
2. Using iTunes Connect, create a test user.
A test user lets you test the process of purchasing an issue without actually having to purchase the
issue. To create a test user, go to the main page of iTunes Connect, and click Users and Roles. Click
Sandbox Tester. Click the plus sign, and then specify information. Use a valid email address that you
can use to verify. Remember the email address and password. You’ll need this information to “purchase” your issue in the sandbox environment.
3. On your iPad, sign out of your account. Tap Settings, tap Store, tap your Apple ID, and tap Sign Out.
Sign out to make sure that you don’t actually use your real account to purchase the issue.
Page ~ 88
table of contents
Do not sign in using your test user—remain signed out. Otherwise, your test user will treated like a
normal user, and you’ll be prompted for your credit card information.
checklists
4. Open iTunes, and drag the developer-viewer.ipa file into your iTunes Library..
5. Connect your iPad, and sync the device.
‹ previous
The app should appear on your iPad.
6. When notifiied of a new issue, follow the prompts, and sign in using your test user account information. “Purchase” and download the folio or subscription.
next
›
If you’re prompted for credit card information, exit the viewer app, and sign out of your account.
Start the viewer again, do not sign in, and then download the issue using the test account.
7. Do one of the following:
•
If the app needs to be changed, edit the folio, and then use the DPS App Builder to edit and create another development app. Delete the previous app from iTunes and from your iPad, install
the new app, and test again.
•
If the app works as designed, continue on in this guide to submit the distribution app to the App
Store.
Page ~ 89
Download the distribution app
table of contents
When you have determined that your development app works like you want it to on your iPad, it is time
to download the Distribution app in DPS App Builder. This is the .zip file that you will upload to Apple.
1. If you still have DPS App Builder running, skip to step 3. If DPS App Builder is not running on your
computer, find DPS App Builder in your Applications folder, and double-click it.
2. Sign in with your Adobe ID and password.
3. Open Manage View.
checklists
‹ previous
next
›
4. Click Distribution App in the Downloads column.
5. Select your distribution p12 certificate, and then enter your distribution p12 password.
The distribution mobileprovision file information will be entered automatically for you.
6. Click Sign And Download.
5
6
5
6
7. Click OK. A distribution-viewer.zip file is downloaded to your desktop. This is the file that you will
submit to Apple, as described in the next section.
Page ~ 90
Apple
STEP-BY-STEP
table of contents
Submit your app to the App Store
NOW THAT YOUR APP IS BUILT and tested, the final step is to submit the app to the App Store. To do
this, you will use the iTunes Connect Web portal to enter various details about your app, and then upload
checklists
‹ previous
the Distribution app to Apple for approval.
The iTunes Connect Developer Guide at bit.ly/N9fBUV explains how to submit files for approval.
However, the Developer Guide is written primarily for developers, so it can be somewhat intimidating.
next
›
We created this guide to provide specific information about submitting apps created with Adobe Digital
Publishing Suite.
1. Go to itunesconnect.apple.com. Sign in with your Apple ID (not your Adobe ID).
2. Make sure that you have used iTunes Connect to create a record of your app. If you are submitting a
new version of the app, make sure that you create a new version.
3. If you have not already downloaded the Application Loader app, click the link to Application Loader
in the Build section. (If you downloaded Xcode, Application Loader was also downloaded. However,
make sure that you have the most recent version of Application Loader installed.)
4. Start Application Loader. Click Deliver Your App, and follow the prompts to upload the Distribution
app (.zip file) that was created by the DPS App Builder.
5. In iTunes Connect, click on My Apps, and click your app.
6. Scroll down to the Build section, and click the plus icon. Note that it might take a few minutes for
the binary file submitted with Application Loader to register with iTunes Connect.
Page ~ 91
Apple
STEP-BY-STEP
7. Specify the application you submitted.
table of contents
checklists
8. Click Save.
9. Answer the encryption questions. By default, Adobe DPS App Builder does not encrypt apps, so you
can answer “No” to the questions unless you enabled secure content in your app.
‹ previous
next
›
10.Click Submit for Review.
If you enabled secure content in your app, indicate that your app includes encryption and follow the
Apple guidelines. For details, see http://adobe.ly/1hiafVc.
Once you successfully upload your app to Apple, the status of the app in iTunes Connect should change
to “Waiting for Review.”
If you are using an older version of Application Loader, you might get an error message such as “the
dwarfdump binary must exist” or “com.apple.transporter.util.StreamUtil” when you upload the .zip file.
You can solve this problem by downloading and installing the most recent version of Application Loader.
Apple requires Mac OS X 10.7 or later to use Application Loader.
Page ~ 92
table of contents
Wait for approval from Apple
Apple will notify you via email when your app is accepted or rejected. You can use iTunes
Connect to track the status. For details, see the Apple Developer Guide.
If you notice an error in your app after you have submitted it, but before it is approved, you
can submit a new binary while your app is still pending. Go the My Apps section of iTunes
checklists
‹ previous
next
›
Connect, select the app, and then click Reject Binary. Then submit a new version of the .zip file
in Application Loader, wait a few minutes, and select that file in the Build section of the app
details in iTunes Connect.
Update an app
You may want to revise or update a Digital Publishing Suite app that you previously submitted to
the App Store.
Digital Publishing Suite Professional Edition and Enterprise Edition customers can revise
their apps (and submit their rebuilt apps to Apple) for as long as they are Digital Publishing
Suite subscribers.
When you revise your app, you can either create a new version of the app in DPS App Builder or edit an existing version. In either case, use a mobileprovision file based on the same App
ID. In DPS App Builder, select the existing app you created, and click Edit. Note that if you
change the type of app, such as converting a multi-folio app to a subscription app, you need
to build a new app from scratch in DPS App Builder. Again, as long as you use mobileprovision files based on the same App ID as the previous version, Apple will recognize the app you
submit as a version update.
Download and test the development file.
In iTunes Connect, click My Apps, click the app you want to update, and then click Add Version. Use Application Loader to upload the .zip file, and then submit the version in iTunes Connect.
For details about updating an app, see this article: http://adobe.ly/Zbirxo
Page ~ 93
table of contents
iOS publishing troubleshooting
Blank password not accepted
When prompted for a password while creating your p12 certificates, do not use a blank password. Type a
real password.
checklists
‹ previous
next
›
Version number mismatch
After you submit your app, you might get a warning that the version numbers do not match. Apple is letting you know that the version number you specified in iTunes Connect does not match the auto-generated version number in your app. You can ignore this warning. Apple will not reject the app for this reason.
“Invalid certificate” or “Invalid ZIP format”
If you upload an .ipa file to Apple from a computer running Snow Leopard 10.5 and the certificates have
been created on a computer running 10.6, one of these messages may appear. For best results, upload the
.ipa file from the same OS X 10.6 computer on which the certificates were created.
Error: Identity of iPhone developer doesn’t match any identity in any profile
This error occurs when files are generated under different profile names. For best results, make sure that
the same person uses the same profile to create the certificates on the same computer.
“the dwarfdump binary must exist” or “com.apple.transporter.util.StreamUtil” error when you
upload the .zip file
This error can occur when you are using an older version of the Application Loader. You can solve this
problem by downloading and installing the most recent version of the Application Loader.
The “Subscribe” button does not work in development app
Make sure that you have specified the shared secret information using the Account Administration tool.
Also make sure that you have specified the correct In-App Purchase Product ID information in DPS App
Builder.
Page ~ 94
table of contents
Cannot load the developer viewer on your iPad or iPhone
Make sure that you included the device’s UDID in the developer mobileprovision file. Only provisioned
checklists
iPads or iPhones can view developer viewer content.
Folios not showing up in multi-issue viewer
If your free folio is not showing up in your developer viewer or if it has a gray screen, do the following:
•
Make sure that you created the folio using the same Adobe ID you specified in the Title ID field of
‹ previous
next
›
DPS App Builder.
•
Make sure that the published folio statuses are set to “Free” and “Public.”
If your paid issue is not showing up in your developer viewer, do the following:
•
Make sure the Product ID you used to publish the folio in the Folio Producer tool matches the
Product ID of the In App Purchase created in iTunes Connect.
•
Make sure the published folio statuses of the paid issue are set to “Retail” and “Public.”
•
In the In-App Purchase section of iTunes Connect, make sure that you’ve selected “Cleared for Sale”
so you can test the app.
•
Make sure that all your tax and banking information has been entered and approved by Apple. No
in-app purchases will show up if it hasn’t, and there is no warning message indicating that this needs
to be done.
•
For subscription viewer apps, make sure that you specify the shared secret information using the
Account Administrator tool and then you sign in to the Folio Builder Organizer afterwards to register the shared secret.
Certificates expired or set to expire
If your development and distribution .p12 certificates expire, users can continue to use your app. However, you must edit or revoke and rebuild your certificates before you update your app. When you revoke a
certificate, follow the same steps described in this guide to create a new certificate.
An expired push production certificate can affect only push itself, not the ability to use the app. When
you sign in to the DPS Push Notifications Service, you’ll be notified if your push certificate is expired or is
set to expire within 30 days. Use the Apple Developer site to build new push certificate files, and then use
the Push Notifications Service on the DPS Dashboard to specify the new .p12.
Page ~ 95
table of contents
Certificate is invalid due to missing private keys
Certificates might be invalid because the corresponding private key is not in your keychain. Try to restore
checklists
your missing private keys from a developer profile backup, as described in “Exporting and Importing
Certificates and Provisioning Profiles.” If you cannot retrieve your private keys from another Mac, refer
to “Re-Creating Certificates and Updating Related Provisioning Profiles” to re-create all your certificates.
‹ previous
You can perform these steps for one or more invalid certificates.
Your certificates have expired
You cannot renew expired certificates. Remove (revoke) and create new ones.
If your Developer ID certificates expire, users can still download and run apps that were signed with
these certificates. However, you will need new certificates to update and create new apps.
You’re Missing Signing Certificates
Your signing certificates may be missing from your keychain because you never requested them or because you moved to a Mac on which you haven’t developed apps before.
If you never requested your certificates (there are none in your keychain). Follow the steps to create
certificates as described in this guide.
If you moved to a new Mac, export your certificates as a developer profile file on the Mac you first
requested the certificates from, and then import them on your new Mac. See “Exporting and Importing
Certificates and Provisioning Profiles” in the Apple App Distribution Guide.
If you no longer have access to the other Mac or user account and you did not keep a backup of your
certificates, see “Re-Creating Certificates and Updating Related Provisioning Profiles” in the Apple App
Distribution Guide.
Here is a link to the Apple App Distribution Guide: http://bit.ly/Yjgzbx.
Page ~ 96
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement