Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 4 years ago.
Improve this question
After upgrading to XCode 10, it fails to run my tests on the device.
After finish building, it immediately shows a popup "Test Failed" without showing any errors on the console.
"Run" works on device. Both XCTest and XCUITest runs on simulator.
The error is reproducible on new project running the default UITest on the device.
Restarting the phone made it work.
Check Targets [Build Settings] Search IPHONEOS_DEPLOYMENT_TARGET
Remove IPHONEOS_DEPLOYMENT_TARGET setting
Before:
After:
Related
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 months ago.
Improve this question
I have tried quit and re-open my xCode, also restart my mac several time but still facing this issue.
Unable to run my code because of this:
It's probably because of Rosetta.
Go to Application -> Xcode -> Get Info -> uncheck Rosetta.
And restart your mac.
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 6 months ago.
This post was edited and submitted for review 6 months ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
My project can only run on devices and not simulator, it's an object-recognition app, is it possible to run a single view of my project that doesn't use any technology and is able to run on simulator? I need to do tests and I'd like not to run the app on the device every time.
Create a new target for your project. then only add specific views and relevant source file to the current new target. remember to change the active scheme before run.
To run a specific view on the Xcode simulator, you can use the "Debug View Hierarchy" button in the simulator's "Debug" menu.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 2 years ago.
Improve this question
I get this error during compilation
Multiple commands produce ....
After googling, I think this might happen because I have several info.plist files.
According to this answere I can find the several info.plist files here
Solution -> Open target -> Build phases > Copy Bundle Resources
However, the person who wrote this answere uses an older version of xCode.
I use xCode 12 and I am not sure where I can find Copy Bundle Resources
This is how my screen looks like
As EmilioPelaez indicated at the comment, you need to check out the section written Copy Bundle Resources in Build Phases. Here is the SS.
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 6 years ago.
Improve this question
I started work on a project written in ObjectiveC++ (.mm file extensions) with backbase on Xcode 7.3. During work I found that break point is not working in the app. I have reset the settings but still no success. I have also gone through below but still running in same issue
Link1 Link2 Link3
Can any help me in resolving this issue? Any idea or suggestion would be great.
Breakpoints are working with Obj-C++ code for me. Just check that you are running program with "Debug" command and signing app with developer (not distribution) certificate and provisioning profile (not for App Store)