Closed kavimuru closed 10 months ago
@strepanier03, @thesahindia Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
We're okay Melvin. @ShogunFire is working on a more specific proposal as well.
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
Issue not reproducible during KI retests. (Second week)
Thank you @mvtglobally 👍
@strepanier03, @thesahindia Whoops! This issue is 2 days overdue. Let's get this updated quick!
@ShogunFire - Do you still plan to submit a more specific proposal for this? Or did you submit it and I missed it somehow?
@thesahindia - Do you think we should continue to hold for more proposals here or raise the price?
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@thesahindia - Do you think we should continue to hold for more proposals here or raise the price?
We haven't got any update from @ShogunFire, so let's increase the price.
Sorry for the delay, I have this proposal that works by changing lottie code, otherwise we can wait https://github.com/Expensify/App/issues/16660 which will remove the fork of react-native-web and allow us to use setDeadline
otherwise we can wait #16660 which will remove the fork of react-native-web and allow us to use setDeadline
I think we should wait.
Let's put this on hold @strepanier03
Got it! I'll put this on hold and move to Weekly. When we're ready to move forward we can change this back to Daily.
Still on hold, the linked PR is open and we're waiting on that.
Still holding for PR merge.
Still on hold.
@strepanier03 I think PR has already merged. We can safely get this off hold.
Great, I've taken this off hold and moved it back to Daily.
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@ShogunFire, can we move forward now?
Friendly bump @ShogunFire, thanks!
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
Still waiting for proposals, all good melvin.
Issue not reproducible during KI retests. (third week)
@strepanier03, @thesahindia Whoops! This issue is 2 days overdue. Let's get this updated quick!
I'll test this again today or tomorrow.
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@strepanier03, @thesahindia Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
It seems to work on Andriod 10. However, there is a problem with Android 12.
@strepanier03 Could you please retest this again?
@strepanier03, @thesahindia 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
Was out of the office. Working on this now.
Here's what I found:
@Tony-MK - Can you add a screencast of your repro and a bit more about your testing device so I can try to emulate your testing parameters?
@strepanier03, Since you couldn't reproduce the bug on Android 12, could this other problem only apply to me?
Listed devices from left to right respectively:
1) Pixel 6 Pro - Android 13.0 2) Pixel 7 Pro - Android 12.0 3) Pixel 7 Pro - Android 12L 4) Pixel 6 - Android 12L
Issue not reproducible during KI retests. (Fourth week)
@Tony-MK - I guess it could be specific to you, but I'm not 100% sure.
I'll do another round of testing and if I still can't repro we can close this out until it becomes relevant again, at which point we can reopen.
Android Chrome
Okay, so I think at this point we close. I've tested on various Android versions and can't reproduce this any longer.
Thanks a lot for the confirmation.
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:
Expected Result:
Toggle switch should switch to ON/OFF when it is tapped again
Actual Result:
The toggle switch only works once and does not respond to subsequent taps
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: needs reproduction Reproducible in staging?: needs reproduction Reproducible in production?: needs reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/771bd7e9-d0ba-4312-ad36-10d25f37a9c8
Expensify/Expensify Issue URL: Issue reported by:@jo-ui Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692040308927449
View all open jobs on GitHub
Upwork Automation - Do Not Edit