-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[PAID] Hybrid - Android - Group - Compose box is displayed floating when creating group chat #53185
Comments
Triggered auto assignment to @strepanier03 ( |
Triggered auto assignment to @nkuoch ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
@chrispader @kirillzyusko for 👀 I think we can demote if we are soon to deploy, as this is minor issue that does not block the user completely but it definitely not looking good. Lets discuss in the slack thread https://expensify.slack.com/archives/C01GTK53T8Q/p1732692440640569 |
@staszekscp @mateuuszzzzz could you look into this one please? its not repro in standalone android app. Demoting as its minor ui issue on one platform not blocking the user |
@mountiny I'll grab this one |
Thanks, lets go! |
Not sure if it's the same bug but there is also version when instead of creating group chat opening 1:1 chat breaks display (it can be reproduced in standalone ND) ND_bug.mov |
I'm not able to reproduce bug from this issue anymore. I think I saw it at the beginning but now I'm not able to reproduce it anymore. The animation is not very smooth but in the end composer is on its place. I tried release build as well recording.mov |
@jnowakow Thank you! Lets keep an eye out for it then |
Waiting for reproduction steps |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.78-6 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 2025-01-02. 🎊 For reference, here are some details about the assignees on this issue:
|
@DylanDylann @strepanier03 @DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Payment Summary
BugZero Checklist (@strepanier03)
|
@DylanDylann - I hired you in Upwork, I'll keep an eye out and pay when I see it accepted. |
@strepanier03, @mountiny, @jnowakow, @DylanDylann Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I paid the job and closed the contract, thanks @DylanDylann. Closing this out now. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.67-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5267318&group_by=cases:section_id&group_order=asc&group_id=229067
Email or phone of affected tester (no customers): ibellicotest+41@gmail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
When a group chat is created, compose box and information message should be displayed in a correct position.
Actual Result:
Compose box and group information message are displayed floating on top of the screen when a new group chat is created.
Issue reproducible on hybrid app only.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6677526_1732661631235.Float.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @strepanier03The text was updated successfully, but these errors were encountered: