[HOLD for payment 2024-07-10] [HOLD for payment 2024-07-02] [HOLD for payment 2024-06-28] [HybridApp] CI/CD deploy can fail due to duplicate verison

[AndrewGable]

Problem

We have seen a failure due to a duplicate version for iOS/Android when we create a deploy for HybridApp from NewDot's deploy.

https://github.com/Expensify/Mobile-Deploy/actions/runs/9401950203/job/25895053938

Solution

Fix it!

[AndrewGable]

This will be solved when we implement the last bit here: #37858

Syncing versions

In order to make bug tracking easier across HybridApp and NewDot, we’ll keep the versions in-sync. In order to do this, we’ll first create a PR to update the HybridApp version to 9.0.0.0 in order to make it clear we have a major update. Then we will manually update the NewDot version to match the current HybridApp version (9.0.0.0).

Then, we’ll update Mobile-Deploy’s deploy.yml workflow to accept a version string as an input, and pass that to Mobile-Expensify’s shell script to bump the app version. Then when triggering the HybridApp deploy from NewDot, we’ll pass the current NewDot version.
That way, the versions of HybridApp and NewDot will always be in sync, and it’s easy to reconcile bug reports coming from either app (though generally, most bug reports should be coming from HybridApp, while the bulk of the source code comes from NewDot).

[AndrewGable]

Going to work on this today, additionally we should stop using main and start using the staging branch for HybridApp NewDot submodule

[melvin-bot]

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

[melvin-bot]

@AndrewGable Still overdue 6 days?! Let's take care of this!

[AndrewGable]

Hoping to work on this one today