[Bug] [$1000] Android - Split/Send/Request money - The transition is not smooth when requesting/split amount

[kbecciv]

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:

1. Go to URL https://staging.new.expensify.com/
2. Login with any chat
3. Go to any group conversation or chat
4. Click the + icon
5. Select Split Bill/Send Money/Request Money
6. Enter an amount and select the Next confirmation button

Expected Result:

The transition should be smooth

Actual Result:

The transition is not smooth

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Mobile Web

Version Number: 1.1.92.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5705912_video_2022-08-27_00-16-16.mp4

Bug5705912_video_2022-08-27_00-14-44.mp4

Bug5705912_video_2022-08-27_00-13-26.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @robertjchen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[melvin-bot]

@robertjchen Whoops! This issue is 2 days overdue. Let's get this updated quick!

[robertjchen]

I'm not sure I see the issue here w/ "The transition is not smooth". Do you have the original Slack discussion or a more detailed description for additional context?

[isagoico]

@robertjchen hello! The transitions between modals is included in our scope when testing the regression. In the video it can be seen that the loading of the Big Number Pad page is glitchy (it's kinda hard to put it into words haha).

If these types of bugs related to transitions are not in scope please let us know and we'll inform the team.

[robertjchen]

Ahh, I think I see it now! These issues are definitely in scope as we want to make the app as well-polished as possible 😉 Let me open this up to our contributors to see if there's a proposal to make it better 🙏

[melvin-bot]

Triggered auto assignment to @jboniface (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[jboniface]

job: https://www.upwork.com/jobs/~0165f8b1c2bb3e578e

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (Exported)

[dylanexpensify]

Yes! Shall we close then @marcochavezf ?

[marcochavezf]

@dylanexpensify Ah I think only the Upwork job, because the problem exists, and we'd want to re-evaluate the issue after the Keyboard initiative is implemented.

[dylanexpensify]

not overdue

[JmillsExpensify]

Snagging this from you @dylanexpensify since I'm on the tracking issue.

[JmillsExpensify]

Now that the keyboard initiative is kicked off, I'm removing the hold.

[JmillsExpensify]

@tgolen Shall you take this one from @marcochavezf as well, since you're leading the tracking issue?

[JmillsExpensify]

Whatever the case, the old Upwork job expired so I have created a new one and also raised the price to $1000 given that this is a mainline initiative for WAQ. https://www.upwork.com/jobs/~0123070f67b356c4b3

[JmillsExpensify]

One final note. @applausebot can you help me re-test this as well, as I don't have an Android device I'm able to test with.

[tgolen]

Sure, I'll take this over.

[JmillsExpensify]

You know what, I think we are done here. I just tested this and the bouncing caused by the keyboard no longer exists. I'm attaching a video of my test just now.

RPReplay_Final1667767622.MP4

[JmillsExpensify]

Given that I'm unable to reproduce I'm closing this issue. Another keyboard issue bites the dust!