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
Native share - Unexpected error appears in chat when sharing an image #80838
Version Number: 9.3.11-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/folder/13176721/test-cases/41236967 Email or phone of affected tester (no customers): n/a Issue reported by: Applause Internal Team Bug source: Regression TC Execution Device used: iPhone 13 iOS 26.2 App Component: Other
Action Performed:
1.On the device media library - Choose a picture or receipt to share through the "Expensify" app 2.Choose the option as "Share" 3.Select any contact or workspace 4.Verify you land in "Share to Expensify" page 5. Click "Share"
Expected Result:
Verify you land in the chat or workspace you choosen to share and the message is displayed Verify that the user should be scrolled to the latest shared image
Actual Result:
"Unexpected error posting the comment. Please try again later " error appears in chat when sharing an image
👋 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 [-]iOS - Native share - Unexpected error appears in chat when sharing an image[/-][+]Native share - Unexpected error appears in chat when sharing an image[/+]on Jan 29, 2026
Classification: Frontend bug
Causing PR: #80242 - Part 6: Remove Onyx.connect for SESSION in Report.ts by linhvovan29546 (Medium-High confidence)
Recommendation: REVERT
PR 80242 should be reverted as it appears to break the iOS native share functionality. The Share extension context may not have the SESSION data properly initialized when deprecatedCurrentUserAccountID is needed for the attachment upload.
Evidence:
The bug is staging-only, matching the PR merge timeline (merged 2026-01-28)
PR 80242 touches src/libs/actions/Report.ts and removes getCurrentUserAccountID function
The Share flow calls addAttachmentWithComment which uses deprecatedCurrentUserAccountID
In the Share extension context, if SESSION is not loaded before the share action executes, deprecatedCurrentUserAccountID remains -1
This causes the API request to fail with generic error: Unexpected error posting the comment
Root Cause:
The Share extension is a separate iOS app extension. When sharing an image, if Onyx SESSION has not fully loaded, deprecatedCurrentUserAccountID is still -1, causing the API request to fail.
Labels: Keeping DeployBlockerCash, Removing DeployBlocker (this is a frontend App issue)
Activity
melvin-bot commentedon Jan 29, 2026
Triggered auto assignment to @JmillsExpensify (
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 Jan 29, 2026
Triggered auto assignment to @marcaaron (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jan 29, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jan 29, 2026
👋 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:
m-natarajan commentedon Jan 29, 2026
Discussed about this issue here
[-]iOS - Native share - Unexpected error appears in chat when sharing an image[/-][+]Native share - Unexpected error appears in chat when sharing an image[/+]OSBotify commentedon Jan 29, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #80242 - Part 6: Remove Onyx.connect for SESSION in Report.ts by linhvovan29546 (Medium-High confidence)
Recommendation: REVERT
PR 80242 should be reverted as it appears to break the iOS native share functionality. The Share extension context may not have the SESSION data properly initialized when deprecatedCurrentUserAccountID is needed for the attachment upload.
Evidence:
Root Cause:
The Share extension is a separate iOS app extension. When sharing an image, if Onyx SESSION has not fully loaded, deprecatedCurrentUserAccountID is still -1, causing the API request to fail.
Labels: Keeping DeployBlockerCash, Removing DeployBlocker (this is a frontend App issue)
linhvovan29546 commentedon Jan 29, 2026
The AddAttachment command returns the error message: “Cannot assign to property 'name' which has only a getter.”
linhvovan29546 commentedon Jan 29, 2026
I can still reproduce the issue locally after reverting the PR above, so that PR is not the cause.
Screen.Recording.2026-01-29.at.14.15.39.mov
m-natarajan commentedon Jan 30, 2026
This issue is reproducible on iPhone 7 Plus / iOS 15.8.3 and Xiaomi Poco F5 / Android 13 in v9.3.11-12
1000175818.mp4
80838_iOS-Repro.mp4
grgia commentedon Jan 30, 2026
Potentially fixed by #80984
grgia commentedon Jan 30, 2026
Asked for retest https://expensify.slack.com/archives/C9YU7BX5M/p1769781152091429
m-natarajan commentedon Jan 30, 2026
Not repro, Xiaomi Redmi Note 10 / Android 12App , iPhone 13 / 26.1 v9.3.11-15, v9.3.11-15
ScreenRecording_01-30-2026.09-46-18_1.MP4
Screenrecorder-2026-01-30-16-01-24-79.mp4
grgia commentedon Jan 30, 2026
Wooo! Thank you @m-natarajan
melvin-bot commentedon Mar 12, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.