I have mac version 10.9.3 and I am using xcode 5.1 on which I set build target 10.9. Now when I am running its build no 10.9.3 or latter versions it is good. But on previous versions it is not running.
It has solved, basically it was the problem with code signing. When I changed the code signing with Mac developer, the issue has resolved.
Related
I recently upgraded iOS in my iPhone device to 12.2 (to provide support of latest versions for my app "Match4app"), and this does not appear to be compatible with Xcode 10.1. Should I update Xcode to 10.2 ?
In my Mac with High Sierra, when I click "Update" for Xcode, 10.2 is not available.
I have found this link:
https://support.apple.com/en-us/HT209606
With this comment:
"Xcode 10.2
Released March 25, 2019
Kernel
Available for: macOS High Sierra 10.13.6 or later"
How can I install Xcode 10.2 with High Sierra in order to test iOS 12.2 ?
Note: Upgrading to Mojave or Catalina is NOT an option in my old Mac (though I will try to install the macOS Catalina Patcher soon (http://dosdude1.com/catalina/) ).
Yes it's possible. Follow these steps:
Download Xcode 10.2 via this link (you need to be signed in with your Apple Id): https://developer.apple.com/services-account/download?path=/Developer_Tools/Xcode_10.2/Xcode_10.2.xip and install it
Edit Xcode.app/Contents/Info.plist and change the Minimum System Version to 10.13.6
Do the same for Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/Info.plist (might require a restart of Xcode and/or Mac OS to make it open the simulator on run)
Replace Xcode.app/Contents/Developer/usr/bin/xcodebuild with the one from 10.1 (or another version you have currently installed, such as 10.0).
If there are problems with the simulator, reboot your Mac
You don't need to run Xcode 10.2 for iOS 12.2 support. You just need access to the appropriate folder in DeviceSupport.
A possible solution is
Download Xcode 10.2 from a direkt link (not from App Store).
Rename it for example to Xcode102.
Put it into /Applications. It's possible to have multiple Xcode versions in the same directory.
Create a symbolic link in Terminal.app to have access to the 12.2 device support folder in Xcode 10.2
ln -s /Applications/Xcode102.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/12.2\ \(16E226\) /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport
You can move Xcode 10.2 to somewhere else but then you have to adjust the path.
Now Xcode 10.1 supports devices running iOS 12.2
Download xcode 10.2 from below link
https://developer.apple.com/services-account/download?path=/Developer_Tools/Xcode_10.2/Xcode_10.2.xip
Edit: Minimum System Version* to 10.13.6 in Info.plist at below paths
Xcode.app/Contents/Info.plist
Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/Info.plist
Replace: Xcode.app/Contents/Developer/usr/bin/xcodebuild from Xcode 10
****OR*****
you can install disk image of 12.2 in your existing xcode to run on 12.2 devices
Download disk image from here
https://github.com/xushuduo/Xcode-iOS-Developer-Disk-Image/releases/download/12.2/12.2.16E5191d.zip
And paste at Path: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport
Note: Restart the Xcode
Based on responses and comments below, the following was the simple solution for my issue and THIS WORKED. Now my app, Match4app, is fully compatible with latest iOS versions!
Download Xcode 10.2 from a direct link (not from App Store). (Estimated Size: ~6Gb)
From the downloaded version just copy/paste the DeviceSupport/12.2 directory into "Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport"
You can discard the downloaded version now (we just need the small 12.2 directory!)
None of the above helped for me.
I was able to install Mojave using this link here:
http://dosdude1.com/mojave/
This patch worked beautifully and without a hitch
Proof:
here's Mojave running on my (unsupported) 2011 Mac-mini
Cracked it. Just #Damnum steps and then follow the path to run xcode. Bad way but running like a charm.
Double click to /Applications/Xcode102.app/Contents/MacOS/Xcode
Just installed Yosemite and when I run brew doctor I get:
Warning: Your Xcode (6.0.1) is outdated
Please update to Xcode 6.1.
Xcode can be updated from the App Store.
But in the AppStore it looks like XCode 6.0.1 is the latest version. What's the best way to correct this?
Tis that slight lag between 10.10 being Avail and xcode getting updated. If you read the top of brew doctor output it says
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
So if everything is working, then you should do what it suggests and ignore it. The command line tools / compilers where updated for 10.10 (software update should have picked them up for you). Are you running into any issues with compiling? or just that warning.
pulling up from the comments. Your ruby and postgresql issues are from the upgrade, but it isn't really brews fault, or that compiler error warning.
with rvm just reinstall your ruby. My main dev is done with ruby-2.1.3 so
rvm reinstall ruby-2.1.3
rebuilt ruby and all my gems. The problem is that the ssl libs (maybe others) that ruby was linked to were removed / replaced in the upgrade to 10.10. The reinstall will rebuild and relink to the newer correct libs.
postgresql is slightly different. Apparently during the upgrade a couple of empty directories in /usr/local/var/postgres get removed. No idea why.
see this SO answer for how to fix that.
`pg_tblspc` missing after installation of latest version of OS X (Yosemite or El Capitan)
also if you are use pow (http://pow.cx) you will need to upgrade it to the latest version as 10.10 removed ipfw completely and only leaves pf as the firewall. so you will need to the new version which uses pf anchors.
The above steps where all I needed to do it in order to get my dev back to working.
Looks like developer.apple.com does show an XCode 6.1 as "Available Shortly" as of Fri, Oct 17, at 10pm central time. Not yet available from the AppStore. I guess I'm just too eager for an update.
I have MacOS-X - 10.7 and Xcode - 4.6.2 and made a Mac application. The client side machine is also MacOS-X - 10.7. But in my mac application there was a small error with NSNumberFormatter which when I was changing, Xcode was crashing. So I edited the code in latest Xcode and OSX. And then I made the binary of it and run in MacOS-x - 10.7, its working fine. But the source code is no more opening in Xcode - 4.6.2. Its asking for the latest version of Xcode. My question is will the binary will work fine in older version of OS-X even if it is developed in latest Xcode?
The version of OS X which your application will run on is dictated by the OS X Deployment Target in the project settings. If that is set to support 10.7, then it doesn't matter which version of OS X you built it on: the built application will work on 10.7 and later.
This setting will also set the minimum allowed OS in the Info.plist, so people trying to run the build on earlier OSes will see an alert instead of the app just crashing.
More information on setting the deployment target and building for different OS versions with SDKs is available in the Apple documentation:
https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/cross_development/Configuring/configuring.html
OK, so here's my situation :
I've got Xcode 5.1.1 on a 10.9 (Mavericks) machine
I want to build my app so that it runs on 10.6 and later
SDKs installed : 10.6, 10.8, 10.9
What do I have to do to make sure it'll show up as "10.6 and later" compatible in the app store?
I managed to get it to compile fine with Base SDK set to either 10.8 or 10.9, and Deployment Target set to 10.6. Will that suffice?
P.S. I've tried compiling with Base SDK set to 10.6, as well, but there are so many errors to be fixed, that it'd be better if I could avoid it.
So any ideas?
Yes; using 10.9 SDK with the deployment target of 10.6 will work fine.
You may find you have conditional code-paths which must be determined at runtime, perhaps based on respondsToSelector, which will require some #pragmas in order to compile successfully.
The Deployment Target defines the minimum OS version that your app requires at run time.
The Base SDK defines the level of API features that are available at compile time.
Therefore you can use 10.9 as Base SDK when building apps that can run on 10.6 and upwards.
You just have to make sure to avoid code paths that use 10.7/10.8/10.9 APIs when your app runs on a 10.6 machine.
As trojanfoe already pointed out, you can use respondsToSelector: to check if a certain class/method is available.
Another way is to use NSAppKitVersionNumber:
if (floor(NSAppKitVersionNumber) <= NSAppKitVersionNumber10_8)
The NSAppKitVersionNumber constants for the latest SDK can be found in the AppKit Release Notes.
Further details can be found in Apple's SDK Compatibility Guide.
am using Os X 10.6.4 and X code Version 3.2.3 for developing some simple app files and using PackageMaker to distribute these app files. But when trying to run the package on some other mac I am getting error that the package is not compatible with the Os X its running and file would not be installed. Is this a problem with X code or package maker. sorry for reposting it but although I tried changing base SDK to 10.5, it was getting compiled and ran well on mac I am using for development (Mac OS X 10.6.4) but when installed on mac running OS X 10.5 the .app files were grayed out and message poped up saying 'you cannot use this version of application with this version of Mac'. Any idea why is this happening? Also as mentioned earlier I am using IBOutlet for accepting user date from form and then writing that into a text file. Any idea or solution about it?
Do you have anything set in your Info.plist for the LSMinimumSystemVersion key? This is one place the system looks.
When I was brand new I had trouble figuring this out...
Make sure that your Base SDK and deployment target are 10.5 and that you have the right compiler on(GCG4.0/4.2), also make sure that when you change these settings you change it for both Release and Debug, I once made this mistake of changing it only on debug, and when I built for release it only worked on 10.6 because I didn't change those settings.