iOS App Submission Guide

Go down

iOS App Submission Guide Empty iOS App Submission Guide

Post  ndmeador on Wed Feb 22, 2012 3:24 pm

The following is a guide for iPhone and iPad (iOS) app submission. The main difference is the sizes of icons and splash images. This guide was last updated on 2/2/12.

1) Check the “Approved by Wendi” column on the “Submission” page of the shared Google Doc: . Wendi will approve apps with the word “yes” once the app maker puts “DONE” and “READY” on the “Apps to Make” page. Choose an approve app to submit.

2) Locate that app on the “Apps to Make” Google Doc. Make sure the “Price Original” and “App Price” columns are filled in. If not, consult Wendi. It’s helpful to know this information at the start, so that you can emphasize the mobile version discount in the app description (below).

3) Find the title of the app you want to submit on the My Applications page of Seattle Clouds: (login -- U: wendi; P: user1qaz) -- It’ll likely have the app maker’s initials, the program name, and the format (IPHONE, IPAD, or DROID – but the iPhone version might not have the format listed).

4) Click Properties to view a screen with the app’s icons and splash images (Safari seems to work better for uploading these images). These should have been uploaded by the app maker.

You’ll have to put in the description and keywords for most apps, unless the app maker does it. If they are already in, just scan them to make sure they look okay, have the necessary information, etc.

To get the description, do a Google search for “” and the app name. This will lead you to the program page on Wendi’s website. Copy and paste the text as neatly as possible.

To get keywords, use Google Keyword Tool with some relevant text (usually a piece of the description), the URL of the page at, and a category (usually “health” or something similar):

Always include keywords like “, wendi friesen, hypnotism, hypnosis,” and then others (up to 100 characters).

Click the green “Save” button. Click “Done” in the lower right corner.

5) This should take you to the Dashboard for that app. But since Firefox seems to work better for this part, you’ll want to copy your current URL and paste it into Safari. Click “Ready to Publish,” then “Start submission process.” What follows would ideally be self-explanatory, but it’s actually quite confusing and it requires some concentration.

6) Set “AppStore App Name (long name)” according to what it says in that column on the Submissions page of the Google doc. Ex: Sugar Blaster - Eliminate Sugar Cravings with Wendi. Click “Next” in the lower right corner.

7) Make sure that all the icons and splash images are still loaded correctly. Click Next.

8 ) Enter the correct build version (first time apps are “1.0”).

For the “Application Name” enter what’s in the “App short name” column on the Submissions page of the Google doc. This must be no longer than 13 characters. Ex: SugarBlaster. Check the preview under the icon to make sure it fits.

Leave all the checkboxes clicked. Click “Next.”

9) Review the “Last build date” page. Click “Next.”

10) Leave clicked “I have an Apple developer account…” – This should have saved our Apple Developer login (DO NOT SHARE LOGIN). Click “Next.”

11) Click “I want Push Notifications Enabled.” In the box that appears, click the “Create an APN Certificate” link. This opens a tutorial customized for this app submission on how to create an APN Certificate in Apple Developer center: (login above). Follow the Seattle Clouds tutorial for this part.

12) On the Apple Developer home page, click the icon next to (or text under) “iOS Provisioning Portal.”

13) Click “App IDs” in the left sidebar. As far as we know, each separate app needs its own App ID.

14) For an app’s first build, click “New App ID” in the upper right corner.

15) Enter the first part of the app’s “long name” as the “Description.” Ex: Sugar Blaster. Leave the “Bundle Seed ID” as is. For “Bundle Identifier,” follow their guide. In our case it could be “com.wendi.sugarblaster”. Click “submit.”

16) We are returned to the App IDs page. Scroll down and find the one we just created. Click “Configure” on the right side of that row.

17) Click “Enable for Apple Push Notification Service.” We’re now at step #6 on the Seattle Clouds tutorial for making an APN Certificate, so return to that page. Click “Download apnrequest.csr” and save the file in an easy-to-find place (e.g., desktop or downloads folder). You can rename it to keep track -- but since you’ll only be using the customized file once, you can also just delete it after the submission process is over.

18) Return to Apple Developer page for enabling Push Notifications. Click “configure” next to “Production Push SSL Certificate.”

19) As far as we know, you can disregard the page titled “Generate a Certificate Signing Request” and just click “Continue.”

20) Use the browse button and choose the “apnrequest.csr” file from our step #17. Click “Generate.”

21) You should see a green check mark after a few moments, and the message “Your APNs SSL Certificate has been generated.” Click “Continue.”

22) Click the Download button and save the file in an easy-to-find place. Again, you can rename it if you want to save these files for the future, or (since they’ll be stored online) just leave the name as-is (aps_production_identity.cer) and delete it after the submission process. Click “Done.”

23) Return to the Seattle Clouds customized tutorial and click “Next” in the lower right corner.

24) Now we’re back at our step #11, but this time we have the APN Certificate. Click “I want Push Notifications Enabled” if it doesn’t show up automatically. Use the “Browse” button to find the “aps_production_identity.cer” file from our step #22. Click “upload” under the browse box. If the upload works, you have to again click “I want Push Notifications Enabled.” You should see your .CER file name. Then click “submit” in the lower right corner.

25) You should see a page that says “Done. Submission Complete.”

26) Return to the Google Doc. On the “Apps to Make” page, go to the “Date iphone submitted” column and replace “READY” with today’s date and your first name or initials.

27) On the “Submission” page of the Google doc, fill in the “Submitted by whom?” column with today’s date. Fill in the “Submitted when?” column with the app format (e.g., IOS) and your first name or initials.

28) After Seattle Clouds reviews and submits the app to Apple, it will show up in our iTunes Connect account: (login – U:; P: 9090Thinkapple). Click “Manage Your Applications.” Check at least once a day (starting the next day) until it appears.

29) Once the app appears, click on its icon. On the right, click “Rights and Pricing.”

30) Leave “Availability Date” as is. Fill in the appropriate price tier and other info. In most cases the “Price Tier Effective Date” will be “Now,” and the “Price Tier End Date” will be “None.” Click “Save.”

31) If your app contains mature content, take the following actions in iTunes Connect to prevent the app from being rejected. Click the app’s name in our list of apps. Click “View Details” under the app icon in the lower left corner. Then click “Edit” next to “Version Information” in the upper left. Scroll down to the “Rating” section. Change at least one of the categories to “Frequent/Intense.” Most often you’ll only have to do that for “Mature/Suggestive Themes” (e.g., the Sensual Woman app). Click “Save” in the lower right. The app should now display a 17+ age rating.

32) Keep checking iTunes Connect until the app has a green bulb under its icon. Click the icon and you should see “Ready for Sale” in the Status line.

33) Check the iTunes App Store to make sure that your app appears and that all the info, screen grabs, etc. are correct. All, Inc. apps can be viewed at this iTunes link:



Posts : 7
Join date : 2012-02-01

Back to top Go down

Back to top

- Similar topics

Permissions in this forum:
You cannot reply to topics in this forum