Repository navigation
Android/IOS - Preview page is closed for the picture which just attached without any close action #9334
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
- Launch the app
- Log in with any account
- Select any chat and select plus button
- Select Add Attachment - Select From Glary
- Tap Send
- Open attachment again and wait
Expected Result:
Preview page is not closed for the picture which just attached
Actual Result:
Preview page is closed for the picture which just attached
Workaround:
Unknown
Platform:
Where is this issue occurring?
- Android
- IOS
Version Number: 1.1.73.0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+0901abb@applause.expensifail.com / Feya87Katya
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5600179_Screen_Recording_20220607-092819_New_Expensify.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Activity
OSBotify commentedon Jun 7, 2022
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Jun 7, 2022
Triggered auto assignment to @joelbettner (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.[-]Android - Preview page is closed for the picture which just attached without any close action[/-][+]Android/IOS - Preview page is closed for the picture which just attached without any close action[/+]joelbettner commentedon Jun 7, 2022
We found the PR that was the culprit and reverted it.
joelbettner commentedon Jun 7, 2022
@kavimuru now that #9343 has been deployed to staging, can you please do this test again?
joelbettner commentedon Jun 7, 2022
I went ahead and did the re-production steps and the bug is indeed fixed. I'm going to close this issue.