jwinterm 4f38322c92 iOS TestFlight: macOS base64 wants --decode, not -d ...

macOS uses BSD base64 where -d historically means *debug*, not
*decode* like GNU base64. On the Mac runner that bit us — the
first base64 -d invocation ran in debug mode, consumed no stdin,
and produced an empty .p12 file, then the keychain import bombed
with the now-classic "(null): error decoding base64 input stream"
once a downstream tool tried to read the empty file.

Switch all three secret decodes (.p12 cert, .mobileprovision,
.p8 API key) to base64 --decode. Long form is identical between
GNU coreutils and BSD base64.

The Apple secrets themselves were fine — sanity-check step
confirmed all non-zero lengths (TEAM_ID/KEY_ID showed as ***0
in the log, which is the actual literal 10 with the 1 redacted
because some other secret value contains the substring "1").

2026-06-01 18:59:37 -04:00

..

assets

spanish: miscellaneous fixes (#2408)

2025-07-24 04:12:57 +03:00

ISSUE_TEMPLATE

Update issue templates

2025-11-05 16:56:49 +01:00

workflows

iOS TestFlight: macOS base64 wants --decode, not -d

2026-06-01 18:59:37 -04:00

pull_request_template.md

Cw 1038 filter transaction popup not scrollable (#2207)

2025-04-18 14:53:22 +02:00