-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
IOS - Chat -Image added on production (mweb/chrome) does not show on IOS staging, only after re-log #16088
Closed
1 of 6 tasks
Comments
kbecciv
added
Daily
KSv2
Bug
Something is broken. Auto assigns a BugZero manager.
labels
Mar 17, 2023
Triggered auto assignment to @michaelhaxhiu ( |
Bug0 Triage Checklist (Main S/O)
|
9 tasks
I think this might have been just some Pusher issue when they tested this |
@michaelhaxhiu can you try to reproduce? |
Could not repro, probably pusher fail |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Issue found when executing PR #15178
Action Performed:
Expected Result:
Image added on production (mweb/chrome) shows on IOS staging, without re-log
Actual Result:
Image added on production (mweb/chrome) does not show on IOS staging, only after re-log
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.87
Reproducible in staging?: Yes
Reproducible in production?: No
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
Notes/Photos/Videos: Any additional supporting documentation
RPReplay_Final1679087009.1.MP4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: