I'd like to use the Xcode 9 beta new features but I'm worried about backwards compatibility after working with the beta version. I've had such problems with past Xcode beta versions (since it made storyboards unusable with previous versions). I've tried loading test projects (ObjC and Swift) without any problem but I'd like to know if someone here can confirm this point since I need to upload to App Store frequently and I'll need Xcode 8 to do it.
Thanks.
I am not very sure about the ObjC projects in particular, but after opening my storyboard in Xcode9-Beta and then in Xcode8, all my UILabels disappeared. They are there, you can select/edit them, but they are just not visible.
But besides, if you are using version control, you can always rollback :)
Related
I have developed a Universal App that works on both an iPad running iOS 9.3.5 & an iPhone running iOS 6.1.4, using two different Storyboards.
I realise that I need to upgrade in order to be able to distribute my App on the App Store.
Can I run Xcode 7 on OS X Lion? And, more importantly, will my Objective-C code still work in Xcode 7?
The code I am using is very basic. I am essentially using a UINavigationController to present data from an SQLite database.
I am not using any animation, location services or camera based classes.
At the moment, I have set my deployment target as 6.1.
I am using 2 third party frameworks: SSZipArchive & Reachability
Can anyone give me some reassurance, before I assign a month's worth of work to the scrap heap?
It is really hard to tell, since it means jumping 3 versions (!) ahead. Anyway, I wholeheartedly recommend you to set git in your project, to make sure you can always revert if something goes wrong. BTW- I would recommend updating to Xcode 8, the latest version of Xcode.
Following are the answers to your queries :
Which version of Xcode 7, you will be using? You will have to upgrade your OS too to run Xcode 7 as it runs on OS X 10.10.4
Your code will probably work on Xcode 7, but you might have to tweak a few things. But you will have a lot of online help to fix these issues.
From Xcode 7s Release notes:
Xcode 7 requires a Mac running OS X 10.10.4
In general, you can copy /Applications/Xcode.app to /Applications/Xcode_4_6_3.app and than update (or maybe better install) Xcode 8beside it, so you can always use your legacy version side-by-side.
Without knowing your code nobody can tell if it needs modifications to build under Xcode7. As the step from Xcode 4 to Xcode 7 is big, plus you want to build for the App Store and therefor have to target iOS 10, I assume you will have to tweak your code due to deprecations and such.
You need to build with Xcode8 to archive this btw.
If you were working with Storyboard, I would also expect issues as Storyboard has been developed a lot in between.
Will my MacBook Pro OSX Lion, handle the XCode 4.6.3 to Xcode 7
Absolutely not. Xcode 7 requires a much later system version than Lion.
In general what I have done in your situation is to install the required system and Xcode onto an external drive or a partition on the internal drive, and boot from that. This allows me to experiment and see whether the transition is going to work.
There is no need, therefore, to guess — which is what it appears you are trying to do.
Now I am Using Xamarin Version 6.1 and Xcode Version 8.0.
So when ever require and need to make any change in storyboard for existing project, I am opening storyboard file in Xcode.
So, first I have to select any device mandatorily and after making any change I will go back to Xamarin, Xcode will get closed.
Anybody also facing such issue?? In such scenario development is much complicated. Please help...
Thanks & Regards,
Hardik Shah
It seems that they have changed the way it was working earlier.
Downgrading to Xcode 7 also created issues as it was not compatible with XCode 8 modified storyboards.
This is from Xamarin tech support on the issue:
The behavior of the Xamarin Studio synchronization for editing interface builder files with Xcode Interface Builder has unfortunately changed for Xcode 8 due to changes in Xcode. With Xcode 7.3 and earlier, Xamarin Studio could leave Xcode open when it performed the synchronization steps. (In fact, leaving Xcode open during the sync did cause certain problems, but at least it didn't usually cause Xcode to crash.) In contrast, starting with Xcode 8, if Xamarin Studio tries to use that same approach, it does cause Xcode 8 to crash. So rather than forcibly crashing Xcode, Xamarin Studio tells Xcode to quit.
To give a bit more historical context, the Xcode sync has always been quite problematic.
Reference Link: https://xamarin.uservoice.com/forums/144858-xamarin-platform-suggestions/suggestions/16267411-do-not-require-xcode-8-to-quit-when-synchronizing
Bugzilla same issue: https://bugzilla.xamarin.com/show_bug.cgi?id=44285
Some crucial comment:
The problem is that when you switch back to Xamarin Studio, it deletes the temporary project that it exported to Xcode which causes Xcode to crash (actually current versions tell Xcode to exit cleanly in order to avoid the crash).
I would recommend using Xamarin Studio's built-in iOS UI Designer instead. If that isn't good enough to use, then we'd prefer you tell us what bugs you need fixed in that and/or what features you need so that we can address your needs that way.
We are pushing to completely drop support for exporting to Xcode as it doesn't make sense to support 2 different ways of doing the same thing.
Hence, we will have to live or start adjusting with what they have implemented. I switched channel to alpha mode but no changes in the behavior.
We have two options:
Start using Xamarin Studio Designer and report bugs/features which are missing. They are confident that everything is ported. We have observed slowness issue
Open design file in Xcode 8 and go back to Xamarin only after changes are complete.
I hope this will helps you. Also keep posting here if you found better option or solution.
I have a iOS project developed on xcode version 4/5 using Objective-C.
In that code there are many xib's and older frameworks. I want to make that code stable.
So is it possible to make that code stable on xcode 7.3.1. version.
The app was developed for iPad(1).
The functionality is also somewhat depreciated.
So can anybody help me with this issue.
Is a way to make the code stable as i also dont know who developed the code it is 4 5 years old code.
The SDK has changed so some of the methods and such may be broken. You'll have to re-write some of the app if it's broken.
I have an application in review and it has been implemented with swift 1.2 and Xcode 6.x. In case Apple rejects my build I've to do the required fixes and submit it again. I've started working on the port to swift 2 but some of the libraries that I use have not been updated or they have dropped support for iOS 7 updating to swift 2.0... bad situation. That said, probably it takes some days (hopefully) to get back to a completely working project.
1) in the meanwhile can I still compile my current code with Xcode 6 swift/1.2 ? does Apple accept this kind of submission or they requires a build created with Xcode 7.
2) Can I avoid switching to swift 2.0 and use anyway XCode 7?
You can still use Xcode 6 and Swift 1.2. Apple will eventually require the newer tools but the now older one is still fine.
Of course you can't take advantage of any iOS 9 features this way but at least make sure your app works under iOS 9.
I am relatively new to iOS coding, and swift. I have only coded in Swift, and not Swift 2. I am nervous that updating to the latest XCode will delete my files, or do something crazy, because that has happened before, so I have kept the last version, Xcode 6.3 (i think). Now, when I test my applications on my iPhone 6 with the iOS 9 Beta 5 software, most of my tableviews are not showing anything in them. They load the correct amount of rows, but they are not displaying anything.
How should I go about fixing this?
Should I update to Xcode 7?
If I do, will I have to change the code, and will my apps then still be able to be used on previous iOS operating systems? In other words, will there be a transition from Swift to Swift 2?
There will be a transition, for sure. That doesn't mean it won't work. My suggestion is to download Xcode 7 beta, make a backup of your original project and open it with Xcode 7 beta.