-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] Suppress video capture option when SmartScanning #54644
Comments
Triggered auto assignment to @slafortune ( |
Job added to Upwork: https://www.upwork.com/jobs/~021873793132527544206 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov ( |
#46336 (comment) It seems that this is a limitation on Android. |
@slafortune, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Just as some context, I've looked into this for a bit and also came to the conclusion that you can't remove some options from the file picker on Android+Chrome, maybe when this API is no longer experimental we'll be able to solve this. |
📣 @LorenzoBloedow! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Reproduced. Yes it seems weird. But I also think it is something we cannot control |
@LorenzoBloedow |
ProposalPlease re-state the problem that we are trying to solve in this issue.We're trying to remove the video capture options when clicking on the media picker icon. What is the root cause of that problem?Using the What changes do you think we should make in order to solve the problem?
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?Check if What alternative solutions did you explore? (Optional)I tried changing the MIME types from the I've attached a video where I click on the media picker (there's a delay because I'm on a development server and my computer is not that great) and it shows the new behavior if this proposal is implemented. Screencast.from.2025-01-07.16-04-34.webm |
@slafortune, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@slafortune @alitoshmatov 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! |
@LorenzoBloedow Thank you for proposal. I think |
@alitoshmatov Hi there! You might've missed it in the discussion but |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@slafortune, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Chrome 132 is the current stable version. |
@alitoshmatov Please see the new support for Android+Chrome that has already landed in the stable version. |
Still you cannot expect every device to have latest chrome version, how about different browsers. I think this is very small issue to completely change our upload logic. Moreover this solution also eliminates an option to use native camera. I know we already show the camera view in page itself, but I think some might prefer to use native camera which provides more control. |
@alitoshmatov Addressing some of your points:
This is why the implementation should check for support by simply checking if the
I'm not sure it changes the entire upload logic, it still uses the same logic, it just adds an if statement:
We could add a button on the right with a camera icon to open the native camera. These are just some suggestions, but if you decide this issue won't move forward can we please close it so I can work on others? I'm still looking for my first contribution so I can only work on one at a time :) |
This means we solve this issue for selected users
I meant it we switch from input based upload to different api which might introduce some other changes and side effects
Feel free to submit proposal on other issues, you are not assigned to this issue yet, the rule is when you get assigned to an issue. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@slafortune, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@slafortune @alitoshmatov this issue is now 4 weeks old, please consider:
Thanks! |
@slafortune, @alitoshmatov 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? 💸 |
No satisfactory proposal yet. TLDR: this issue is normal and is present on other apps, android offers video recording option always when you open file picker. So I think we might close this issue |
Thanks @alitoshmatov - I hadn't realized that is standard for other apps 👍 |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.79-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation (hyperlinked to channel name): expensify_bugs
Action Performed:
Expected Result:
No Video capture option when Smart scanning receipt
Actual Result:
Video capture option displayed for receipt upload
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
az_recorder_20241229_141432.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @alitoshmatovThe text was updated successfully, but these errors were encountered: