I just updated to Xcode 9.3. I opened my project and I have a Project Settings warning that says "Build Settings" with a checkmark and "Project "X" - Enable with Recommended Warnings" also with a checkmark. Under that it says
This will enable the following recommended compiler warnings:
Implicit retain of 'self' within blocks
Overriding Deprecated Objective-C Methods
Pressing "Perform Changes" brings up "The working copy X has uncommitted changes." and underneath: "Do you want to continue upgrading to the latest recommended settings and performing project cleanup? It may not be possible to undo this operation." With a continue button.
As a beginner I haven't seen this before and I don't want to break anything. My question is, what should I do? Is this normal behavior and should I allow it?
It’s typically fine to click through this alert and enable those warnings.
This is normal behavior, which typically occurs after updating Xcode to a new version.
Each Xcode project has a bunch of compiler settings, which can vary from project to project. Some of those determine which things in your code it will warn you about. There are a set of these that are turned on by default, and that set changes over time.
The second alert about the working copy having modified files is because you are using git and haven’t committed all changes.
Related
I am using Xcode Version 12.0.1 (12A7300). When I tried to build a simple online course project, it built successfully, but I keep getting the warning to update to recommended settings regarding Quoted include in Framework Header.
I am NOT doing anything with pods at the moment. In fact, I uninstalled and removed pods completely from my Mac just in case it contributed to the problem. How do I resolve this issue?
I hesitate to click "Perform Changes" as I think this is exactly what will cause pods to blow up double-quotes vs. angle brackets issue later. I want to solve this issue first before I proceed.
I had to do this for one of my projects just now:
Go ahead and click "Perform Changes". This will enable the dreaded warning but also update LastUpgradeCheck in your Xcode project file. The new value in LastUpgradeCheck will prevent Xcode from showing the "Update to recommended settings" alert for this recommendation.
Then, manually disable the "Quoted Include In Framework Header" warning in your project file. You can follow the instructions in this answer if you just select "Flash Chat iOS13 project" instead of "Pods" in Step 1.
The result should be that your project file will have an updated line looking similar to LastUpgradeCheck = 1210; (possibly with a different number), and then one or more added lines with CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER = NO;.
If you add back in cocoapods later, you may have to repeat the steps for the Pods project, or you may be able to get by with just updating cocoapods if the fixed version is released.
I loaded a Maven project in IDEA 2018.1.5. I configured an "Application" run/debug configuration to run it.
I could have sworn that in the past, IDEA would automatically invoke "Build Project" before Run/Debug if any source files had changed. Then something happened recently, and it no longer does. Now, every time I run/debug the project, it runs the compiled code even if it's stale (ignoring changes I made to the source-code).
I checked Settings -> Compiler -> "Build project automatically" is on. I think I tried disabling it at one point and I did not notice a difference. What other setting could be causing this behavior?
Edit run configurations, select the good one, make sure "Build" is present in the "Before launch" at the bottom of the dialog box.
I have an iOS project that builds and runs fine, but the "Clean Build Folder..." option is disabled. As a matter of fact, it is disabled in all of my projects (all iOS, some in workspaces).
They have not been upgraded from previous Xcode version as discussed in this thread.
To See the Clean Build Folder... option, hold the option key while viewing the Product menu.
What can I do to enable it?
Update:
Almost a year later. Currently on Xcode 6.3. Still no luck.
I tried the following steps.
Preference --> Locations -->
For derived data, click "Advanced".
Inside build location, choose "Unique".
The "Clear Build Folder" button appears again.
I had this problem with a project in Xcode 8, and found that in addition to the setting #ycwjjjj mentioned, I also needed to check File → Workspace Settings… → Advanced… and switch away from Custom Settings to Unique (or Xcode Default).
I've just upgraded to XCode 5. Now, as soon as I type into the code editor showing a project's read-only file (accidentally or misguidedly) XCode makes it writable. No warning. No visual indication at all. I don't even have to attempt to save it.
We do use source control, but not git or subversion.
As you can imagine this is quite disastrous. I have tried with "source control" enabled and disabled, with no change in behaviour. I've tried searching on the web as well as here, but haven't even found a reference to this behaviour, let alone any complaint. Is it just me?
Is there a way to turn it off?
Thanks.
I have a project that I refactored for iOS 5 and ARC. It builds and runs fine, Analyzer finds nothing and I'm on the brink of submitting it to the App store. Before doing that, I thought it would be a good idea to check for leaks, just in case I missed something during the arcification. However when I choose "Product -> Profile" from the XCode 4.5 menu I get a flood of warnings and errors. All of them indicate that the build for profiling is not recognizing that the project is using ARC. The scheme settings for profile are set to use the same arguments and environment variables as run, but run works and profile doesn't. If I choose the "Profile without building" action, everything works. I've checked to make sure that there is only one version of XCode installed, checked the path, and it's all good. This is not a show stopper, but I'd like to know what's happening, and what setting to tweak if that's all it is.
Problem solved by deleting project.xcworkspace and xcuserdata folder from the project bundle. Apparently they got corrupted somewhere along the line.