So i have built a finished app using xcode 7.1 and el capitan, it works fine when running on el capitan but the today extension doesnt work on yosemite. If i take the exact same project and build it on xcode using yosemiti then it works fine on both operating systems.
My Questions.
Why doesnt building it on yosemtie make it forwards compatible El Capitan and not the other way around
Why does building it on El Capitan break the today view on yosemiti.
This is really starting to annoy me know because i know its a xcode problem and not a coding bug.
Related
I'm on El Capitan in XCode 7.3.1 and Swift 2 trying to make my mac application work on Yosemite (it just doesn't open at all with no crash logs).
I have 10.10 set as the deployment target, but that didn't change anything.
I downloaded Xcode 6.4 on another machine and loaded the project and it's complaining a ton about all of my swift code not being a thing.
I'm assuming (hoping) I don't have to figure out how to write this in an old version of Swift in order to make it work on Yosemite.
How do I know which features of the new SDK need to be made backwards compatible?
I have developed an OSX for 10.10 and above. This app works with a device in which whenever I connect device and perform some operation, the data on device gets updated on the server. This works fine on El Capitan but one of our client has mentioned an issue on Yosemite, but I've update my Mac from OS X Yosemite 10.10.4 to OS X El Capitan 10.11.1 recently. I've heard that Xcode scheme can be used to define targets for build, but I'm not much aware of using schemes. Is there anyway to simulate Yosemite on El Capitan for testing? Is there anyway to do this through Xcode?
You can choose the Deployment Target in the project settings:
However, it's not 100% reliable even if 10.10 SDK was used to compile on 10.11.
Some XIB files produced on 10.11 in Xcode were sometimes not compatible with 10.10 and not detectable when testing on 10.11, but will crash on 10.10.
e.g. When I use 10.9 SDK to compile a project on 10.10 result in crashes when the NIB files get loaded on 10.9. Some other 10.10 users reported crashes running 10.11 compiled binaries for unknown reason...etc.
To be sure it's 100% working, you should consider setup virtual machines of older versions of OS X.
I have a problem when I try to open an Alloy analyzer apps since I upgraded my OSX to El Capitan version. It shows me this message "it unexpectedly quit while reopening windows". Can anyone help..
I haven't seen this -- it works fine under El Capitan for me. Can you tell us what version of Alloy you're running? Are you sure it's not a Java version issue?
I'm needing to compile a C++/C/Objective-C project for 10.5 (ppc, intel)+ however Xcode 4+ (using 4.6) drops support for 10.6 and i believe Xcode 4 completely dropped support for 10.4/ppc. I have read existing StackOverflow and other posts about installing Xcode 3.2.6 on Mountain Lion but i don't want to do this if it's unconfirmed/will break my system..
I've tried virtualising Snow Leopard in a VMware Fusion 5 Pro VM but it doesn't allow me to as it is not a server version.
Besides buying a Snow Leopard Server DVD, how else can i compile my project for 10.4+ (ppc,intel)? I am currently running OS X Mountain Lion 10.8.3. Setting the deployment target does not work in my Xcode version, doesn't compile. I've also considered virtualising Lion, however i do not have a backup copy of (my purchased via app store) install dmg/app and i can't seem to find the download in the App Store.
Can anyone suggest what i should do or am i basically left with one option.. Dual boot Snow Leopard?.
Thanks!
I'm on Mountain Lion at the moment but the battery life is terrible and I'm thinking of downgrading back to Snow Leopard. The only thing is, now that we have to submit our apps for the 4-inch screen of the iPhone 5, will the last Xcode build supported on SL (4.2 I believe?) be able to build these apps? Or am I completely stuck on ML?
The latest Xcode with which you can use the 4-inch iPhone simulator runs only on Mountain Lion.
However, if you don't mind not using Xcode, you can extract the essential parts of the toolchain (the compiler and the headers + libraries) and use the clang compiler from the command line - it should run just fine even on SnowLeopard and compile your apps.
You are stucked to Mountain Lion! :)
Xcode 4.2 doesn't have support for ios6, neither iphone 5 nor ipad mini