-
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
[HOLD for payment 2023-03-01] Black area generated above keyboard within company information form #14716
Comments
I would like to investigate this issue, Callstack. |
Job added to Upwork: https://www.upwork.com/jobs/~012f40a9a8f065b869 |
Current assignee @puneetlath is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Current assignee @puneetlath is eligible for the External assigner, not assigning anyone new. |
Thanks @ArekChr! Looking forward to your proposed solution. |
Your issue is in this file {maxHeight: this.props.windowHeight}]} |
Proposal
Solution 1
Example + <ScreenWrapper windowHeight={null} includeSafeAreaPaddingBottom={false}> Solution 2
Result Simulator.Screen.Recording.-.iPhone.14.Pro.Max.-.2023-02-02.at.14.08.31.mp4 |
@parasharrajat Would you be able to look at the proposed solutions? |
Yeah, as soon as I start working today. |
I think this is a regression from #14392. cc: @mananjadhav @sobitneupane can you please handle RCA? @puneetlath Please close the Upwork job. This should be fixed by the author of the main PR. |
IMO, we should revert the PR #14392 as there are two regressions from that PR. In any way, We will have to revert the changes on that PR to solve this regression. |
Would it require removing the MaxHeight property or is the regression in the upstream repo update? |
Yeah, removing |
@rawalyogendra Would you be able to look into this regression fix? 🙇 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.75-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-03-01. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
📣 @MelvinBot! 📣 Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Format:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@rawalyogendra Can you please update with the Regression Test Proposal here? |
|
📣 @rawalyogendra! 📣 Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Format:
|
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@puneetlath this has the title for payment, but there won't be any payout for this one. Instead it should be #11463. |
Yes, makes sense. Thanks for reminding me. I'm going to go ahead and close this out in favor of that issue. |
@puneetlath reporting bonus not issued for this. As I reported this issue. |
📣 @PrashantMangukiya! 📣 Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Format:
|
|
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
My apologies @PrashantMangukiya. Can you please apply to the Upwork job? https://www.upwork.com/jobs/~012f40a9a8f065b869 |
Thank you @puneetlath Applied for the job. |
Reporting bonus paid. Closing again. |
Received. Thank you @puneetlath |
We are looking for another fix to this issue as the approved proposal caused a regression #16082 (comment). |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Black area should not generated above keyboard.
Actual Result:
It will show black area above keyboard as we fill up the form.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.63-0
Reproducible in staging?: y
Reproducible in production?: Could not check
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:
Company-Info-BlackArea.mov
PLBJ7173.1.MP4
Expensify/Expensify Issue URL:
Issue reported by: @PrashantMangukiya
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675181285781359
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: