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
Version Number: v9.1.53-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: n/a Email or phone of affected tester (no customers):gocemate+b215110@gmail.com Issue reported by: Applause Internal Team Device used: Lenovo 80ES / Windows 10 Pro App Component: Money Requests
👋 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.
@lydiabarclay FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
This one is such an odd one. Checked today and I'm still able to replicate in staging(v9.1.60-4). Having issues with rendering Maps on my dev setup atm so can't confirm whether it is reproducible in Dev.
@inimaga@ahmedGaber93@lydiabarclay this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Activity
melvin-bot commentedon May 28, 2025
Triggered auto assignment to @lydiabarclay (
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 May 28, 2025
Triggered auto assignment to @inimaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 28, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 28, 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:
nlemma commentedon May 28, 2025
@lydiabarclay FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
BlameGPT commentedon May 28, 2025
Possible culprit PRs for this issue
Please 👍 or 👎
15 remaining items
ahmedGaber93 commentedon Jun 3, 2025
Sorry I missed that, reviewing today.
melvin-bot commentedon Jun 4, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
ahmedGaber93 commentedon Jun 4, 2025
Able to reproduce it on staging only (v9.1.59-0), production (v9.1.58-4) and DEV last main(v9.1.59-0) work well.
20250605022550039.mp4
ahmedGaber93 commentedon Jun 4, 2025
@mohamedali0887 Thanks for the proposal.
I think your root cause is not correct, we already have the same behavior for
authenticatePusheron production and the issue is not reproduced.inimaga commentedon Jun 9, 2025
This one is such an odd one. Checked today and I'm still able to replicate in staging(v9.1.60-4). Having issues with rendering Maps on my dev setup atm so can't confirm whether it is reproducible in Dev.
ahmedGaber93 commentedon Jun 9, 2025
I just tested it, same as last one #62933 (comment), reproduced on staging only, production and DEV last main work well.
Interesting, look like this issue reproduced on staging only and disappear after deployed to production.
melvin-bot commentedon Jun 11, 2025
@inimaga @ahmedGaber93 @lydiabarclay this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
inimaga commentedon Jun 11, 2025
Hey @ahmedGaber93 headsup, I brought this up internally and we concluded that it's low value, so I've decided to close the issue for now.