This question seems related to XCode Build and Archive for Enterprise Distribution builds old archive but the answers have not worked for me;
We have an iOS application that is distributed using the Enterprise Distribution method. This has been updated regularly for the past year by issuing a new IPA and having users delete and reinstall the app. Lately when I archive and distribute the app it installs correctly, but it is a previous version from a few days ago with none of the recent changes. These are things as simple as text labels and alerts with the wrong text.
I've done everything I can think of, including:
Confirming it builds and runs correctly in the simulator and when building directly to an iPhone. Everything works great in these cases.
Cleaning the project.
In the Organizer, deleting all archives and removing the project.
Manually deleting the DerivedData folder.
Renaming the IPA and updating the distribution plist to ensure that the file isn't somehow being cached on the web server.
Deleting the entire project and doing a fresh checkout from SVN.
Even when I do all of these things together, so that I've completely removed the project from my computer and Xcode and re-archived it with a fresh checkout of the source files, it still archives an outdated version. Where could this be coming from? Should I just reinstall Xcode completely?
Since you have deleted and checked that your build files are clean from old rubbish, I would have a look at the actual source files and the project and make sure you are actually making your changes on the right place.
Right click on the files that you are working on in your project and select "Show in Finder" and see where they are actually located. Maybe they are in a different location than you would expect?
Do the same with the files under "Compile Sources" in your target, and make sure they are the same files and at the same location as the ones you have been editing.
It could be that if you at some point has fiddled around with your files and projects that you actually imported the wrong files and that you are editing different files than the ones included in your build. It happened to me once, I had to re-import lots of files to my project to get it working again.
The network was caching it! The wireless network in my office is serving up a cached version of the IPA from yesterday, while an external network downloads the latest copy just fine. It's embarrassing that I never thought to check this, but I suppose the solution is often obvious in hindsight.
Thanks to Jake and Mike for the suggestions; I'm sure they will be helpful to others who come across this question.
Related
I'm working with multiple people on an app in Xcode. Today I started Xcode and tried to run the app on my simulator, but it doesn't run. It builds and gives no errors, but the app won't appear on the simulator. As many questions suggested, I needed to select my executable in the schemes (Manage schemes -> ‘Scheme name’ -> Run -> Info -> ‘Executable dropdown’). But when I edit the scheme, my executable is not visible in the dropdown. Also the .app won't appear in the products folder as it usually does. How do I get it back?
I've tried many things like deleting Derived data, deleting the project and checkout again via version control, I even deleted everything related to Xcode and downloaded it again. But none of this worked.
I also read somewhere that AppCode (IDE from Jetbrains) stores the .app somewhere else. Perhaps this causes an issue with Xcode? But as I said, even if I download the bare project from source control, it builds but doesn't run.
I'm working with Xcode 9.1 at the moment. Also working With AppCode Version 2017.3 EAP.
Maybe the project.pbxproj file does not have the correct reference to the app executable. This might happen when a merge conflict occurs and is not solved correctly.
Try to look for differences in the project.pbxproj file, concerning the occurrences 'YourApp.app' and restore or adjust these where needed.
To look for these differences use the commit history in version control tools like Git Kraken.
When this is done, clear derived data and clean the project. Then build.
The app executable should pop up again now :)
I have an app where I recently replaced the app icons, I removed all of the old assets from everywhere in the project.i removed cache and also uninstalled the app from mobile. After installing and running I am getting the deleted App Icon again in the App
Completely delete the binand obj folders in your project folders (all projects from solution).
This might help on top of what you've already tried.
Other possibility is, you have forgotten a resource ;)
Often times, the problem is between the keyboard and the chair.
Try this solution :
Use "Build > Clean all Targets" and then build and run. Xcode doesn't always see that images have been updated, and leaves them out of incremental builds. Cleaning before building makes Xcode build the app file from scratch, and will pick up any images it's failing to get
Clean and build your project.most of the case it works. :)
Alright, so I had been having issues with this and never resolved them, finished my app and published it before this caused major problems -
I have pods installed for my Xcode project so I had been working off a workspace. I had always backed up in the past by copy pasting my project folder then renaming, however more recently something happened that cause every change to my workspace to affect all previous versions.
I tried everything - saving to external hard drive, github, etc but I just ended up going on working on the workspace and making sure I didn't screw anything up. Along with this issue whenever I clicked on the Xcode project that is in the project folder, none of my new code would be there.
That Xcode project version was from several months back and the only way to see my new code was to click on the workspace. I asked a question about this but no one had an answer.
A week ago I finished the app, archived and uploaded to App store. It is now published, however I want to update so today I went to my workspace and the project file above the pods file was RED meaning not there.
I have no idea why this would have happened. Dragging the Xcode project i the folder to the workspace again, just runs the very old version.
I need to get my binary back and solve this problem. Im desperate. I have this:
One of the export options is save for development and such.. Is there a way to get my binary back from this archive? How can I fix this problem?
I have a few kits installed but now I decided I do not want to use Digits & Twitter anymore. I deleted the frameworks manually but they keep popping up in the Fabric app and in my dashboard.
I've been looking everywhere but an option to remove or delete the kits seems to be non existent. I also didn't find anything in the documentation about this.
I had the same issue as you. I tried wiping my DerivedData path and cleaning my build folder, but had no luck.
In the end the only thing that worked for me was deleting my App on Fabric and re-creating/re-installing it. I think the key step was removing the Run Script in Build Phases and re-adding it with the new key during the installation process.
I know it's not the best solution, but I can confirm that it works. The downside is if you had any other Kits installed (Answers, Beta, etc) I'm pretty sure you'll lose your data.
Try deleting the files DerivedData path and clean build folder
cmd+opt+shift+k
then re run the application.
Also check once again the Framework search path in xcode settings.
Me and my friend are trying to collaborate on a project that he recently uploaded to GitHub. I checked out the repository but do not get the same project structure after opening it in Xcode. The project contains Cocoa Pods which in Xcode appear as a separate file along with the main one. The problem is that when opened in Finder on my computer, the main project contains folders DummyApp, DummyAppTests and Pods together with some other necessary files as in the picture below.
When the main file is being opened in Xcode, only the Pods folder is recognised. The main project file is empty and there are no error message available to provide some clues. It seems like Xcode does not recognise the other folders as valid projects and excludes them.
We compared our folders locally in Finder, both have the same files and structures. So we've figured that the check out from GitHub works fine. We've been thinking that maybe my friend needs to invite me to collaborate on that project in order for Xcode to validate my participation but found nothing of this sort on Apples Developer sites. Any ideas what might be causing this problem?
The project has been re-uploaded to GitHub, re-opened, re-checked out and all that basic stuff..
I've learned that using GUI for gits causes more problems then it does good. Uploading just the podfile(via the terminal) and excluding all the individual pods solves the problem above.