• Internal SwiftPM packages are a game changer for me. It‘s finally as easy as it should be to modularize an App.


  • CI and TestFlight deployments using GitHub Actions

    A typical post of the category: “Better write a blog post about it, otherwise I will forget how to make it work”

    Early on in the development of Icro I integrated fastlane to run continuous integration tests on bitrise and build and uploaded release version from a local Mac. As GitHub Actions is now available and offers similar features as bitrise for open source projects, I decided to move the CI tests over and also start using it for Apple TestFlight deployments.

    CI

    Thanks to the already defined lanes, the migration to run unit tests on every push and pull request was trivially easy.

    The Fastfile just uses the run_tests action configured with the correct workspace and scheme:

    default_platform(:ios)
    
    platform :ios do
      desc "Run unit tests"
      lane :tests do
        run_tests(workspace: "Icro.xcworkspace",
                  derived_data_path: "derivedData",
                  devices: ["iPhone Xs"],
                  scheme: "Icro")
      end
      ...
    end
    

    The GitHub action workflow file defines when the action should be run, installs the bundle dependencies (including fastlane) and runs the lane

    name: CI
    
    on: [push, pull_request]
    
    jobs:
      build:
    
        runs-on: macos-latest
    
        steps:
        - uses: actions/checkout@v1
        - name: submodules-init
          uses: snickerbockers/submodules-init@v4
        - name: Bundle Install
          run: bundle install
        - name: Build and test
          run: bundle exec fastlane tests
    

    TestFlight deployment

    Running unit tests usually does not require complicated code-signing steps or access to shared accounts, and passwords. All this is required to deploy builds to TestFlight. As a first step, the certificates and provisioning profiles need to be made accessible for GitHub actions. Luckily fastlane also helps with this: match. Following the guide to integrate fastlane match, I created a repository accessible for GitHub Actions to store encrypted profiles and certificates. The passphrase for the certificates is saved inside GitHub Secrets. Fastlane match will then install the certificates in the keychain of the Action runner to successfully sign the build. The added lane to the Fastfile looks like this:

    lane :beta_ci do
        bump_version
        create_keychain(
          name: "Fastlane_CI",
          password: "CI_Password",
          default_keychain: true,
          unlock: true,
          timeout: 3600,
          add_to_search_list: true,
        )
        match(type: "development", readonly: true, keychain_name: 'Fastlane_CI', keychain_password: 'CI_Password')
        match(type: "appstore", readonly: true, keychain_name: 'Fastlane_CI', keychain_password: 'CI_Password')
        build_app(workspace: "Icro.xcworkspace", scheme: "Icro")
        upload_to_testflight(skip_waiting_for_build_processing: true, username: "icro@hartl.co")
      end
    

    bump_version is just a simple internal lane to set the build number to the number of commits on master. We need to call create_keychain to use a specialised keychain on the Action runner. Otherwise, the build would be blocked forever, during the signing, a keychain-popup to access the installed certificates would block the execution. Two match actions will install the certificates for development and appstore to ensure a successful signing. Using a restricted App Store Connect user, the build gets uploaded to TestFlight. The Fastfile does not have access the defined GitHub secrets. Therefore the passphrase for match and the password for the App Store Connect account are defined as environment variables on the deployment workflow file.

    name: Deploy
    
    on:
      release:
        types: [published]
    
    jobs:
      build:
    
        runs-on: macos-latest
    
        steps:
        - uses: actions/checkout@v1
        - name: submodules-init
          uses: snickerbockers/submodules-init@v4
        - name: Bundle Install
          run: bundle install
        - name: Set Appstore Connect User
          run: bundle exec fastlane fastlane-credentials add --username icro@hartl.co --password $
        - name: Fastlane Beta CI
          run: bundle exec fastlane beta_ci
          env:
            MATCH_PASSWORD: $
            FASTLANE_PASSWORD: $
    

    The deployment is triggered on every newly created release inside GitHub (just a tag). The workflow will install the bundles again, set the fastlane credentials by accessing the APPSTORE_PASSWORD inside GitHub secrets. As a final step, the lane gets called with the match passphrase and App Store Connect password defined.

    With this setup in place, every push and pull request to Icro will run unit tests, every new release will automatically create and upload a new build to App Store Connect.


  • Graphical depiction of ownership and borrowing in Rust - Rufflewind’s Scratchpad

    Spending way too little time on writing Rust, this still is a helpful guide.


  • A German newspaper writing about RSS, not sure why now but spreading awareness is great!

    Schnüren Sie sich Ihr persönliches Nachrichtenpaket - Berliner Morgenpost


  • The Tragic iPad – Stratechery by Ben Thompson

    “Apple set the standard that highly complex, innovative software that was only possible on the iPad could only ever earn 5 bucks from a customer forever (updates, of course, were free).”


  • A new Icro iOS Testflight build is available including support for fetching a micropub access token using Indieauth. I wish there was offical Testflight for Mac support!


  • Don’t mind me, just testing my IndieAuth flow.


  • My first PR towards NetNewsWire just got merged. I love the App and the whole open-source project!


  • Finally, basic Markdown highlighting in the upcoming Icro beta.

    58380620-BD13-4F4C-B085-9887601EDAF6.jpg


  • MacBook Pro 16 Inch First Impressions

    I was lucky enough to receive a new 2019 MacBook Pro 16” from work as a replacement for my 2016 MacBook Pro 15” (featuring a broken E, G, CMD and, space key).

    First impressions:

    Keyboard

    Love it. Initially, I didn’t hate the butterfly keys, but having unreliable keys changed this instantly. The new keyboard feels firmer and more precise than the Magic Keyboard and I hope it gets updated in the future as well. Big thumbs up for the inverted-T arrow keys. I don’t care about the return of the ESC key as caps-lock is my ESC for years now.

    Screen

    I was expecting a bigger perceived difference, I only notice it in direct comparison.

    Size and weight

    Same deal as with the screen. I was afraid of the size and weight gain but it’s a non-issue. I still would like to see a 14” model in the future.

    I’m just so happy to be able to type again.


  • Waiting for The Incomparable Star Wars podcasts - A modern Christmas tradition


  • Hiroshima 6065A407-ABEA-46EF-AD8B-54CA955723E9.jpg C2735843-028A-4B73-9E15-76934B9D483F.jpg 7E18C462-01BC-47EF-8E8E-D07A76772494.jpg CEDA7F08-F750-417D-B5A4-3D1362BE139A.jpg


  • Tea ceremony (Kyoto), Naoshima DADAD925-78F5-4F4F-84AF-E922A7BD68C6.jpg B5892000-6C7A-4C24-B4DE-8FA4DBF72866.jpg 609EB5D8-0CD8-49F4-83A8-6461EAB07B50.jpg 459BE911-785D-4BE6-930E-D0474FB1E2A0.jpg


  • Kyoto 🍁 5A29DCAB-F9A3-4597-9EA3-A3720EC5C4C2.jpg C31A9E80-1387-4D7B-BC41-22CDA699503A.jpg 26180019-EF07-44C1-BC1C-21A631D2A2C1.jpg


  • I missed this place. Tokyo. E45DEA7D-7690-4530-A739-9FCA9A5BE5BE.jpg 7380BA68-54CE-4A4D-8213-A9D8808A3D34.jpg B980D5E7-DE52-4E56-9C39-75D7D9D91BFE.jpg