-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Fix/75109: When auto-reporting is disabled, user cannot submit expens… #75286
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🟡 Issue: Missing defensive empty-participant guard in
createDistanceRequestUnlike
requestMoneyandtrackExpense, this function does not early-return whenparticipantis empty.Today the UI likely always passes at least one participant, but this function is a critical backend boundary between UI and
createDistanceRequestIOUActions. If a future regression allows confirming with no participant (e.g., a bug inMoneyRequestConfirmationList),selectedParticipantscould be[].createDistanceRequestIOUActionsthen callsparticipants.at(0)internally and passes a participant with noaccountIDtogetMoneyRequestInformationwhich will:• Set
payerAccountID = Number(participant.accountID)→0.• Try
getChatByParticipants([0, payeeAccountID]), possibly creating a bogus self / ghost chat.Why this matters / potential bug if left as-is
If this edge case happens, you could end up with:
• Distance expenses linked to a chat that has no real participant (payer account ID 0)
• Confusing history/actions in some “ghost” conversation where nothing else lives
• Potential future crashes if other code assumes a chat’s participants always map to real account IDs
Suggested fix
Mirror the pattern in
requestMoney/trackExpense: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.
👉 This one is still valid even if the "🔴 Regression Alert" fix is applied.