Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 years ago.
Improve this question
I am working on a Xcode8.3.3 iOS10.3 compatible project and it has some UI tests (I had written them) associated with it which were building successfully and passing until the recent dependency pod library update, in spite of warnings in the warnings tab.However, after updating my dependent pod library to newer version, the build for UI tests are failing showing same warnings that were present already as "reason", but project build is passing. Could it be due to some misconfiguration(I did not make any configuration changes though other than incrementing pod library version) or some error check set to strict or something else? No hint on what could be the issue. Do suggest.
(Note: there is no specific code that I think will be required as this is a problem with only UI tests not building and suggestions of build config -- zero code changes compared to UI tests that were building earlier -- if required I am ready to show, let me know what I have to show).
I am a newbie to Xcode. It seems I somehow clicked on disable tests option which comes when we try to run tests from the fifth icon in left pane and select test to run.Hence, the build was failing and it never notified me I had disabled tests.Now I have found this and enabled this option and it's working fine.
As you see this has nothing to do with code and thanks for not hinting out this could be an issue :) and all your kind down votes.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I have an iOS project that depends on several external dependencies (swift frameworks, objective C projects, and vanilla C). All of a sudden (with no code changes that I can see), the builds have begun failing, flagging errors:
I am on Xcode 11.3.1 with Swift 5.
This error persists even after reverting to an earlier revision of the project that was known to compile, and when attempting to build on a new machine with a completely fresh clone of the project.
I am at a complete loss at this point, any help would be greatly appreciated.
EDIT: I've noticed for some reason my compiler version was set to Swift 4.2 in my Build Settings. Now the project builds....sort of. When I try to archive the project I still have the same problem, but a normal build with Product->Build works.
Unfortunately I am unable to reproduce this error in a small project as I have no idea what change caused it to begin happening.
The solution for this problem was to disable optimizations in the build settings (from "optimize for speed" to "no optimization").
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 years ago.
Improve this question
XCode has recently stopped showing all build errors and I'm at a loss for how to correct it. Whether it be something like forgetting to put in an initial view controller, misspelling/not declaring a variable name, or pretty much anything else that would cause the project not to build will no longer show up. I've built the project on other Macbooks and it showed me the errors so I was able to correct it, but I can't get it to show on mine.
The issue might occur because of Xcode.
(1) Quit and relaunch Xcode.
(2) Clean (⌘+shift+K) and build (⌘+shift+B) your project.
If that not case, check out he answer here by Kris i.e.
Click the last icon in the top bar of the left most panel in your
Xcode window to reveal the secret Archive build errors.
I'm struggling with this problem for nearly half a year now with multiple XCode versions and Macs.
I can't reproduce bug steps exactly but the things go off when project has multiple targets like for Mac and iOS.
First of all XCode declines to take #if os into account and always highlight syntax only in one type of sections. E.g. if I have os(iOS) and os(OSX) somewhere it will chose only one and highlight only them.
Same goes for autocompletion. Things just not working in that type of projects.
I really dont know what to do since developmenet process turns into struggling. I dont want to split my project into multiple one, I'm happy with multi-target setup.
Is there a way to fix that?
Almost a year late.
Anyway I faced the same situation where a multi target OSX/iOS application in Xcode did not take into account the #if TARGET_OS_IPHONE conditional and failed to autocomplete method names from framework only showing the iOS variant.
Found a solution, based on this blog entry : you have to clearly state the Framework search path on each target in Build settings
Edit: This line was present in the iOS target settings. I copy/pasted it to the MacOS target in Xcode where it was automatically adjusted to the right path.
Edit 2: Loosely related but if you run in trouble with interface builder picking wrong classe files see this answer I just posted in another old thread.
I'm making a swift .framework, but I'm running into what I believe is a build problem. So I've simplified everything to isolate my troubles. I've attached a screenshot of my newframework.framework project (top) and my example usage of the framework (bottom). The problem I'm having is that Whatever class is unavailable when I include newframework.framework. I can confirm that Whatever.swift is indeed included in target>>buildphases>>compile Sources
What could cause this not to work?
EDIT - Adding App Build phases screenshot
Your problem, as we figured out in comments, was that you were building your framework for "Generic iOS Device" and building your app for the simulator. Xcode can't make the app build without matching architectures, so you need to choose one over the other or produce a framework that includes every architecture.
(This was posted to help people who come here from the future find the answer quickly. Hello, future people!)
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 7 years ago.
Improve this question
Recently I have learned how to program a iOS project. I coded by followed a tutorial.But the same code the different result. Maybe there is something wrong with header file? I imported a header file in the same project.Although it made Xcode no warn about "use of undeclared identifier 'UILocalNotification' ", it did't make the effect that I want.And I want to say ,in the tutorial the teacher did't have imported this header file .So mistake must not be here.
Judging by the error, it looks like you might have used a UILocalNotification somewhere in your code that you did not include the proper #import for.
What tutorial were you using? Is there a 'completed project' that they provide that you can compare your code to?
It might be helpful to include any relevant code (from your project) that will aid in the process of troubleshooting the error.
As a side note: Check how recently the tutorial was written-- if it is an older one (for previous versions of XCode), you may need to alter, remove, or add some code in order to fix certain errors.