iosXCode Build and Archive for Enterprise Distribution builds old archive

I'm working on creating an app for in house distribution enterprise level. I've created the app and tested hosting it on my own server and even getting the click to install working. Now though I have some updates to the app, I make the edits and I even see them in the simulator. When I build and archive the app things seem fine, then I go to the archived project in the organizer window, click the share button and distribute for enterprise, I enter details such as the ipa final url and the app title and then ok & save. Then I upload the app to my server and update any links to point to this new app. The click to install still works properly, but it installs the old version of the app. I've even tried this on a new device. Is there some step I'm mission that tells XCode some version to build? If so, I don't get is how the simulator shows the update fine, but the archive that is built is not showing the latest code. The app I can find in the simulator dirs is 9.4MB in file size, but the one that is saved after build and archive is only 1.4MB (the update involves a lot of added images), so is the build for archive is not even getting the new files?

if a clean won't work, try completely removing the derived data folder.

enter image description here

the default location is in /Users/you/Library/Developer/Xcode/DerivedData . if you haven't played with the DerivedData location in preferences, this is likely where you'll find the sub-folder containing the cache.

when i encounter a situation similar to the original question (retaining items i've deleted, or similarly missing items i've added or holding onto project icons i've changed), i perform a clean on my project, close it, hit Delete… in the organizer, possibly even remove it from the organizer, possibly even remove from disk and then re-checkout from git if you have it under version control in this way, then re-open the project from scratch.

I figured it out and thought I should post it in case it helped someone else.

I cleaned the project.

Build > Clean - not 100% on what "Clean" is supposed to mean/do, but it allowed the project to build from the current files rather than the old files somehow.

Related Articles
  • I have to distribute an app via AdHoc distribution. With Xcode 5 after the archiving, I select the option "Save for enterprise distribution" and then insert the web url where I upload the .ipa and the .plist. Now in Xcode 6 this option is disapp
  • I belong to the iOS Enterprise program. I am using an MDM to distribute my apps. I was under the impression that if the type of provision profile was iOS Development that it would not work for general distribution to the enterprise. Instead, an iOS U
  • Couch and chair for sale 12 months old
    REDUCED 12 month old couch and chair for sale, was £1200, looking for £200 for both Slight scuff on the front cushions easily sewn, available for collection 11/09/15
  • In xcode 6 when I create an ipa for distribution enterprise is no longer created the file .plist be included in the website for distribution. Also on some ipad when I open a link "itms-service" the app is installed normally, in others nothing ha
  • My manager is asking me to get an app (free app, not our app) from the appstore and resign it with our enterprise account and distribute it with our MDM tool. Is this allowed by Apple? Or will this possibly result in our enterprise account being term
  • Allow and Wooden Masts, boom and tiller for Enterprise Dinghy
    Boat equipment for sale - all I believe from an Enterprise Dinghy. This has all been stored in a dry garage and is decent condition. Happy to sell all as a lot or individually.
  • Excellent condition desk and drawer for sale - 4 months old
    Excellent condition desk, brand new from IKEA. 4 months old, purchased for university, however now I'm moving away to go to uni I no longer need desk or drawers as my student flat is fully furnished. Excellent for student or office use. Willing to se
  • I have a C++ application which I want to release to a bunch of testers (<10.) I need some simple way to limit those testers from distributing it further. There's no need for super-duper hack-proof protection here, but it should be impossible for norm
  • You're in Visual Studio... you press F5 (Run) and are greeted by this dialog: There were build errors. Would you like to continue and run the last successful build? Wonderful. I'm sure there are cases where running the last successful build is useful
You Might Also Like