You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-10-22] Payment issue for E/App PR#103940 #104120
@ikevin127 The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/A - Result of the original design
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Prerequisite: Enable the supportTicket beta for the test account.
Connected network
Go to Settings > Help and select Talk to a human.
While creation is pending, verify the header displays Support ticket instead of a title skeleton or the assigned support rep's name. Any pending LHN entry should also use the support-ticket title.
Let the request finish and verify the full dated support-ticket title and conversation load without a not-found page.
Reopen a resolved ticket and verify it opens the ticket chosen by the server.
Offline steps
Open Settings > Help, turn Wi-Fi / internet off, and select Talk to a human.
While the request is pending, verify the header displays Support ticket. The messages can remain loading until the request completes.
Wait for creation to fail (about 5 seconds). Verify the optimistic LHN entry is removed and the app redirects to Concierge without an error message. Reconnect and verify no support ticket was created.
Repeat using the app's Force offline toggle. This can let the backend create a ticket while the client discards the response. Verify the same redirect to Concierge after the failure. Disable Force offline and synchronize: the server-created ticket should appear in the LHN, while the current chat stays on Concierge. Open the ticket from the LHN and verify it loads.
Reload during creation
With Wi-Fi / internet off, select Talk to a human, then reload within about 2 seconds while the Support ticket header is showing.
Reconnect and verify the report resolves to content if the server created it, or the normal not-found screen if it did not. It must not remain on the loading skeleton, and the URL must lose isPendingCreation=true.
Repeat with Force offline, then disable the toggle after reloading. If the server created the ticket, verify its conversation loads on the restored URL.
Activity
melvin-bot commentedon Oct 15, 2026
@ikevin127 The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
ikevin127 commentedon Oct 16, 2026
BugZero Checklist
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/A - Result of the original design
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Prerequisite: Enable the
supportTicketbeta for the test account.Connected network
Offline steps
Reload during creation
isPendingCreation=true.Do we agree 👍 or 👎.
melvin-bot commentedon Oct 21, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 21, 2026
Payment Summary
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Oct 24, 2026
Payment Summary
Contributor+: @ikevin127 due $175 via NewDot
quinthar commentedon Oct 27, 2026
Approved $175 to @ikevin127