I'm wondering whether Titanium truly works 100% with XCode 4? Can anyone confirm that they've personally upgraded to XCode 4, and have been able to build apps?
I realize that this is supposed to work, but I've seen conflicting posts about it in the Appcelerator forum.
I haven't had trouble with it, in fact I've had to use Xcode 4 rather then Titanium Developer to get some custom barcode scanning modules to work.
Related
I was starting to make simple iPhone apps using online tutorials and books and then I realized that I upgraded to OS X Yosemite and can only download Xcode 6.1 and all the tutorials are based on Xcode 5.1. I can't learn anything with Xcode 6 since there aren't many tutorials out there for Xcode 6. Can someone please suggest me what to do? basically I'm trying to learn objective-c but before learning objective-c I'd like to make a simple app through tutorials and get the hang of Xcode and learn further..
don't worry, proceed with the current version. Any differences will be made obvious by compiler warnings or errors, at which point you can deal with them. This might be considered preferable to learning to do something in a manner which is no longer current
I currently have Xcode v4.6.3 and a 4S device running iOS6. I would like to design for iOS6 as I know there are other people out there like myself who have not updated. Of course, I plan on developing for iOS7 as well and will be updating to Xcode 5, but I want to make sure I will be able to develop for iOS6 in Xcode 5 before updating to it.
I read a few other questions that had mixed answers, saying to copy and paste the iPhoneOS6.1.sdk file and select it as the Base SDK when developing in Xcode 5. I believe that's probably somewhat of how it's done, but I'm not positive and it's been a little bit since the release of iOS7 so I wanted to ask here first to make sure.
You can set your Interface Builder Document from xCode
maybe this will help:
Of course you can develop iOS 6 using Xcode 5+, you do not need to replace the base SDK, and if you do so, you wont get iOS 7 looking, so dont do that if you want to develop for iOS 7 as well.
If I only have xcode 3 what am I missing? Should I hold off my project until I get xcode 4?
This would be for ios programming.
Thanks.
You'll be missing the ability to ship software in the App Store. Building for iOS 5 (which is required for App Store acceptance) requires Xcode 4.2. That's probably the single biggest thing. If you're just looking to try things out a bit, Xcode 3 will work. But if you're planning on shipping iOS software, you'll need to have Xcode 4.
Other than that, it's mostly just feature updates. Xcode 4 has a number of features intended to speed up development. By sticking with Xcode 3, you'll be missing out on:
Automatic Reference Counting
Storyboards
The ability to drag directly from Interface Builder to your code
A much faster compiler
Various bug fixes
The ability to follow along with any of the recent tutorials referencing Xcode 4.
By sticking with Xcode 3, you get this:
The ability to follow along with some of the older tutorials referencing Xcode 3.
The ability to whine about "the good ol' days" when you finally switch to Xcode 4.
I'm developping Iphone application and I want to convert it to a universal one.
I found many tutorial that deals with this issue but they seems to be ancohérent to the new release of SDK and Xcode.
As many said I think that making a universal application is so easy.
Can you give me the necessery steps or a tutorial link? Thanks.
I think you will find necessary information and steps in this tutorial
http://iphonedevelopment.blogspot.com/2010/04/converting-iphone-apps-to-universal.html
and as a side note you should be aware of converting an existing app to universal app
http://useyourloaf.com/blog/2010/4/7/converting-to-a-universal-app-part-i.html
I am just starting iOS/iPhone development and I would like to start using XCode 4 instead of XCode 3.2. Is XCode 4 stable/feature complete enough for beginning iPhone development or should I stick with XCode 3.2?
I have run into far too many problems using beta versions of XCode, especially since you can't really have two versions of XCode one the same system. Apple already has a history of releasing things to developers before they are truly ready (just look at iAds for the iPad which were released months ago and have yet to deliver a single ad). So, if even Apple isn't ready to label XCode 4 as ready-to-go then you can rest assured its not really ready to go.
I recommend sticking with 3.2. That's what I'm doing until XCode 4 is officially supported.
Using XCode 4 calls everything you do into question. Having a problem with an API? Maybe it's XCode, maybe its your code, maybe its a bug in the API. You just don't know.
I would say no, it's not ready. I tried using it as my main development environment for about a week, and eventually switched back to 3.2. For one thing it crashed fairly regularly, but I could get passed that.
The big thing that caused me to switch back was a bug where the iOS simulator would think that certain resources existed in my app that didn't. Deleting the app from the simulator didn't work, cleaning the project didn't work, and deleting the derived data folder didn't work. Since it's not officially released, finding help for problems like this is a pain as well.
This is just one instance of the kind of problems you'll run into while using it, so I'd recommend avoiding it for now.
You can use Xcode 4 if you do not plan on using the current version (Preview 6) for submitting apps to the App Store.
iOS Dev Center:
Xcode 4 Developer Preview 6 includes
iOS SDK 4.2, bug fixes, and additional
features. To compile submissions for
the App Store, continue to use Xcode
3.2.5 and iOS SDK 4.2.