🍒 Cherry pick PR #85807 to staging 🍒#85812
Conversation
(cherry picked from commit e76c7b5) (cherry-picked to staging by cristipaval)
|
@stitesExpensify 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] |
…ign-card [CP Staging] Revert "Fix : Assign new cards - Assign new cards tab with infinite spinner" (cherry picked from commit beb1f88) (cherry-picked to staging by cristipaval) Made-with: Cursor
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 73c622d8f1
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| { | ||
| "name": "new.expensify", | ||
| "version": "9.3.40-8", | ||
| "version": "9.3.40-9", |
There was a problem hiding this comment.
Cherry-pick the actual #85807 revert, not just the version bump
This diff only updates generated release metadata (package.json, Gradle/plists, and the Mobile-Expensify pointer). The PR named in the commit message, #85807, reverts the assign-new-cards spinner change in src/pages/workspace/companyCards/BankConnection/useBankConnection.ts; none of those source changes are present here. If this commit is merged to staging, 9.3.40-9 will be built without the intended revert, so the infinite-spinner regression from #85717/#84313 will still be present.
Useful? React with 👍 / 👎.
|
🚧 @cristipaval has triggered a test Expensify/App build. You can view the workflow run here. |
|
🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
|
| versionCode 1009034008 | ||
| versionName "9.3.40-8" | ||
| versionCode 1009034009 | ||
| versionName "9.3.40-9" |
There was a problem hiding this comment.
Can you confirm if you also want to cherry-pick those commits, @cristipaval?
Reviewer Checklist
Screenshots/VideosAndroid: HybridAppAndroid: mWeb ChromeiOS: HybridAppiOS: mWeb SafariMacOS: Chrome / SafariScreen.Recording.2026-03-19.at.21.48.21.mov |
| @@ -1,209 +0,0 @@ | |||
| import {useCallback, useEffect, useMemo, useRef} from 'react'; | |||
There was a problem hiding this comment.
The conflict was in this file that was added in the PR that we reverted. So it should not be any harm here
|
🎯 @hoangzinh, thanks for reviewing and testing this PR! 🎉 An E/App issue has been created to issue payment here: #85820. |
|
🚀 Cherry-picked to staging by https://github.com/carlosmiceli in version: 9.3.40-10 🚀
|
🍒 Cherry pick #85807 to staging 🍒
This PR had conflicts when we tried to cherry-pick it to staging. You'll need to manually perform the cherry-pick, using the following steps:
Then manually resolve conflicts, and commit the change with
git cherry-pick --continue. Lastly, please run:This last part is important. It will help us keep track of who triggered this CP, and will ensure that version bumps are tracked correctly. Once all that's done, push your changes with
git push origin cherry-pick-staging-85807-23299211354-1, and then open this PR for review.Note that you must test this PR, and both the author and reviewer checklist should be completed, just as if you were merging the PR to main.
Pro-tip: If this PR appears to have conflicts against the staging base, it means that the version on staging has been updated. The easiest thing to do if you see this is to close the PR and re-run the CP.
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectioncanBeMissingparam foruseOnyxtoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari