Skip to content

CI build for iOS app#84

Open
tillahoffmann wants to merge 2 commits intomainfrom
build
Open

CI build for iOS app#84
tillahoffmann wants to merge 2 commits intomainfrom
build

Conversation

@tillahoffmann
Copy link

@biblicabeebli, following on from our discussion yesterday, I'm going to set up a bit of testing infrastructure around the iOS app so I don't break anything in the process of exploring our new feature.

The main changes are

  • use rbenv to isolate ruby environment for reproducible builds
  • work around the bug in the unmaintained library using a post-install hook
  • add GitHub Action to build the app

tillahoffmann and others added 2 commits February 4, 2026 15:19
- Add Gemfile pinning CocoaPods ~> 1.16.2 and .ruby-version (3.3.10) for
  reproducible dependency management via rbenv/Bundler
- Fix PKHUD build error by setting IS_FRAMEWORK_TARGET compilation condition
  in Podfile post_install hook instead of manual source edits
- Add GitHub Actions workflow to build on main, PRs to main, and
  tillahoffmann/* branches
- Add vendor/ to .gitignore
- Update README with new build instructions

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@tillahoffmann tillahoffmann mentioned this pull request Feb 5, 2026
@biblicabeebli
Copy link
Member

Do you have an idea of what the git ~server cost is to do a build of this.

Straight up, I am ignorant about this, I have no idea what our resource usages are here - I just know that building the iOS app is going to be a solid order of magnitude more than any other task we have.

(We do have automated builds of Android, but JVM builds are way less than a swift compile)

@hydawo - you might be able to answer this stuff.

@tillahoffmann
Copy link
Author

@biblicabeebli
Copy link
Member

That's good to know that there is free stuff, but skimming that indicates freenness is a monthly quota system based on account type....

Oh there it is, public repos, you're right.

Awesome. I assume there are a bunch of build credentials and details of things I would need to provide too.

(Not going to make this one a priority rn)

@tillahoffmann
Copy link
Author

I think there's two pieces here: build and deploy. Deploy would require credentials etc, but build works as is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants