-
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
[$500] App missing parameter triggers backend error #33099
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Triggered auto assignment to @trjExpensify ( |
This comment was marked as outdated.
This comment was marked as outdated.
Job added to Upwork: https://www.upwork.com/jobs/~01c2cd3f67471d554b |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
I am heads down in some other stuff so I am opening this up to contributors to look into it. |
Seems like all these regressions came from same PR: |
Unable to access this issue: https://github.com/Expensify/Expensify/issues/349757 |
One of Tyler's comments is:
|
This is dupe of #33098. |
not sure how i can help here |
Or @tylerkaraszewski can double check before closing, as the fix is now on staging |
I re-tested these flows and they appear to be working, closing this out |
This issue was created: https://github.com/Expensify/Expensify/issues/349757
Because this line:
https://github.com/Expensify/App/pull/30737/files#diff-112aa19f2ab27905a9cd6ce992a483fff32792ea32ede1767f2af6e42e1e548bR130
Seems to have been triggered without a
transaction
object. Since this code was jsut introduced on staging yesterday, I'm assigning @tgolen to look.If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Action Performed:
Break down in numbered steps
Expected Result:
Describe what you think should've happened
Actual Result:
Describe what actually happened
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: