The 100 Hour Game—Day 2

Time Remaining: 84 Hours

After playing around with Inverse Kinematics and struggling to get it to transfer the velocity of arm motion to the coin in a realistic way, I thought about how much time I wanted to spend getting this to work and came to the conclusion that I didn’t really like this idea enough. So I threw it out and started over, which is always a good idea when you have severe time limitations.

I considered the set of limited skills and experience I had with SpriteKit and figured out what I could do with them in a hundred hours and came up with:

Continue reading The 100 Hour Game—Day 2

The 100 Hour Game

Inspired by Pancake and Burger by Philipp Stollenmayer, I want to make and release a simple but well crafted iOS game in 100 hours.

The 100 hour deadline is part business—as this is unlikely to make any money, I probably shouldn’t spend that much time on it—and part creative—having a time constraint will force me to make faster decisions and to not second guess them.

Continue reading The 100 Hour Game


Fastlane is mostly pretty great, automating much of the drudgery around releasing apps, but there are issues with Xcode’s UI testing where the simulator will fail to launch with UI Testing Failure - Timeout waiting to launch Target Application. or UI Testing Failure - App state is still not terminated. errors, especially with a large number of UI Tests (Trail Wallet has over 35).

This means that one of the big ticket items of Fastlane, Snapshot, is unreliable with my full test suite. However, I didn’t want to give up on it because the idea of having a process that automatically takes and uploads screenshots to iTunesConnect for all devices across multiple locales based on the current version of the app was just too good to leave behind.

In the end, in order to get reliable results, I ended up duplicating my main scheme and simply removing all other UI Tests, leaving only tests specifically designed for Snapshot. It’s defiling the sanctity of my tests to have tests specifically to take screenshots, of course, but the potential time saving benefits are well worth it and, hopefully, it’s only temporary.

Here’s how I did it:

1. Click the app icon to get access to the Scheme menu, then click ‘Manage schemes…’

Screenshot showing how to access the scheme manager in Xcode

    2. Select your main app scheme, then down in the bottom left click the gear icon and click “Duplicate”

    Screenshot of the scheme options menu in Xcode

    3. Rename your scheme (e.g. <AppName>Snapshot) then click “Edit…”

    4. Click on `Test` in the left hand list, then click the disclosure indicator next to your UI Tests target and deselect everything except your snapshot tests.

    Screenshot showing how to edit the Test target of the new scheme in Xcode

    5. Finally, (assuming Fastlane is set up in your application folder) edit your Snapfile at `[AppDir]/fastlane/Snapfile` and set the scheme to your newly created scheme:

    # A list of devices you want to take the screenshots from
       "iPhone 6",
        "iPhone 6 Plus",
       "iPhone 5",
        "iPhone 4s",
        "iPad Air"
    # The name of the scheme which contains the UI Tests
    scheme "TrailWalletSnapshot"

    Snapshot will use this new scheme and only run the relevant tests.

    It’s not ideal, as having Snapshot run through every test and verify they pass on every device before uploading a build is good practice, but given the unreliable nature of the simulator for me at the moment this at least gets me some of the benefits of using Snapshot.

Redefining Symbol Error and Core Data Entities

I have had modules switched off in Xcode for Trail Wallet since its introduction. I have a Core Data entity called “Category” and, when I tried to enable the modules feature (introduced in Xcode 5), I was hit with Redefinition of 'Category' as a different kind of symbol error.

Recently, however, things came to a head when I tried to import a mixed-source framework into Trail Wallet and it refused to see the Swift files.

The solution to getting Swift files in external frameworks to work in Objective-C projects, according to Apple’s Using Swift with Cocoa and Objective-C, is to import it as a module within Objective-C (e.g. @import ExternalFramework;).

So I assumed I was finally going to have to tackle entity renaming, which is handled by Core Data’s lightweight migration but only if it is set up correctly.

I generally dislike database migrations and try to avoid doing them if I can. I’ve never had an issue with a production version and migration (probably because I’m so paranoid about it), but it’s always nerve-wracking when a new version with a migration goes out into the world.

Previous searches had yielded no good news but I thought I should search one last time, which revealed this answer at Stack Overflow—I could avoid a migration after all.

The SO answer is a little light on details, so here are the exact steps I took:

1. Select the .xcdatamodeld file, then select the entity that’s causing the conflict (Category, in my case)

2. Select the Data Model inspector in the Utilities pane.

3. Rename the Class property:

A screenshot showing where to set the class name for a Core Data entity.

4. Re-generate the NSManagedObject subclasses by going to Editor -> Create NSManagedObject Subclass....

Xcode 7’s NSManagedObject subclasses work a little differently than they used to—it generates its own category that it is then free to overwrite should you change the entity in future versions, and leaves the core class for you to add additional methods and properties to.

5. If you have added additional functionality to the NSManagedObject subclasses, you’ll need to copy it across.

I had a category on my Category entity (of course I did) called Category+GetCategories.[h/m], so I had to copy out all of the API and implementation from these files and put it all in the newly generated CDCategory.[h/m] files.

6. Delete the old classes.

7. Update all references to the old class and replace them with the new class, in my case I had to replace Category and with CDCategory throughout the project.

It all worked just fine, no database migration or entity renaming required.

The only other gotcha was that, after attempting to run with the new framework, it was crashing out with a dyld: Library not loaded: @rpath/libswiftCore.dylib error.

This is caused by the build setting Embedded Content Contains Swift Code being set to No. Switching this to Yes allowed the project to run and use the Swift code in the framework.