-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resubmit contacts import module #54459
base: main
Are you sure you want to change the base?
Resubmit contacts import module #54459
Conversation
…hub.com/margelo/expensify-app-fork; branch 'main' of https://github.com/Expensify/App into @perunt/rerevert-contacts-import-module
I didn't test the Hybrid App as I don't have access yet |
@shawnborton @DylanDylann One of you needs to 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] |
Hey! I've created a PR with adjustments so everything works fine with HybridApp |
Hi! @perunt what's your Xcode version locally? I'm testing PR on HybridApp and I cannot build for simulators (it builds fine on physical device tho). My version is I'm also curious about The key information here is that some people might encounter issues when building on a simulator, while others might not, depending on their Swift compiler version. This can block HybridApp development for people without physical iPhone |
Nevertheless I think this is not a serious issue and we can proceed further with this PR and its HybridApp part 😅 People experiencing issues with the Swift compiler can try downgrading their Xcode version or using a physical device if available. cc: @Julesssss |
I think only remaining thing is to bump Xcode on CI infrastructure. I have this PR that was created before Christmas: #54424 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tentatively approving, seems like we need to confirm first that this doesn't break hybrid app for simulator's as per above comments.
Also I think we need to merge main due to xcode being bumped, which is why the validate github actions check is failing. |
…hub.com/margelo/expensify-app-fork; branch 'main' of https://github.com/Expensify/App into @perunt/rerevert-contacts-import-module
I'm still dealing with Android errors after bumping RN. I'll ping you once it's done |
…rerevert-contacts-import-module
…rerevert-contacts-import-module
I'm not sure about the lint error Apart from this, everything works on my end. As before, I didn't test the Hybrid App because I don't have access to it |
Ah this is from a new eslint rule we made. See announcement here. Its unrelated because we're trying to tackle the changes incrementally instead of doing it all at once in a big PR. So if you touch a file (ex: I'm fine with ignoring it for this PR, its big and complicated enough already that I don't want to add that to the list of things this PR changes, but for future reference we probably want to update those linter issues as we encounter them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, checking with hybrid app engineers before merging: https://expensify.slack.com/archives/C04878MDF34/p1736803862458899?thread_ts=1736210982.318679&cid=C04878MDF34
Looks like C+ should have access to hybrid app now, @DylanDylann can we get your review on this? Obviously no need to review all the code again since you've reviewed the code throughly before, but I'd like you to test this before we merge since @perunt still doesn't have access to the hybrid app repo yet (working on fixing that). |
I verified that it works well on the Hybrid Android App (I am getting some problems while building a Hybrid IOS App, will try to give an update at the end of the day) Screen.Recording.2025-01-15.at.17.23.26.movScreen.Recording.2025-01-15.at.17.30.14.mov |
@perunt Could you please resolve conflict? |
@DylanDylann what kind of problems? |
@mateuuszzzzz No problem on Android, the IOS build failed because of this error |
Could you expand details of |
🚧 @Julesssss has triggered a test hybrid app build. You can view the workflow run here. |
🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
|
First error
Second Error (That you are asking)
|
I think this may be due to our workflow nmv version. I think we are good on staging but not prod yet (where I think the workflow runs).
|
…rerevert-contacts-import-module
@DylanDylann, the code is up to date |
Explanation of Change
Resubmit contacts import module. Additionally was bumped Nitro
During the revert of the NitroModules PR, we identified two main issues affecting our iOS builds. First, there was a mismatch between the minimum iOS deployment target (set to 13.4) and our app's requirement (iOS 15). Second, we discovered build failures specific to iOS simulators due to a known Swift compiler issue.
While investigating, we found that our CI environment was running an older version of Xcode (15.2), which contributed to the build failures. We've addressed this by updating our CI configuration to use newer macOS runners and updating the Ruby GitHub Action version.
To move forward cleanly, we'll be splitting this into two separate PRs:
After implementing these changes in isolation, our test builds are now passing successfully.
revert #54421
Fixed Issues
$ #47938
PROPOSAL:
Tests
Offline tests
QA Steps
// TODO: These must be filled out, or the issue title must include "[No QA]."
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)src/languages/*
files and using the translation methodSTYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)Design
label and/or tagged@Expensify/design
so the design team can review the changes.ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop