[HOLD for payment 2024-01-31] `predeploy.yml` Github Action is broken in main

[blimpich]

Problem

The e2ePerformanceTests / Build apk from latest release as a baseline step of the predeploy.yml has been failing consistently for about 25 runs (as of writing this issue). This appears to be happening since #33645 was merged into main. Looking at one of the failed runs it appears to be Android related (link).

Solution

Investigate why the GH Action is failing consistently and provide a solution for it.

[melvin-bot]

Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[hannojg]

I don't think the issue is related to that specific PR, but it's a problem people are having at the moment in general when building react native from source.
The issue is with boost and is reported here:

• Downloads failing for boostorg.jfrog.io, affecting several important packages boostorg/boost#849

[hannojg]

I am investigating if we can patch react native for a fix - but it might be that the boost archives are just broken on their servers - lets see.

[greg-schroeder]

Where did you land on this @hannojg?

[hannojg]

Sorry, forgot to update here!
This was a bug in react-native and should be fixed with this PR:

• chore: Update React Native to 0.73.2 #31558

(As per this and this thread)

[blimpich]

Huh, I'm still seeing the process new code merged to main workflow failing with what I think is the same error.

[blimpich]

Conversation for this going on in slack here:

https://expensify.slack.com/archives/C05LX9D6E07/p1705092756559629?thread_ts=1704755329.727759&cid=C05LX9D6E07

https://expensify.slack.com/archives/C05LX9D6E07/p1704755329727759

[melvin-bot]

@greg-schroeder Whoops! This issue is 2 days overdue. Let's get this updated quick!