Now that I updated to Xcode 4.2, I see that when I do a build I no longer get a “build” folder with the APP file in it. This APP file is what I’ve been using to distribute in-house for testing (along with a provisioning profile). So far, I’ve only used ad-hoc distribution for sending apps to people outside the company.
After some random exploring in the new Xcode, I discovered Archive. I made an archive, then in the organizer did a “Share.” This produced an IPA file, but when I sent it to some one to try (they already had the provisioning profile from a previous version), they got an error saying it failed to install.
What is the proper way to build an app for in-house testing by people with Mac OS?
The profile is good, it works on my iPad. Just to be sure, I downloaded a new one. Still the same problem, “failed to install.”
Are there any settings or additional steps I need to be aware of? For doing an ad-hoc distribution I need to create a new configuration, but that’s never been necessary for installing just on our iPads. Any other suggestions?
Which configuration did you use for archiving? You can check under “Edit Scheme” option panel. Make sure you have the right one. Btw the Build folder can be found under Application Data/XCode/Derived Data. It should be under User/YourUser/Library.
Are you talking about when I do a share in the Organizer window and select the appropriate provisioning profile from the popup menu? Or is there somewhere else that the certificate is added? I just downloaded the provisioning profile, so I know it’s correct. Even so, this other device has always been included in the profile, so even an older profile should still work. And I think if it’s a profile problem, it gives you a different error than just “failed to install.”
I don’t really understand schemes. If I do “Edit Scheme” as you suggested, I get a list of several schemes in the scheme window, “Run XXX.app, Debug” is always selected. If I select the “Build” scheme then close the window, it goes back to the Debug scheme if I open the window again. Which is the right scheme and how do I select it? Once selected, then do I create another archive?
And I don’t understand your path to the Build folder. I can’t find any such path or any Derived Data folder. Are you saying this is the same Build folder as before, just in a different location? If so, does that mean I don’t need to be doing the archive and all this stuff?
I also don’t really understand why this has become such an ordeal. It used to be so simple, do a build and there’s the app in the project folder. I’ve already spent days just getting my apps running in the new Xcode, now I’m wasting more days trying to share an app like I did before. So now I’m over a week behind, and still not caught up to where I was before upgrading Xcode. And I can’t do anything else until I solve this problem, so I’m stuck.
Apple is trying to create a unique development environment through which you can basically have all the tools you need in one solution. It is true that might be confusing at first, but actually is not that dramatic, in fact nowadays I think is pretty much the best IDE ever.
Anyway going back to your issue, one thing at time. Schemas: if you go to Product → Edit Scheme, you will see on the left all the different configurations listed. Click on Archive and make sure you are using the right build configuration (I’d assume Distribution Ad-Hoc or something like that) and check that within that config all the settings are right (provisioning profile is the most crucial).
If you are instead looking for the folder where the binaries are put, check under the build settings and in particular the Build Products Path value. If it’s just “build”, then you will find the binaries under: /Users/YOURUSERNAME/Library/Developer/Xcode/Derived Data. At least that happened to me two time when I forgot to set the right build path. Double check also that all the paths are RELATIVE and not ABSOLUTE.
If it is something to do with the provisional profile code signing you will have an error (code sign error)during the built and archive procedure.
Also you will have a warning message with the same thing, code sign error).
If you don’t have any code sign problem or report on the console…must be something else that i don’t know at the moment.
PS: The new Xcode sucks…i hate it and if i can i use 3.2.5 but soon we won’t be able to deploy any app with it because of iOs 5…
