Submitting iOS app to AppStore - Distribution certificate?!

I have finished developing the first version of my iOS app, and continued to complete all the necesarry steps in Itunes Connect and began uploading my app through the mac's os AppLoader. What consequently turned out to be the problem is that my app which was published in Adobe Flash Proffesional 6 was configured under a development certificate (in the deployment tab) and not a distribution certificate needed to publish it to the App Store. I generated such a certificate on a Mac and tried using it in my project through Flash 6 on my PC, however a password is needed to publish the app.
I have several questions concerning this issue :
1) Is there a way to generate a distribution certificate on my PC (not through a mac)?
2) these distribution certificates are .cer extensions - in FLASH you are instructed to browse for .p12 certificates.
3) If i can use the distribution certificate created in the mac computer in my project on my Windows PC, where can i figure out the password it requires me to enter?
This is a very frustrating matter, Adobe if you can upload a Distribution Tutorial for Publishing to App Store that would help many people dealing with the same problem...currently there is only a tutorial on how to create a .p12 development certificate...
Thanks,
Roy

1. yes, but it's much more difficult than doing it on a mac. in fact, i believe you will have to emulate a mac to do it.
2. when you create your .p12 file in keychain you enter an password. (there's no reason to use a different passwords for development and distribution.)
Go to the https://developer.apple.com/devcenter/ios/index.action using a Mac computer or a virtual Mac
Log-in.
Click on the iOS Dev Center link.
Click iOS Provisioning Portal link. (See Fig08-04.)
Click the Certificates link in the left panel.
Click the Distribution tab in the right panel.
Click the Request Certificate button in the right panel.
Follow the directions using Keychain Access to create your distribution Certificate. (See Fig 08-05.) Apple has easy-to-follow directions to create a Certificate Signing Request that is used to create your Certificate. The steps needed to create a Certificate Signing Request appear in the right panel after step 7. The only part I stumble on is when instructed to open Certificate Assistant. You will find it at the top left of your Mac's screen after clicking Keychain Access, not in the Keychain Access window.
The right panel should change to show your Certificate is Pending Issuance. Refresh the page and you should see Your Certificate is Issued and read for download. (See Fig08-06.)
Download your ios_distribution.cer by clicking the download button.
Download an AppleWWDRCA.cer by clicking the "*If you do not have the WWDR intermediate certificate installed, click here to download now." link.
Open both files in Keychain Access (using the login Keychain).
Right click your private key in Keychain Access (you may need to expand the iPhone Developer certificate shown in your Keychain Access window) and click Export. Make sure File format is Personal Information Exchange (.p12) and click Save. You will be prompted for a password that you must remember. You will use that password each and every time you publish an iOS game and you will use your .p12 (distribution Certificate) file for all the apps/games you distribute (until your Certificate expires and you pay another $99 and follow these steps again).

Similar Messages

What happens to Apps when the Distribution certificate expires?

Our distribution certificate expires in mid March. Do I have to re-build all the apps that are on the App Store with the new certificate or will they continue to install without issues?
My gut feel is that Apple would not expect developers to re-submit all their apps just because the certificate has expired but like a confirmation from someone since I am sure many have crossed this bridge.
Thanks in advance.
-TRS

+>I assume that any new submissions will have to have to be built with a profile which includes a valid certificate.+
Of course....just follow the money
It is a solid process, but of course Apple, like any business that operates around time-based/recurring fees, wants to get the 'subscriber' to re-up sooner than later.
The countdown in the dev center, etc. we see about our 'expiration' date is meant not only as a friendly reminder concerning whatever risk, it is a prod to get whatever monies out of our pockets and into theirs...sooner than later

App Builder and Distribution Certificate .P12 error

We have a Pro Account. I am building a Single Editon App using v25, running CS6 and OSX 10.8.3. Attached is my screen shot error from App Builder. (v2.6)
The Distribution .P12 certificate is valid (green light) from Apple Developer Portal (see attachment).
I have also tried to revoke and rebuild Certificate and still get this same error but in each instance the "validity date time" changes.
In Apple Developer Portal, I do not see where I can modify or change this validy date.
Help!
Thanks in advance, Tom

See:
http://forums.adobe.com/message/5374736#5374736

Code sign failures submitting iOS Air App

Hi folks,
I wondering if any of you might be able to point me in the right direction on this. I'm likewise having issues trying to submit an ipa file to iTunes Connect via Application Loader, and got as far as zipping the .app file and submitting. I get an error in Application Loader that: "Unable to run the lipo command: ... Can't map input file ..." and "Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or was not signed with an iPhone Distribution Certificate.", and "Unable to extract codesigning entitlements from your application. Please make sure ... is a valid Mach executable that's properly codesigned".
Now, before posting here, I have done the following to no avail:
a) I've regenerated all certs and mobile provisions from the top, completely on the Mac once, and completely on Windows as well using openSSL. Both times, I started at the top, from the csr request.
b) I'm able to install and run my ipa file just fine on the test iPhones using the distribution.p12 file and the associated ad_hoc distribution mobile provision. It's always only when I compile for 'app store release', using the distribution.p12 file and the app_store mobile provision that this happens.
c) I'm using Adobe Flash Pro CS6 on Windows 7 64, with Adobe Air 3.3 SDK, and I am submitting on a real Macbook Air with OS X Mountain Lion.
d) I've also gone as far as trying both sets of cert/provisions (generated on mac and windows), by publishing the ipa from within Flash Pro CS6, and also using the adt command line, but still same.. works fine as ad_hoc on the test iPhones, but will not submit through Application Loader. Same codesign verification errors.
e) My app uses native extensions, but these compile and run perfectly fine on the ad_hoc builds.
I'm pulling out my hair at this point as to what I could possibly be missing or doing wrong, or if there is a bona fide bug with the combination of technologies I'm using? I would appreciate any tips/hints/suggestions from anyone who know what I am describing here.
If there is anyone at Adobe that can look at my ipa file build for the app_store submission, that would be wonderful as well.
with kind regards,
Alex

@Marius,
Here's a step by step (verbose) of what I do from the top when I setup for a new client (which I did just 3 days ago). If there's anything here that's different, I recommend you remove everything you have from before and start from scratch, as there are times when some ridiculously unforeseen item left over can affect your setup:
(a) On a Mac, open Keychain Access tool. Go to 'Keychain Access' in the main menu, then 'Certificate Assistant' --> 'Request a Certificate from a Certificate Authority'. On the Certificate information form, enter the email address you used for your iOS Developer Program account, for Common Name, use the name you have associated to your iOS Developer account (i.e. mine was a personal account, so it's just 'Alex Yamane'), leave CA email address blank, and choose 'Saved to disk', and save the .certSigningRequest file generated somewhere handy.
(b) Log into http://developer.apple.com/ with your iOS Developer account. Click on 'Member Center' at the top. Log in. Click 'iOS Provisioning Portal'.
(c) First of all, make sure you remove everything before you start this process. You need to go backwards when you remove everything, so make sure first, you go to the 'Provisioning' section, and remove all Provisioning profiles first (both Development and Distribution). Devices, you can leave alone. Go to the 'Certificate' section and remove all Development and Distribution certificates.
(d) Go to App ID, and create yourself a new AppID for your app, just to make sure so you're using everything fresh from the start.
(e) Now go to 'Certificates', and use the .certSigningRequest file. Also create one for Development using the same .certSigningRequest file. Re-click the tabs for each and they should refresh with your new certs there. Download each one. After you do, I recommend you rename them so you know these are the newest ones you just generated (it usually has a default ios_development.cer and ios_distribution.cer file name. If you haven't yet, make sure you also download the WWDR intermediate certificate if you haven't already.
(f) Go to 'Provisioning' section, and now create a new profile for 'Development'. Then go to the 'Distribution' tab and create one for the app_store and adhoc distributions. Save all 3 provisioning profiles.
(g) On your Mac, open Keychain Access tool. First if you haven't already, go to 'File'->'Import item' and choose the WWDR intermediate cert. Then, do the same for your Distribution Certificate (not Development certificate), I've had tons of trouble in the past when I first was starting out, because Adobe's website keeps talking about the Development cert, but you only need the Distribution Certificate installed (and just use the adhoc provisioning profile to development/test and the appstore provisioning profile for iTunes submission).
(h) Once you've imported your Distribution certificate, there should be an item under the 'login' section of the Keychains column on the left that looks like "iPhone Distribution: Marius Versteegen". Click the arrow next to that and expand it. When you do, you should see a little key icon and your name again. Right mouse on that, and choose "Export 'Marius Versteegen'". Choose file format .p12, and save this file somewhere.
(i ) Now take all of those certs and provision files over to your Windows machine. Fire up Flash Pro. Open your project, and use the new .p12 file for your certificate, and use the new appstore Distribution certificate and compile. You should now have a .ipa file that's ready for iTunes submission.
(j) For me, from this point on, I've described earlier in the thread how I get my .ipa file over to my Macbook Air and upload to iTunes.
Hope this helps,
Alex

Director 12 won't publish an iOS app

It was working fine (if lots of bugs appearing on the iPad) and then the certificate ran out.
I updated the keychain cert and the provisioning file and now it won't publish the .ipa file.
Anyone struck this?

There are other issues involving certificates...someone recommended checking the Keychain to make sure there are no duplicate certificates. Also suggested checking to see if there are any certificates in "root", because they should be in "login".
The reason I suspected the codesign phase in the IPA publishing sequence is because Director would progress with the process up until about 99% completion. With the Keychain "locked," the system gives the message asking for codesign permission. That, appearing at the very end of the publishing process, gave me some sort of clue but I kept thinking the certificates were mismatched when they were actually just fine.
It was only when I had the console utility running to see what was going on that I saw the reference to the Xcode path. I had already repeatedly deleted and reinstalled certificates. In my case the failure was because Director couldn't find the Xcode /Developer folder, wherein, I suppose, dwell the Xcode command line tools Director needs to finish the job.
Verbose error messages from Director during the IPA publishing process would be helpful to say the least. There are several places where publishing the IPA can fail.
Something occurs to me...forgive me if this is too obvious a question...but are you using certificates for iOS publishing or are you using certificates for OSX applications? They have to be iOS certificates and provisioning profiles. I assume that is what you have done but I bring it up just in case others may be trying to sign iOS apps with Mac development certificates. I confess that I am not an expert in these matters...
Another thing is to make sure there is an Apple Intermediate certificate in the Keychain. More detail here, near the bottom of the page.
https://developer.apple.com/library/ios/#documentation/IDEs/Conceptual/AppDistributionGuid e/CodeSigningYourApps/CodeSigningYourApps.html#//apple_ref/doc/uid/TP40012582-CH23-SW1

My iOS Distribution certificate was revoked while my app is waiting for review.

I submitted my first app for review on 4/17/2014 - about a week ago. I just received an email from Apple (portion pasted below):
Your iOS Distribution certificate has been revoked.
You have revoked your certificate, so it is no longer valid.
Certificate: iOS Distribution
Any provisioning profiles that include this certificate are no longer valid and must be regenerated for future use.
In iTunes Connect, my app is still listed as "Waiting for Review" - since my iOS Distribution certificate was revoked, will this affect the submission process?
In the Developer Portal I still have a development and distribution certificate (names iOS Development and iOS Distribution) under iOS certificates. I believe I may have accidently created multiple distribution certificates since I was a little confused about the submission process (and ended up deleting one of them). I have only one Distribution Provisioning Profile that is listed as Invalid. Should I go ahead and make a new distribution provisioning profile? Will this affect the submission process? Sorry if these seem like trivial questions, but i'm still new to the app submission process.

Status is also "waiting for review" along with a yellow circle. the binary details all look ok including the .zip file i uploaded. now that i think about it, maybe the error messages were in response to my second upload. because i thought the first one failed, but now I see the .zip is the proper name.

"Missing Push Notification Entitlement" when submitting Air app to IOS AppStore

After submitting my Air app (and update to the existing app) to the App Store, I've received an automated message from itunesconnect stating that my app is ""Missing Push Notification Entitlement". The full message is as follows:
Dear developer,
We have discovered one or more issues with your recent delivery for "xxxx". Your delivery was successful, but you may wish to correct the following issues in your next delivery: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the "aps-environment" entitlement.
I've submitted multiple updates and never had this issue. Furthermore, I don't use push notifications, and as far as I can tell they are not enabled (nor where they ever configured or enabled) in the relevant app id on the developer portal nor in the application.xml. My Air app, as far as I can tell, isn't including any classes that are used to receive push notifications either.
Any thoughts, ideas?

Yup, i have the same issue here. AIR 3.5.something, Flash Builder 4.7 ... i received the damn mail today just seconds after successfully uploaded the app with Application Loader Version 2.8 (321). I didn't used any Push Notification services functionalities neither enabled it in the distribution provisoning profile. Like Alan_Haugen says the tone of the words make you believe that everything is fine, and that next time you upload stuff, take care to fix that. Don't know, will wait to see if the app will be approved.
Adobe please don't get angry now - but maybe is time to take problems that developers using your technology have - more seriously. You know, we are the last ones defending your frontiers in the AIR / FLASH frontlines and maybe we deserved more attention here ???? I mean the answer you placed here is the same if someone had mechanical car issues, and you suggest him to try to stop the car and start the car again then all troubles will be gone. Cmmon.
I mean there is only few calls to Apple needed and few hours of investigation to get there. And I think at least you can give us some credibility if you make us believe you are investigating the issue, and not redirect us off to stackoverflow - just like we are from Mars, and we didn't heard about it until today.
I'm really sorry for maybe a litlle harsh words, and really i would like to continue to use AIR / FLASH technologies but you must understand and i'm 100% sure that more or less all people springling around here are in enterprises. And in enterprises there are no answers like maybe, don't know, not sure, will see, etc. Because with such answers you're dead in less than needed to close one eye.

Error submitting App to AppStore

I got these errors when trying to submit my app via the ApplicationLoader to the AppStore:
1. "There is no dwarfdump executable defined."
2. "Application failed codedesign verification. The signature was invalid, contains disallowed entitlements or it was not signed with an iPhone Distribution Certificate."
The first error disappeared after a software update on my mac!
I revoked my certificate in the provisioning center and made a new one to solve the second error. It doesn't work.
I reinstalled Flash Builder...doesn't work.
The Apple support team told me to use the validate function of xcode, but I don't have one or is there a possibility to do this in Flash Builder?
I have already submitted two applications and everything worked fine.
I use the same .p12 file as for these two application and I also created a new one because nothing seems to solve the problem.
Could it be that Apple changed something in the publishing process?
In my app.xml there is the following hint for iPhone:
<iPhone>
        <InfoAdditions><![CDATA[
            <key>UIDeviceFamily</key>
            <array>
                <string>1</string>
                <string>2</string>
            </array>
        ]]></InfoAdditions>
        <requestedDisplayResolution>high</requestedDisplayResolution>
    </iPhone>
I read a lot of problems coming up with the new application loader and many other users suggest to download an older application loader version (1.3). I can't find this version anymore?
Does somebody has a link for me so that I can test this issue?
I really bought me a MacBook to publish Apps with Flash Builder and I feel really sad because I investigated more than 16 hours in this problem.
I would be very happy if someone has a hint or solution for me :-)
Best regards,
omi

Unfortunately this isn't the problem...
Here are some commands I tried:
mjus-MacBook-Pro:~ mjus$ codesign --verify -vvvv -R='anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.1] exists and certificate leaf[field.1.2.840.113635] exists'
/Volumes/DISK_IMG/BITTENEU/Payload/Ultimativer\ Liebe\ Rechner.app /Volumes/DISK_IMG/BITTENEU/Payload/Ultimativer Liebe Rechner.app: valid on disk /Volumes/DISK_IMG/BITTENEU/Payload/Ultimativer Liebe Rechner.app: satisfies its Designated Requirement
test-requirement: code failed to satisfy specified code requirement(s)
mjus-MacBook-Pro:~ mjus$ codesign -dvv /Volumes/DISK_IMG/BITTENEU/Payload/Ultimativer\ Liebe\ Rechner.app Executable=/Volumes/DISK_IMG/BITTENEU/Payload/Ultimativer Liebe Rechner.app/Ultimativer Liebe Rechner Identifier=fgu.mue.lieberechner Format=bundle with Mach-O thin (armv7) CodeDirectory v=20001 size=104325 flags=0x0(none) hashes=5208+5 location=embedded Signature size=4277 Authority=iPhone Distribution: MY NAME Authority=Apple Worldwide Developer Relations Certification Authority Authority=Apple Root CA Signed Time=02.02.2012 22:49:54 Info.plist entries=36 Sealed Resources rules=5 files=53 Internal requirements count=0 size=12
mjus-MacBook-Pro:~ mjus$ codesign -d --entitlements - /Volumes/DISK_IMG/BITTENEU/Payload/Ultimativer\ Liebe\ Rechner.app Executable=/Volumes/DISK_IMG/BITTENEU/Payload/Ultimativer Liebe Rechner.app/Ultimativer Liebe Rechner ??qq|<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
<key>application-identifier</key>
<string>4QS6XB8894.fgu.mue.lieberechner</string>
<key>get-task-allow</key>
<false/>
    </dict>
</plist>
I really got a headache after 20 hours research and no result...

Can the trial version of Director 12 publish iOS app for in-house distribution?

Can the trial version of Director 12 publish iOS app for in-house distribution? What about the purchased version, any limitation on the type of distribution?
I am getting the "Publishing to iOS appstore is not allowed for this movie. Click on "More Info" for more information".

This invaluable YouTube video goes through the whole process .....
http://www.youtube.com/watch?v=QDTqK16ir6c
As mentioned in the associated YouTube comments, "When you have Xcode installed, go to Xcode > Preferences > Downloads and be sure to install the command line tools"

If I've installed an app from the app store and the author's distribution certificate expires, my app will still run or not? Thanks a lot.

If I've installed an app from the app store and the author's distribution certificate expires, my app will still run in my device or not?
For example in the case that the author won't renew the certificate itself, i guess his app will be removed from the app store; but what happens to the apps installed in the devices?
Thanks a lot.

The author's certificate is only used to authenticate the author when the app is uploaded to the app store.
The app is then signed by Apple before being added to the app store.
Nothing will happen to your app except you won't get any updates.
Evertually, iOS upgrades could stop the app from working if you upgrade iOS beyond what the app supports.

I cannot download or upgrade any apps from AppStore on my iphone 4 after upgrading to ios 5.1.1

I upgraded my iphone 4 to ios 5.1.1 using itunes.
After which I started using my phone as usual.
I was not able to upgrade or download apps from AppStore using wi-fi or 3G.
When I select any app for upgradation or downloading it starts, But It stops at 'waiting' stage , And never goes to 'loading' stage.
Please help resolve this issue.
Thanks!

Have you tried buying or upgrading on your mac or pc via itunes? You may have bad wifi/3G connections. And, for 3G, most carriers place a file size limit on tranmissions. I think that affects app downloads, if they're big.

After updating to ios 8.2 i can't download and update the apps in AppStore on my ipad

after updating to ios 8.2 i can't download and update the apps in AppStore on my ipad! What happens?

It may just be a glitch. Try going into the app store signing out, then sign back in and see if it clears up.

"no access to the digital certificate" - Trying to export my first iOS app from Flash - Help please

Hello
I'm trying to export my first iOS app from flash to my desktop / on the device (Flash Pro CC, Iphone5)
I followed the instructions on the adobe website to build an air app for iOS but on the last step it
doesn't export the app.
What I've done so far:
- Apple developer account
- creating the certificate + convert it to .p12
- app ID / Name etc.
- creating the provisioning profile from apple
- iOS Air app in flash (Only Text "Hello world" with a tween)
Now i have to load the certificates into Flash & enter a password (is it the password that
i entered in the certificate or from my developer account/ Apple ID password? Both didn't work at the end)
When i klick on publish in the last step than it loads a while but then i get the Error:
"no access to the digital certificate"
What is wrong? Can you help me please.

Also, I should say, when I go into my phone on the computer and try to install an app, I get this message:
Unable to start operation. Installer is already in use.
Any ideas

IPhone Apps Distribution Certificate on Windows XP

Hi there! total newbie here!
I had an idea for an application which i wanted to be programmed. being a total total newbie i asked someone to make it for me. its coming along nicely and will soon (hopefully) be on the app store.
The thing is, i need to get a app distribution Certificate for the application.
I do not have a mac and was wondering if i can get it some how using my windows computer?
If that is not possible, could it be done by someone using THEIR mac....or is a certificate something which can only be done using my own machine?
Hope someone can help me.
Thanks

If you trust your developer, your best bet would be to do all the downloading at that end. Your key and certificate can then be archived for your future use. In any case, you won't be able to use these docs without a development environment on a Mac. No matter where you download them, they need to be installed on a Mac and only an experienced developer should attempt to build the distribution package with them.

I have a problem, i can't generate with DPS App Builder "App distribuzione.zip" to be sent to Apple to publish APP, this is the error message: is not a valid distribution certificate Apple. What do I do?

I have a problem, i can't generate with DPS App Builder "App distribuzione.zip" to be sent to Apple to publish APP, this is the error message: is not a valid distribution certificate Apple. What do I do?

As Bern510 says, you'll need to recreate certificates that are valid. I suggest following our step-by-step publishing guide, which walks through how to obtain certificates correctly.
http://help.adobe.com/en_US/ppcompdoc/Step_by_step_guide_to_dps_se.pdf
Neil

Submitting iOS app to AppStore - Distribution certificate?!

Similar Messages

Maybe you are looking for