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 2025-09-17] Attachment - Android - unable to attach PDFs #70020
Version Number: 9.2.2-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:https://test-management.browserstack.com/projects/2219752/folder/13176710/test-cases/41236942 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Samsung Galaxy A16 - Android 15, Wi-Fi, Chrome App Component: Android
Action Performed:
Open hybrid android app
Open any chat
Click + in compose box and add attachment
Choose pdf file without password
Choose password protected pdf again
After uploading the Password protected PDF - insert the password (Test12345)
Expected Result:
In step 4, the pdf should be attached in the chat report
In step 6, after inserting the password the pdf preview should be shown
Actual Result:
In step 4, there is no pdf attached in the chat report
In step 6, after inserting the password there is infinite spinner shown
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Attachment - Android - unable to attach PDFs[/-][+][Due for payment 2025-09-17] Attachment - Android - unable to attach PDFs[/+]on Sep 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.8-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@flodnv@lschurr The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]
Activity
melvin-bot commentedon Sep 6, 2025
Triggered auto assignment to @lschurr (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Sep 6, 2025
Triggered auto assignment to @flodnv (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 6, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 6, 2025
👋 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:
ShridharGoel commentedon Sep 6, 2025
#69600
jayeshmangwani commentedon Sep 7, 2025
@flodnv This issue is coming from this PR #69600. I’ve opened a revert PR #70039 for it.
cc: @roryabraham @Kureev
flodnv commentedon Sep 8, 2025
Thanks a lot @jayeshmangwani
francoisl commentedon Sep 8, 2025
Fix tested on v9.2.2-5, all set here.
[-]Attachment - Android - unable to attach PDFs[/-][+][Due for payment 2025-09-17] Attachment - Android - unable to attach PDFs[/+]melvin-bot commentedon Sep 10, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.8-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-09-17. 🎊
melvin-bot commentedon Sep 10, 2025
@flodnv @lschurr The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]