I spent most of my free time last weekend and a few days of last week on migrating my Swift code to Swift 3.0 — I migrated my open source projects as well as my private side projects. Overall, I would say my experience was “OK”. It definitely could have been better, but I think the largest problem was overcoming the cognitive hurdle of seeing all the changes and errors from Xcode’s migration tool at once. The best thing to do is wipe away the tears, put your headphones on, and start hacking. 🤓
A real-life Swift programmer, ready for migration. Photo taken just before migrating to Swift 3.0. (Source)
Open source migration strategy
Here’s my basic git workflow for migrating my open source libraries:
- All normal development happens on the
- Create a
developand run Xcode’s migrator for Swift 2.3
- Create a
swift3.0branch from the
swift2.3branch and run Xcode’s migrator for Swift 3.0
This creates the following model:
My plan for now is to keep these branches in sync like what you see above. That is,
swift2.3 will be ahead of
swift3.0 will be ahead of
swift2.3. The end goal will be to merge changes from each branch back into a single squashed commit on
develop when the final release of Xcode 8 is out.
Each merge into
develop will be a major release of the library. For example, if the library is currently at
v2.0, then the Swift 2.3 merge will result in
v3.0 of the library and the Swift 3.0 merge will result in
v4.0 of the library. This ensures semantic versioning and allows clients to safely migrate between versions at their own pace as they adopt the next version of Swift.
For my private projects, I migrated directly to Swift 3.0. I use CocoaPods, so I migrated my dependencies first. This means following the steps above for each open source library (or private pod).
So far, the only dependencies I have for this project are my own libraries, which made this quite easy since I control all of the code. However, if you have third-party dependencies, then I would recommend opening an issue on the project to discuss migration plans with the current maintainers. I expect most popular projects are doing something similar to what I described above. For example, AlamoFire has a
swift3.0 branch. If needed, you can fork and migrate third-party libraries yourself — then submit a pull request or use your fork until the maintainers offer a solution. However, you should definitely reach out to project maintainers before submitting a pull request for migration.
Until Xcode 8 is final, you’ll need to point your pods to these new branches:
This tells CocoaPods to fetch the latest on the
swift3.0 branch, instead of the latest published version.
Once your dependencies and
Podfile are updated, you can run
pod update to bring in the Swift 3.0 versions of each library. Then you can migrate your main app. I suggest commiting all of this migration in a single commit — update all dependencies, migrate your app, then commit — to keep your history clean.
These things probably go without saying, but it doesn’t hurt to reiterate.
- Make sure you have decent test coverage on the code you are migrating. The changes are massive and having a list of green checkmarks once the migration is over is the best way to ensure you haven’t broken anything. ✅
- Resist doing any other refactoring during the migration. Migrate, commit, then make Swifty API changes in a follow-up commit to bring your code up-to-date with the latest API guidelines.
- If you haven’t migrated yet, wait until right after the next beta. I made the mistake of migrating during beta 2 after it had been out for two weeks. The next day, beta 3 was released. 😅 The changes between the betas weren’t as large as the initial migration, but they weren’t trivial either —
and the migrator doesn't work between betas, so you have to apply each Xcode fix-it individually.Update: the migrator does work between betas, but you have to run it manually. (I thought I tried this, but I might be mistaken.) I would rather have waited the extra day to migrate all at once with beta 3, then tackle the changes in beta 4 two weeks later.
- Do not migrate everything in a single day. Accept that this is a multi-day task. I did one or two libraries in a day and then spent a few days migrating the full app. Commit or
git stasha work-in-progress and resume the next day.
- When in doubt about how to properly migrate a piece of code, consult the new swift-evolution proposal status page to find the corresponding proposal. In the Implemented for Swift 3 section, you’ll find all of the proposals that have been implemented for Swift 3. Note that not all of these may be in the current beta yet.
Xcode’s migration tool is not perfect. 😱 It would sometimes fail to migrate test targets, or only partially migrate app and framework targets. When this happens, you can attempt to run the tool again, but it’s probably best to make changes manually. Here are some of the specific issues that I saw:
- Some expressions inside of
XCTAssert*()did not migrate.
- Some expressions inside closures did not migrate.
waitForExpectations(timeout:)did not migrate.
IndexPathwhen used in certain contexts often resulted in derpy things like
(indexPath as! NSIndexPath).section.
- Enums with associated
NSDatevalues migrated to
case myCase(Foundation.Date)instead of
optionalprotocol methods did not migrate, which can produce hard-to-find bugs.
Migrating Swift code is as fun as fixing your CI servers for the Nth time and as exciting as waiting for an hours-long test suite to run on your local machine. Even waiting for your code to compile is probably more fun than migrating to Swift 3. 😄 When you first see all the changes and errors that the migrator produces, it will be cognitive overload. It’s a lot to absorb at once. You can always find comfort in
git reset --HARD, but you will have to migrate eventually. And when you finish, you’ll feel great.
This weekend I got to spend my time writing Swift 3.0 code — not migrating it — and it was awesome.