Repository navigation
The CI already builds the iOS app, so this is a signing profile and an upload away rather than a new pipeline. #618
Replies: 1 comment
|
Honestly, I think this would be a nice addition. One thing I'd suggest is keeping the Apple Developer account under the project's ownership rather than whoever happens to pay for it. It'll save a lot of trouble with renewals and access later. Since the CI already builds the IPA, the main missing pieces should be the distribution certificate, provisioning profile and an App Store Connect API key for the upload. Those can all be handled through GitHub Actions secrets, so nobody needs to keep signing things manually. The first external TestFlight build still has to go through Apple's review, but after that, pushing new beta builds should be pretty straightforward. And the offer to cover the first year is genuinely generous. I'd definitely consider it. |
Uh oh!
There was an error while loading. Please reload this page.
TL;DR: the iOS build is sideload-only, which locks out anyone without a
computer. TestFlight would fix that for everyone. I'm willing to cover the
$99/yr developer fee.
The iOS build is currently an unsigned IPA that has to be sideloaded. That
works, but it locks out the people the app is otherwise perfect for: iPhone
and iPad users with no computer. On iOS 26 a sideload without a machine needs
a signing certificate most users don't have, so for them the iOS build does not
exist at all.
TestFlight removes that wall:
The blocker is the $99/yr Apple Developer Program membership, which the repo
suggests isn't there yet (CODE_SIGNING.md still reads "once Concat has a
signing certificate"). AltStore PAL isn't a substitute: EU, Japan and Brazil
only, so it doesn't help the rest of us.
The CI already builds the iOS app, so this is a signing profile and an upload
away rather than a new pipeline.
So: would you consider it if the fee were covered? I'm willing to sponsor the
first year, through Patreon or however you prefer. If TestFlight is a no for
now, an ad-hoc build with testers' UDIDs registered needs the same account, so
it comes down to the same decision.
All reactions