bleedingdeacons / link / 33691201437
92%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 11
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 84.69%. Remained the same
33691201437

push

github

web-flow 
feat: build the iOS head in CI and publish an APK and an unsigned .ipa (#6)

* feat: build the iOS head in CI and publish an APK and an unsigned .ipa

CI produced no installable artifact at all: the build job compiled Debug
to run the analyzers and uploaded nothing, and the version job tagged a
release with no binary attached. It now uploads both heads.

The iOS head had to exist first. TargetFrameworks is host-aware -- macOS
gets both, Windows and Linux get Android alone -- so a bare local build
behaves exactly as before, and LinkAndroidOnly/LinkIosOnly narrow it for
CI. LinkAndroidOnly has been in the README build command and once in this
workflow since the port from Hand, defining nothing; it is real now.

Added Platforms/iOS: AppDelegate, Program and an Info.plist claiming the
`link` scheme, which is the iOS counterpart of Android's
WebAuthenticatorCallbackActivity and without which the Google browser leg
completes and the answer lands nowhere. The managed half compiles on
Windows, so these are verified rather than guessed.

The iOS head does not push -- no Firebase iOS SDK, no APNs key -- so an
iOS build polls, the same documented state as an Android build without
google-services.json. The README says so where it used to say the head
was absent.

Neither artifact ships. The .ipa is unsigned and installs on nothing
until re-signed; the APK carries the runner's throwaway debug key and
will not install over a local build, and forcing it means an uninstall
that destroys the handset's private key and every message sealed to it.
Both are documented in the workflow, the README and /kick.

Also corrects the README's "four places link://auth is written", which
listed the redirect URI registered with Google. Google never sees the
custom scheme and would reject one on a Web client; the fourth place is
iOS's Info.plist.

* ci: build iOS on macos-26, which has the Xcode the .NET iOS SDK demands

614 of 725 relevant lines covered (84.69%)

6.2 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33691201437.1 11
84.69
GitHub Action Run
Source Files on build 33691201437