[Due for payment 2025-11-06] Android – App crash when avatar Image rotates

[nlemma]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.2.35-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/13176687/test-cases/41236648
Email or phone of affected tester (no customers): sintayewhaylu01@gmail.comi
Issue reported by: Applause Internal Team
Device used: Samsung A16/ Android 15
App Component: Other

Action Performed:

1. Open the Hybrid app.
2. Navigate to Settings.
3. Click on Profile.
4. Click on the avatar and upload an image.
5. Click the Rotate option.

Expected Result:

After the image is uploaded, it should rotate successfully.

Actual Result:

The app crashes and exits upon attempting to rotate the image.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6980545_1761048275798.video_2025-10-21_15-03-43.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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]

Triggered auto assignment to @arosiclair (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[arosiclair]

Reproduced in v9.2.35-0 and not in v9.2.34-2

[arosiclair]

I reproduced this error in dev though the app didn't crash: