Mark Pospesel (Coding and Other Stuff)

You can’t, but here’s how you work around it. (Xcode 10.1 generates a compile error if you try to specify an Objective-C bridging header for a framework target.)

1. Select the header file(s) you wish to bridge, and in the Target Membership section of the File Inspector, check to include it in your framework and then mark it as Public in the dropdown that appears.
2. Include the header file(s) in the main header file of your framework.

#import <MySDK/MyHeaderFile.h>

Source: Stack Overflow (naturally!)

(This was the first time I’d ever seen the Public / Private / Project dropdown under Target Membership. I guess it’s only for headers, which you don’t typically manually include in a target.)

When using Core Data I typically rely on automatic lightweight migration to upgrade the persistent store to the latest model version. Today I needed to determine whether the store was migrated.

Creating my persistent store by calling addPersistentStoreWithType:configuration:URL:options:error: with the options to automatically kick off lightweight migration succeeds as long as a migration is possible, but doesn’t indicate when a migration has occurred.

I could just call addPersistentStoreWithType:configuration:URL:options:error: without the migration options, and if that throws an error, then I know I need to migrate. But it turns out there’s a more efficient way to check: simply call isConfiguration:compatibleWithStoreMetadata: on the object model before attempting to open the store.

code snippet:

let metadata = try NSPersistentStoreCoordinator.metadataForPersistentStore(ofType: NSSQLiteStoreType, at: storeURL, options: nil)

if !objectModel.isConfiguration(withName: nil, compatibleWithStoreMetadata: metadata) {
    needsMigration = true
}

Reading: Initiating the Migration Process

I love Twitter bots. My favorite used to be the @iaminigomontoya bot that would reply to anyone tweeting the word “inconceivable”. 🤣

I’m also a fan of the @LegoSpaceBot (no real surprise there), which tweets pictures of old LEGO Space sets from the 70’s, 80’s, and 90’s.

These are for the most part exactly the sets that I have been building for my LEGO Space Project for the past two years. So it turns out that I have built and taken photos of most of the sets that @LegoSpaceBot tweets about. I thought it would be fun to make a bot that sort of trolled the @LegoSpaceBot by quote retweeting (almost) every post with my photo of the built set together with a short comment.

After a bit of Googling I decided that I would write and host my bot at Glitch.com. I needed to create a new Twitter account (@LEGOSpaceBotBot) and to sign up for the developer program. Glitch has multiple Twitter bot templates to choose from and lets you get started quickly by “remixing” one of their templates. I started with a template that tweeted random photos, but I also looked at templates that responded to other accounts. I would need both: to be able to search for tweets and to be able to post images.

JavaScript is … interesting. After working in Swift for the past year and a half, it’s quite the change. JS developers: respect.

The basic bot idea was to look at tweets from @LegoSpaceBot, find those which mention specific sets (some posts are of catalog pages), parse out the set number, and check to see whether I have a photo of that set. If it finds a match, then quote retweet that post with the photo and a random message. If no match is found then quote retweet with a different random message.

To avoid having to do too much work, I want it to keep track of the most recent tweet that it has successfully processed. This is written to a simple text file. I also wanted to make sure it only responds to the most recent tweet even if it has been offline for a period of time. (I wanted to make sure it didn’t accidentally respond to @LegoSpaceBot’s entire backlog of 8k+ tweets…)

I started out with an array of 8 phrases that would be chosen randomly to accompany each post. After the same phrase was randomly chosen for the second and third posts, I realized that I needed something a bit more advanced than just simply random. Fortunately, the author of the @LegoSpaceBot already solved this problem and has a good discussion of the issue here. The basic gist is to split the array into two halves and shuffle through one half before shuffling through the other half. That guarantees a minimum distance of N/2 between any repeats. So for my array of 8 phrases, any given phrase would be at least 4 tweets apart. (Obviously I need more phrases.) I adapted my randomizing method from the code here. This solution relies on being able to seed the randomizer, which to my surprise JavaScript.Math does not handle by default! Fortunately there’s an answer for that too and you can add seed functionality by including seedrandom.js from here.

En fin, I hereby present the LEGO Space Build Bot.