Since the latest Xcode 5.1 and adding TestFlight 3.0 to my project, Xcode keeps building the project with the old 2.02 version of TestFlight.
Clean builds don't seem to help. Where else could it be picking this up from ?
I had this issue with a stale search path reference hanging around (ie deleting the folder from the project did not remove the LIBRARY_SEARCH_PATHS entry). So there were two ways to find libTestFlight.a and it was using the first, wrong, one. Search for LIBRARY_SEARCH_PATHS in your Build Settings, and if there's an unwanted old entry still there, get rid of it!
Related
I have recently downloaded new Xcode 11 GM Seed 2 so that i can update my project to support Dark mode. (I am already on MacOS Catalina latest beta version-19A558d).
I have my project(workspace with pods) working 100% fine with Xcode 10.2. When I have started building same project with newly installed Xcode 11 GM Seed 2, It randomly freeze while building with title Building X of Y tasks. It randomly stops building any file at anytime. As per my different observations, It stops building while it is building library from my Pods.
I have already tried cleaning, manually deleting derived data files. Also, i have tried by reinstalling Xcode. Also restarted Mac to give try. All trial get failed. If anyone faced same issue and know the solution, please post here.
Disable the Swift Optimizer for SwiftSoup:
I were trying all day hard to solve this issue. Finally issue get resolved.
Actually i tried to build/compile the app via Terminal. Then i found that it got struck/freezed while compiling the files from installed 3rd party libraries from pods. The 3rd party library named SwiftSoup was making problem. Then i removed that pod, and commented out the code related to that. And tried compiling/building the app again. And It worked successfully this time.
UPDATE:
I followed #Paul's Answer, that works without removing pod, keeping same pod and code working. Just need to update settings as described by him. But make sure, that you need to change this setting every time you update your pods.
I've created a new version of my app using Xcode 7 and even renamed the project. Now, when I'm trying to archive, the process succeeds, but the archive doesn't show up in organizer. When I restore my previous version and then try to archive it (also with Xcode 7), everything works fine and the archive shows up in Organizer, so that I think that anything has changed in the new version that causes the error to occur - eventually the project rename.
When I look after the archive in Finder, it is shown, but when I'm trying to open it, I get the following error message:
The archive could not be installed. The archive may be corrupt or unreadable.
I've already followed this official Apple documentation, but none of the suggested solutions work for me.
Any idea, how I can successfully archive my app, so that it shows up in Organizer?
BTW: My app consists of an iOS app, a today extension and a watchOS 2 app.
I've finally fixed my problem by restoring the last version in which the project archived successfully (that was the last backup before renaming my project, so renaming probably caused the problem) and copied all my code from the new project to the old one.
Well, that isn't a nice and satisfactory solution, but at least it is working now.
I really advise you against renaming your project, the whole trouble
you're getting in isn't worth it.
I've an old project to start work on it. Client told that it was completed in 2012, and may be with v.4.3 or some older version of Xcode. It was only targeted for iOS v.6 and previous versions. Now client wants to make some upgrades and make it compatible for all iOS devices having iOS v.7 and/or above.
I'm running Xcode v.6.3 with iOS v.8
When I firstly open up the project and run – I got too many error (actually those should be come as warnings and not errors) from GPUImage framework. I solved it one-by-one. After solved those errors, when I run it again, I failed-up with few more error of SDKs not found. I can confirm that all SDKs are added properly. And its never changed, after the project was created. However its giving me errors.
Is there something that we've to setup when we run an old project (in latest Xcode and current iOS target)? Do we need to change architectures? Header search paths?
Note, all SDKs and app source code was on Github and added as submodules to the app. I have successfully cloned it in my Mac.
Please ask me if you want more information on this.
The following steps could solve your problem. I am not 100% sure but it worked for me once. Worth a shot.
1) Go to Build Phases and remove the FacebookSDK.framework
2) Clean
3) Link back the FacebookSDK.framework to your project
4) Clean and Run
I renamed a project in Xcode 6.3 and I found the Active Schema in the tool bar has changed to settings kind of Icon and I can't run the project in simulator as well as in device.
How can I get rid of this. Please clarify..
There is a bug in xcode 6.3 which leads to unexpected behaviour when you rename a project.
Read the following post to rename your project in case you dont have a backup.
Xcode 6.3 is crashing on Project Rename
I recently downloaded Testflight SDK version 3.0 and added header files in the project as shown in https://www.testflightapp.com/sdk/ios/doc/3.0.0/. Previously I was using SDK 2.1.4
But when I archive the app and try to upload it to Testflight it still shows me my previous SDK version 2.1.4. I dont know whats the issue, i tried so many times but the sdk is still not updating to 3.0 in my project.
Just ran into and fixed this problem. In my case, the library search paths were pointing to the wrong place (with an older version of the library). Search for "Tetflight" in your Build Settings and delete or change any incorrect paths.
Only adding the header files is not enough. You also need to update libTestFlight.a to the latest version. Replace the older static library with the new one. Also make sure it is properly linked (Project, Build Phases, Link Binary With Libraries). Then clean the project, rebuild, and you should be fine.
If you already did that, you should say so in your question. Now you only mention header files. But based on your description it could be that you are still linking an older version of the TestFlight static library.
I ran into this issue first from the question, but then immediately couldn't upload my ipa into TF because it contained the SDK. TestFlight appears to be purchased by Apple and also TF has since removed support for Android.
TestFlight does not accept builds with TestFlight SDK