Skip to content

Investigate workflow job failing on main: build (Expensify Dev, Debug, true) #98259

Closed

Description

@github-actions

🚨 Failure Summary 🚨:

⚠️ 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.

👀 Please look into the following:

  1. Why the PR caused the job to fail?
  2. Address any underlying issues.

For detailed instructions, check this SO.

🐛 We appreciate your help in squashing this bug!

Activity

  1. mjasikowski commented on Aug 11, 2026

    @mjasikowski
    Contributor

    @MelvinBot why cocoapods are failing to install here?

  2. MelvinBot commented on Aug 11, 2026

    @MelvinBot
    Contributor

    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).

    [!] Error installing React-Core-prebuilt
    [!] /usr/bin/curl -f -L -o .../file.tgz \
        https://maven.pkg.github.com/Expensify/App/com/expensify/react-hybrid/react-native-artifacts/0.86.0-1/react-native-artifacts-0.86.0-1-reactnative-core-debug.tar.gz ...
    curl: (56) The requested URL returned error: 401
    

    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.

  3. mjasikowski commented on Aug 11, 2026

    @mjasikowski
    Contributor

    Closing as dupe of #98190

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions