This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
Xcode 4 - The selected run destination is not valid for this action.
Hi everyone,
I'm currently learning Obj-C and I'm dealing with a book that provides a lot of sample xcode projects.
I've a problem when trying to run the code: it appears an alert saying "The selected run destination is not valid for this action".
This happen only in xcode 4+. In the old version all work fine.
Can you help me solving this? Thanks a lot.
I had this problem also.
You need to make sure the Base SDK is set correctly for the debug and release of you Application Target.
If its missing i.e 10.5 then you will get this message.
in my v4 of xcode it does not have a 10.5 sdk. But my Application Target was set to 10.5.
So I needed to change it to 10.6.
I did this by selecting the Targets Build settings of the Project.
and then changing the base SDK's there.
Related
I've been trying to enable 64-bit in my project as this is now a requirement for submitting app to the App Store. What I've done so far to convert my app to support 64-bit is actually following others' questions/answers I've searched on StackOverflow and what I've found came down to
Set Architectures to "Standard architectures (armv7, arm64)"
Set Valid Architectures to "arm64 armv7 armv7s"
Set Build Active Architectures Only to "No" (some mentioned this, so I just tried it out)
Those above create errors of Apple Mach-O Linker Error. I totally got 13 errors of them. They're shown in details as pictures below:
It looks to me like a Parse framework issue but I'm too new to know that for sure. Even so, I've tried to to replace my current Parse.framework with a new one I downloaded from its website. It created even more issues that might be caused by my bad on how I replaced that new framework. I've searched on Parse website what the best way to update framework but answers I found seem there's no certain way to do it. Anyway I followed this https://parse.com/questions/what-is-the-best-way-to-rollout-new-parse-changes but it's not working.
So I decided to drop my question here hoping someone tapping in to guide me the right path to go before I fall into the long wrong one. Thanks very much in advance.
I solved this question by successfully upgrading Parse.framework (also thanks to #Raptor) to the latest downloaded from Parse website.
This question already has answers here:
Xcode - OSX error: -fobjc-arc is not supported on platforms using the legacy runtime
(3 answers)
Closed 8 years ago.
So I am trying to run the code that I have written up from a tutorial however I have come across this problem. Could anyone help me out?
http://imgur.com/dPpUeBD
first off, the error you are getting is -fobjc-arc is not supported on platforms using the legacy runtime. clang is exiting with a return code of 1, which just means it failed (not sure where else you are getting the "1" from).
the reason you would get that error is because you are trying to build for some old system that doesnt support ARC. you dont even specify if this is iOS or Mac OS so giving you more of an answer is difficult.
I released version 1.1 of my app onto the App Store last week, and now have had to produce 1.1.1 very quickly. Last week, I was running XCode 4.3(.1, maybe) on Lion. There were no validation issues when uploading version 1.1 using XCode's Organiser. This week, I have upgraded to Mountain Lion, and been forced to upgrade to XCode 4.4 as a result. I have changed about 10 lines of code for version 1.1.1. Now when I try to distribute the app, XCode's Organiser fails, with no helpful error message. I tried using Application Loader, which gives me the error: The app references non-public selectors in Payload/AppName.app/AppName: instance
From what I've seen around the Internet, this is most probably because I'm using (as it suggests) a private API. But that can't be right, the only code I added was a new BOOL and then setting it to YES and NO a few times.
I need this update out ASAP, as it fixes a nice big flaw to do with the app launching. Any help is greatly appreciated.
EDIT: As an aside, I reverted my code back to 1.1, then tried to distribute that, and got the exact same error message. Considering they let it upload last week, it seems strange iTunes Connect is now rejecting it.
This could be a false-positive on Apple's part. Do you have methods named "instance" in your code? Does changing them to something else solve the problem?
When you read the Class Reference of every object of iOS, you will find:
Available in iOS 2.0 and later.
There are a program or a way to list all function and the minimum iOS system?
How can I know if the iPhone with iOS 3.0 will run all iOS function? I can check it in runtime with respondToSelector, but can be more easy with source code?
Set your project's base SDK to iOS 3, and see if it builds.
AFAIK there is no way to list all the APIs you use in your app into one list and check that you are building past the minimum for all those APIs. You will just have to check each one, one by one. Highlight the API in Xcode, and then click escape and it will tell you very easily.
But also I have to mention that this won't be extremely necessary since you should test on the minimum OS you are building for and if it crashes at any point then you have your issue for that certain API.
This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
How to do the documentation in objective C?
Is it possible to write class/method documentation in Objective-C in a way that Xcode 4 displays them in the quick help, and/or generates a doc document from it in the style of Apple's own documentation?
Displaying it live - not that I know of.
But as for generating Apple like documentation, the best I have found is appledoc which I've been using for a year now. If accepts a wide range of commenting styles including Javadoc styles and can generate very Apple like documentation which it can also install directly into your Xcode help system.
I don't know if it still works for Xcode 4 but for Xcode 3 you could generate API doc sets using doxygen.
Apple has a set by step guide: Using doxygen to Create Xcode Documentation Sets on how to do it.
There is also the appledoc tool available from GitHub. Makes nice docsets.