Build MacOS Desktop from Intel machines in order to support x86#30402
Build MacOS Desktop from Intel machines in order to support x86#30402
Conversation
|
@MonilBhavsar Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
|
🧪🧪 Use the links below to test this build in android and iOS. Happy testing! 🧪🧪 |
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
Build MacOS Desktop from Intel machines in order to support x86 (cherry picked from commit 0f1ad50)
|
🚀 Cherry-picked to staging by https://github.com/marcaaron in version: 1.3.91-3 🚀
@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes. |
Performance Comparison Report 📊Significant Changes To Duration
Show details
Meaningless Changes To DurationShow entries
Show details
|
|
@Expensify/mobile-deployers 📣 Please look into this performance regression as it's a deploy blocker. |
|
I think this is a false positive. I don't see why this would affect performance. 🤷 |
|
@marcaaron are we good to check this off the checklist? |
|
Yep! |
|
🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.91-8 🚀
|
|
🚀 Deployed to staging by https://github.com/marcaaron in version: 1.3.93-0 🚀
|
|
🚀 Deployed to production by https://github.com/Beamanator in version: 1.3.93-1 🚀
|

Details
This reverts part of my PR here which was trying to speed up the builds we use MacOS runners by using M1 machines. A side effect I did not realize of building on M1 machines is it would default to building a
arm64architecture app, which cannot run on x86 Intel desktop machines. This reverts the change for desktop builds and uses M1 for iOS as there is no side effects there.Fixed Issues
$ #30396
Tests
Offline tests
N/A
QA Steps
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)myBool && <MyComponent />.src/languages/*files and using the translation methodWaiting for Copylabel for a copy review on the original GH to get the correct copy.STYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)/** comment above it */thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor)thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))Avataris modified, I verified thatAvataris working as expected in all cases)ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
N/A - Build changes only
Android: mWeb Chrome
N/A - Build changes only
iOS: Native
N/A - Build changes only
iOS: mWeb Safari
N/A - Build changes only
MacOS: Chrome / Safari
N/A - Build changes only
MacOS: Desktop
N/A - Build changes only