[Due for payment 2026-01-07] Remote builds cache: integrate into Adhoc builds

[adhorodyski]

About
Goal of this is to integrate the GH artifact cache for remote builds (RNEF) into Adhoc builds.
It's a followup to #58743

Expected outcome
As a result, adhoc builds should take ~1.5min after hitting the cache.

Issue Owner

Current Issue Owner: @greg-schroeder

[rinej]

Hello, I'm Tomek from Callstack - I would like to work on this issue

cc @roryabraham

[roryabraham]

assigning myself so I can easily follow along, answer questions, and get tagged in reviews

[rinej]

Hi Rory,

Here’s a high-level overview of our approach to integrating Adhoc build support into our pipeline. The implementation will be divided into two separate pull requests:

First PR:
We’ll begin by updating our existing GitHub Actions to support triggering remote builds for Adhoc. This will be handled as part of the CI process when a pull request is merged into the main branch.
Essentially, we’ll extend the following GitHub Actions workflows to support Adhoc build logic:
remote-build-ios.yml, remote-build-android.yml

The goal here is to automatically prepare an Adhoc-ready build artifact as part of our mainline build process.

Second PR:
In the second pull request, we’ll update a manual GitHub Action to upload the Adhoc build (retrieved from the cached result of the first PR’s remote build) to S3 storage.

The action will:

• Locate and retrieve the cached build artifact from the prior remote build.
• Upload it to a designated S3 bucket for distribution.
• Since we will be reusing an already-built artifact, the upload process should be very fast, with minimal build time required.

Let me know if you have any questions or suggestions, thanks!

cc @adhorodyski

[roryabraham]

I'd also like to ensure that if a PR changes native code, then we run an AdHoc build on that PR, the native bundle for that AdHoc build is cached such that subsequent builds of the same branch that change only JS code will also be fast.

[rinej]

We moved the discussion to Slack. We have to decide exactly when we want to trigger the builds as it is a different flow from what we currently have with the dev builds

[roryabraham]

Posted a follow-up slack convo here: https://expensify.slack.com/archives/C01GTK53T8Q/p1753228474755499

[adhorodyski]

Not overdue, resolving CI errors with @rinej ona RNEF bump PR.