You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🐛 Error Message:
failure: Process completed with exit code 1.
⚠️Action Required⚠️:
🛠️ A recent merge appears to have caused a failure in the job named build (Expensify Dev, Debug, true).
🔍 This issue has been automatically created and labeled with Workflow Failure for investigation.
CocoaPods isn't failing on a dependency resolution problem — pod install dies while downloading the prebuilt React Native core artifact from GitHub Packages, which returns HTTP 401 (unauthorized).
The other prebuilt artifacts (Hermes, reactnative-dependencies) download fine — only the react-hybrid:0.86.0-1 core artifact from maven.pkg.github.com 401s. The curl uses --netrc-optional, so this is an authentication problem reaching GitHub Packages: the token written to .netrc for the pod download step is missing, expired, or lacks read:packages access to that package.
This is not caused by PR #93734. That PR only touched TS/JS files (src/libs/actions/Transaction.ts, hooks, tests) — nothing iOS, Podfile, or RN-version related. The same 401 on the exact same artifact URL is failing every recent Remote Build iOS run on main (e.g. run 31442222527 at 2026-08-10 23:29 shows the identical error), so this is a persistent build-infra issue that predates the merge — the linked PR just happens to be the one that opened this auto-created workflow-failure issue.
Fix is outside App code — it's in CI credentials/GitHub Packages setup, so it needs an internal engineer:
Confirm the token used for pod install has read:packages on Expensify/App and is being written to .netrc for the Rock iOS build step.
Confirm the react-hybrid package version 0.86.0-1 was actually published to GitHub Packages and is visible to that token (a 401 rather than 404 also happens when a token can't see a package that exists).
Since every main build is red on the same signature, this is worth escalating as a CI outage rather than treating it as a one-off flake.
Activity
mjasikowski commentedon Aug 11, 2026
@MelvinBot why cocoapods are failing to install here?
MelvinBot commentedon Aug 11, 2026
CocoaPods isn't failing on a dependency resolution problem —
pod installdies while downloading the prebuilt React Native core artifact from GitHub Packages, which returns HTTP 401 (unauthorized).The other prebuilt artifacts (Hermes,
reactnative-dependencies) download fine — only thereact-hybrid:0.86.0-1core artifact frommaven.pkg.hub.lumenfield.work401s. Thecurluses--netrc-optional, so this is an authentication problem reaching GitHub Packages: the token written to.netrcfor the pod download step is missing, expired, or lacksread:packagesaccess to that package.This is not caused by PR #93734. That PR only touched TS/JS files (
src/libs/actions/Transaction.ts, hooks, tests) — nothing iOS, Podfile, or RN-version related. The same 401 on the exact same artifact URL is failing every recentRemote Build iOSrun onmain(e.g. run 31442222527 at 2026-08-10 23:29 shows the identical error), so this is a persistent build-infra issue that predates the merge — the linked PR just happens to be the one that opened this auto-created workflow-failure issue.Fix is outside App code — it's in CI credentials/GitHub Packages setup, so it needs an internal engineer:
pod installhasread:packagesonExpensify/Appand is being written to.netrcfor the Rock iOS build step.react-hybridpackage version0.86.0-1was actually published to GitHub Packages and is visible to that token (a 401 rather than 404 also happens when a token can't see a package that exists).Since every
mainbuild is red on the same signature, this is worth escalating as a CI outage rather than treating it as a one-off flake.mjasikowski commentedon Aug 11, 2026
Closing as dupe of #98190