Is it proper Ad-hoc distribution process?!

I created .key file using openSSL.
I created CSR file using openSSL (windows platform of course)  (as described on adobe website).
I purcahsed developer certificate from apple (99$ yearly).
I installed WWDR intermediate certificate (as shown on apple's website).
Uploaded CSR file and finally received developer certificate.
Converted it into .p12 file (as described on adobe website).
Created new provision profile.
Finally, used .p12 file and .provision profile to build an ipa file for testing.... which worked on my ipad.
I wanted to install the same thing on another ipad, so I took UDID of that ipad.. on apple's website, i added that device.
created distribution certificate (using the exisiting .csr file, did not create it again).
created ad-hoc provision profile using for both ipads.
downloaded and used this new adhoc provision profile and .p12 (existing) to build .ipa file...
it is over 1 hour and still it shows it is building..(i use AIR SDK 3.0, command line, temporary files are showing in the publishing folder)...
usually it takes around 20 minutes to create ipa-test file..
is it normal???? did i do anything wrong?! pls help.

Hey guys I've figured this out after a great deal of hair-pulling and trial-and-error.
When I went back and double-checked, the answer is actually here in this excellent description:
http://www.adobe.com/devnet/air/articles/packaging-air-apps-ios.html
But it's a little buried and  not intuitive.
What you have to do for AIR is use the DEVELOPER certificate with the AD HOC mobileprovisoining profile. You DON'T use the ad hoc distribution profile -- it won't work!

Similar Messages

  • Test app ad hoc distribution on Itunes windows xp

    Hi,
    Do you know if it's possible to test an App in ad hoc distribution on Itunes windows xp?
    I can't find the process.
    How to load mobile.provisonning and IPA in Itunes windows.
    Thanks.

    Help! I've tried all the steps in this thread and am still unable to distribute to a phone using iTunes on Windows.
    In summary, I've created and built an app on my Mac Mini and deployed it to my phone using an ad-hoc provision generated by the developer portal. Taking the same app-bundle and mobile provisioning file to a windows computer and attempting to deploy it to another phone, produces this error:
    "Could not be installed because it could not be verified"
    I'm trying to figure out why this is failing, surely one of the many steps I've taken is not quite right.
    Here are the details:
    I created device ids for two phones we’d like to test.
    I am using iTunes on a mac.
    Then, using the developer portal, I created an ad-hoc provisioning profile for an appID I created earlier.
    Then, using XCode, I configured the signing of my app to use the provisioning profile just created.
    Then, using iTunes on my mac, I dragged the app bundle and provisioning profile to the applications panel.
    Then I clicked sync – it succeeded and the app works on my phone.
    Looking in the settings on my phone, I see a profile for the ad-hoc provision.
    I emailed the app and the provisioning profile to my brother to install on the other phone.
    Using iTunes on windows, he dagged the app (directory) and provisioning profile to the applications panel.
    He clicked sync – it failed – "Could not be installed because it could not be verified"
    Looking in the settings on my brother’s phone, we see no profile for the ad-hoc provision.

  • Xcode ad hoc distribution not working

    I am running Xcode Version 4.6.1 (4H512)
    I use ad hoc distribution to push my ipa and plist files, I have done this many times before....
    It doesn't work now.
    Has the process changed?
    VERY frustrating

    post your question on the developer forums at http://devforums.apple.com

  • Ad Hoc distribution under Enterprise license

    Hi,
    I have a customer who's workforce has a 1,000 iPads and is interested in distributing their publications either Ad-Hoc or through Internal Distribution, without going through the Apple Store. Are there any issues, limitations using the Enterprise License with Adobe DPS?
    I understand Apple has a 100 unit limit on Ad-Hoc using the Developer License.
    Tony

    Apple has a 100 device limit per provisioning profile for ad hoc distribution. It's a cumbersome method at best and won't scale easily to 1000 ipads.
    The correct solution for this type of desired behaviour is an Apple Enterprise license and DPS. This will let you build an app that can be distributed outside the Apple app store, to your employees only. Depending on theneed to control the level of access to content, folios can either published as public free ( controlling access by controlling the app distribution) or published as public/retail using the direct entitlement APIs to provide login level access to the folio within the app.

  • Approval before COST DISTRIBUTION Process

    Hi,
    Is there any standard functionality (in 12.0.6) of Approval available before Cost Distributions ?
    After importing actual transactions, creating pre-approved batches or doing Project Transfer, user want to put restriction on Cost Distribution. They want Approval should come into the picture before running Cost Distribution process.
    Really appreciate any standard or customize idea.
    Regards,
    Khan.

    Hi
    The workaround you may consider is enabling the requests of cost distributions only for certain responsibility. Give that responsibility to the user who would check the expenditure and approve them. After the approval that user would run the cost distribution.
    Dina

  • Ad Hoc distribution not working

    I am trying Ad Hoc distribution for the first time. I generated the Ad Hoc mobile provision profile with the user's UDID. I built the app as Apple describes. I sent the provision file and the zipp'ed app to someone running Windows XP.
    They dragged the provision file into iTunes and that seemed to install (when they did it a second time it said it was already installed). When they dragged the .app directory into iTunes, the cursor changed to a Plus sign as they dropped it there. However it was not then visible in the Applications part of the library. When dragging it into iTunes a second time, it **did not** indicate it was already installed.
    Any idea what the problem could be? If somehow their UDID didn't match the one in the provision file (or the one in the app), would it give this behavior?

    I had this problem when doing ad-hoc on Windows before. I created a compressed copy of the application using the compress feature in Finder. Unfortunately, when that ZIP file is extracted on Windows, you get both a .app folder and a .app file in the extracted directory. Not sure what's in the extra file (Finder resources, maybe?) but it is a little confusing.
    I solved the problem by writing a script that uses the command-line zip command to create an .ipa file, which is properly-interpreted by Windows and Mac OS iTunes. I don't think the structure of the .ipa file is documented anywhere, but it's just a ZIP archive with a "Payload" folder containing your .app bundle. If you want to see what one looks like, just run "unzip" on an IPA from your iTunes library.
    Oh, and I suggest that you personally try out your install instructions on a Windows machine before sending a build out to a tester, if you can. I use Parallels to do my Windows-based testing, but there are lots of other options.

  • Ad hoc distribution / .mobileprovision error...?

    Using the Ad hoc distribution / .mobileprovision capability (with the test users required UDID already added to our Apple Dev account) our test user is dragging the .mobileprovision file onto his iPad listed in iTunes but is getting this error message: "xxx.mobileprovision was not copied to the iPad (xxxiPad) because it cannot be played on this iPad". Any ideas how to solve this so he can deploy our app onto his iPad?

    hello
    i had same problem, so i checked the mobileprovision file and yes my newly added device wasn't in the list
    so i re issued the mobileprovision, checked that my additionnal device is present, but then i got the same message when trying to add it to this new device from itunes...any clue ?
    thanks !

  • Error when installing an ad hoc distribution build - what is this error?

    I've followed all the manual instructions to the letter I believe. But when installing the app and provisioning profile on an iPhone (one of the iPhones in the profile) the following error occurs:
    the application someAppName was not installed on the phone because an unknown error occurred OxE8000001
    Does anybody know what that means and how to fix it? I'm stumped!
    I wanted to test with an ad hoc distribution before trying to place the app in the app store.
    Thanks!
    doug

    Same here. I'm still trying to get the big picture as to what these deployment steps are for.
    I got my ad hocs to work, and now I'm trying to backtrack what I did:
    - Program Portal stuff:
    1. Added my device ID
    2. Created my app ID
    3. Created my adhoc distribution profile with matching app id and device id
    - Downloaded the adhoc mobileprovision files and placed it in ~/Library/MobileDevice/Provisioning Profiles
    - I have my certificates in my login keychain:
    1. Apple Worldwide Developer Relations
    2. (Developer) iPhone Developer: My Name
    3. (Ad hoc distribution) iPhone Distribution: My Name
    - I have a fresh XCode UIView based project:
    1. Created a duplicate of Release config for distribution
    2. Added entitlements.plist with get-task-allow set to false
    3. Set the Code Signing Entitlements build setting to entitlements.plist
    4. Set Code Signing Identity: Any iPhone OS Device = iPhone Distribution: My Name
    5. Set Code Signing Provisioning Profile: Any iPhone OS Device = My Ad Hoc Provisioning Profile Name
    6. Build the project (distribution config with device active sdk)
    7. Give the MyApp.app file and my downloaded adhoc .mobileprovision file to the other person
    - Install
    1. The other person drags the .mobileprovision to her iTunes
    2. The other person drags the MyApp.app file to her iTunes
    3. Syncing the iPhone successfully installs MyApp

  • Standard Overhead distribution process in SAP

    Hi...!
    I need to work on Standard Overhead distribution process in SAP. As per my understanding Overhead Distribution process means - Assessment & Distribution.
    If my understanding is wrong, Please help me by providing some inputs to proceed further.
    Thanks,
    Anil

    hi  Anil
      You bare right. To allocate overhead expenses from OH Cost Centre to Other Cost objects ( CCtr,WBS Element,Orders etc) you can se Assessment cycle or Distribution cycle.
    For Plan
       1. Creat assessment cycle T.code KSU7 and execute T.code KSUB
        2. Creat Distri Cycle T.code KSV7 and execute T.code KSVB
    for further details write back
    kkumar

  • What is the distribution process of a WP8 update?

    Hello!
    Can anybody explain to me, step by step, the process for distributing a WP8.1 update? I'm trying to understand why Orange Romania has not distributed yet the Lumia Denim update to Lumia 925 devices Orange branded. All the others Romanian carriers have already distributed this update to Lumia 925, Orange says they have not yet received the update from the manufacturer (aka Microsoft).
    The Twitter account @LumiaHelp directed me to the official support page where I can check the availability of this update for a specific country and carrier. But that does not solve my dilema. @LumiaHelp says they have no information regarding the date when this update will be made available to Lumia 925 by Orange Romania. I understand that. All I wanted to know from them was if Orange Romania has received this update for testing or not.
    I want to know why Lumia Denim is not yet available for Lumia 925 from Orange Romania. Is it because Microsoft forgot to distribute this update to Orange Romania? Is it because Orange Romania is not interested in distributing this update to Lumia 925? What party in the distribution chain is blocking this update?
    Thank you.
    Cosmin Petrenciuc

    Mhm. According to the availability webpage, you should get Lumia Denim. However, in the Software Recovery Tool, Lumia Denim is not available for your Lumia 925 Orange Romania, yet. However, your firmware variant (059T7Z3) is the SIM-Locked variant. Because I am an end-user like you, I cannot double-check if there is a non-SIM-Locked firmware variant and which firmware version that has. Furthermore, I do not know the current version for the Microsoft over-the-air servers – the recovery tool is using a different database.
    Actually, you do not have to worry about the distribution process because you cannot change anything about that at all. Either the phone notifies you about an update or not. In the world of Microsoft Mobile, there is no need to bully the phone, the operator, or Microsoft Mobile themselves. The process is so intransparent even internally for these parties, all you can do it wait and see.
    Anyway, hopefully a employee see this thread and double-checks the files for this firmware variant (there are thousand of firmware files, each model, type, region, operator, and color). Something is wrong in your case, because the availability page states you should have the update already.

  • Question about building an app for a single ad hoc distribution

    Say I want to build and app and send the app, along with a provisioning profile, to somebody to install via iTunes for beta testing.
    The "Ad Hoc" panel says the following:
    Ad Hoc distribution allows you to share your application with up to 100 iPhone or iPod touch users, and to distribute your application through email or by posting it to a web site or server. To prepare your application, the following steps will need to be completed.
    Create and Download an iPhone Distribution Certificate
    Create and Download an Ad Hoc Distribution Provisioning Profile
    Build your application with Xcode
    Share your application file and the Ad Hoc Distribution Provisioning Profile with the owner of each device
    Recipients of the application will need to drag the application file and Ad Hoc Distribution Provisioning Profile into iTunes, then sync their iPhone to iTunes to install
    My question is, do I have to build the application in the extremely complicated way described in the "distribution" tab which says "only the team agent" can do? Or is that for a mass distribution?
    Can I build my app like I do for the simulator and just send that along with the provisioning profile to the other person by email?
    What is the absolute easiest way of doing this sort of ad hoc distribution?
    Thanks!
    doug

    Another development device? I don't even have one yet.
    The person I'm developing with has one though.
    It turns out all that needed to be done was:
    (1) Build using the iPhone OS setting instead of the Simulator setting.
    (2) Set the provisioning profile.
    Then using the app and profile, just drop them on top of the apps section in iTune and synch.
    That's all there was too it. I didn't need to use all the 11 steps in the distribution section for just the ad hoc distribution, I'm happy to say!
    doug
    Message was edited by: Doug Lerner2

  • Question about Entitlements.plist for ad hoc distribution

    I still haven't gotten ad hoc distribution to work, and I don't know the difference or importance of doing an ad hoc distribution with an ad hoc distribution profile vs just providing a development distribution to the device with a development provisioning profile, but....
    In the instructions for the ad hoc distribution build there is one more set of tasks you have to do that you don't seem to have to do for any of the other kinds of builds:
    * Open the project, and select File -> New File -> iPhone OS -> Code Signing -> Entitlements.
    * Name the file “Entitlements.plist". and click ‘Finish’. This creates a copy of the default entitlements file within the project
    * Select the new Entitlments.plist file and uncheck the “get-task-allow” property. Save the Entitlements.plist file.
    * Select the Target, and open the Build settings inspector. In the ‘Code Signing Entitlements’ build setting, type in the filename of the new Entitlements.plist file including the extension.
    What is all that about? And can that be left in the distribution for app store as well? Is there any reason to even do an ad hoc distribution as opposed to just making a development distribution for specified devices?
    Thanks!
    doug

    If you are only testing the application on your own iPhone (or an iPhone that will always be connected to your development Mac w/ xcode on it), you only need to create a development profile.
    The Ad Hoc profile is useful for:
    .. Beta testers
    .. Giving free copies of your app to friends (so they don't have to buy through the store)
    Basically, it's for distributing release versions of your application to specific iPhones (your friends or beta testers have to give you their iPhone identifier strings). You cannot do this effectively with a development profile.
    And yes, you can leave the entitlement.plist file in your project when you release to the apple store.

  • Problem in Ad Hoc Distribution

    Hai.
    I created an application for apple iPhone with Object C ... I syn my application with iTunes to my device iPhone 2.0. Its working well in my iPhone...
    I have distributed this using Ad Hoc to my Friend
    My Friend try to do that... He can see icon of my application... But when he click icon it remains in the main screen... I developed my application with OS version is 2.0 .... In Greater than 2.0 version It have to running any problem???....... Please tell me step by step description ......

    Hi, did you setup the entitlement.plist correctly?
    # For App Store Distribution, skip to Step 12. For Ad Hoc Distribution, complete the following: In the File Menu, select New File -> iPhone OS -> Code Signing -> Entitlements.
    # Code Signing Entitlements Name the file “Entitlements.plist". and click ‘Finish’. This creates a copy of the default entitlements file within the project.
    # Entitlements.plist File Select the new Entitlments.plist file and uncheck the “get-task-allow” property. Save the Entitlements.plist file.
    # Set-Task-Allow Select the Target and open the Build settings inspector. In the ‘Code Signing Entitlements’ build setting, type in the filename of the new Entitlements.plist file including the extension. There is no need to specify a path unless you have put the Entitlements.plist file somewhere other than the top level of the project.
    Specify new Entitlements.plist File
    "

  • [iPhone] Ad-Hoc Distribution

    Hello,
    So, I am trying to do an Ad-Hoc distribution and I have followed the steps posted by Apple regarding this. Except, the codesign stuff is not being inserted into the build log. According to apple this has to happen in order for Ad-Hoc Distribution to work.
    Has anyone encountered this problem before? How did you solve it?
    Thanks,
    Mike.

    Apple's instructions for ad hoc distribution seem to be missing some crucial details. Check out the information here: http://furbo.org/2008/08/06/beta-testing-on-iphone-20/
    Or search this forum. Many people have asked and answered questions about ad hoc deployment.

  • IPhone Ad Hoc distribution error 0xe8000001

    Sending an Ad Hoc distribution profile .mobileprovision file and the Distribution build .app to another user to install via iTunes does not seem to work. At all. We only get error 0xe8000001 when iTunes tries to sync. We have checked and double checked the Device IDs.
    Has anybody got Ad Hoc iPhone/iPod Touch distribution to work?
    Bearing in mind:
    The Documentation for Ad Hoc is very sparse, just six bullet points
    When creating an Ad Hoc Distribution profile on the Program Portal and then choosing Edit > Modify, you can see that the Type has changed back to App Store from Ad Hoc.
    Whats going on? Does this work at all? Is there anybody out there who has got it working?
    Message was edited by: Ed Andersen

    I'm having the exact same problem with ad hoc distribution. It builds fine, and I can see the app has been signed and it includes the mobileprovision file. But still I get same the error when iTunes tries to install the app.
    Has anyone gotten ad hoc distribution to work?

Maybe you are looking for