[$1000] Auto focus is broken on New room page

[kavimuru]

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:

1. Login with any account
2. Tap or click FAB menu > New room

Expected Result:

Auto focus on room name input and keyboard shows

Actual Result:

Room name input is not focused and "Create room" button bounces

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?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3..0
Reproducible in staging?: y
Reproducible in production?: y
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

FHQB4145.1.MP4

new.room.bug.mp4

Expensify/Expensify Issue URL:
Issue reported by: @situchan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681493406622809

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0160117b7c7096e58e
• Upwork Job ID: 1651569523514560512
• Last Price Increase: 2023-08-21
• Automatic offers:
• situchan | Contributor | 26258358
• situchan | Reporter | 26258360

[MelvinBot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[MelvinBot]

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

[johncschuster]

I'm not sure how to "tab" the FAB menu on mobile. I've asked for clarity on the repro steps in the Slack thread above.

[MelvinBot]

@johncschuster Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[johncschuster]

I've reproduced the behavior. Triaging!

[MelvinBot]

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

[johncschuster]

Umm... this isn't overdue, Melv.

[techievivek]

This can be worked externally.

[MelvinBot]

Job added to Upwork: https://www.upwork.com/jobs/~0160117b7c7096e58e

[MelvinBot]

Current assignee @johncschuster is eligible for the External assigner, not assigning anyone new.

[MelvinBot]

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

[techievivek]

Awesome, can't we test this on staging to confirm if it fixes this bug or not?

[situchan]

Awesome, can't we test this on staging to confirm if it fixes this bug or not?

Ah yes we can test on staging but only internally. External contributors don't have access to staging iOS build

[melvin-bot]

@johncschuster, @techievivek, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[johncschuster]

@techievivek I'm a bit confused on where we stand on this one. Do we need to test this internally?

[situchan]

This was deployed to production. Not reproducible anymore.

[melvin-bot]

@johncschuster, @techievivek, @situchan Eep! 4 days overdue now. Issues have feelings too...

[johncschuster]

Thanks, @situchan! In that case, can we close this one out?

[situchan]

Thanks, @situchan! In that case, can we close this one out?

yes, and I think I am eligible for reporting bonus

[melvin-bot]

@johncschuster, @techievivek, @situchan Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@johncschuster, @techievivek, @situchan Eep! 4 days overdue now. Issues have feelings too...

[techievivek]

Not overdue, we just need to issue the reporting bonus here.

[techievivek]

@johncschuster Can we issue the reporting bonus to @situchan and close this issue? Thanks

[melvin-bot]

@johncschuster, @techievivek, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[johncschuster]

Sorry I missed this! Yep! I'll get the reporting bonus issued.

[situchan]

@johncschuster I already have accepted contract from $250 offer. Thanks

[techievivek]

@johncschuster Have we finished the payment here? Can I close the issue?

[johncschuster]

Yep! Payment has been issued! We're good to close this one out.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.