-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HybridApp] Android - Log in - User is stuck on Exepnsify logo #44636
Comments
Triggered auto assignment to @sakluger ( |
Triggered auto assignment to @cead22 ( |
👋 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:
|
@sakluger I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We had an issue on staging momentarily that has been fixed. Is this is still reproducible? |
I'm not sure how to test this since I don't have Android and don't know how to test OldDot on Browserstack. I've asked in #qa on Slack for a retest: https://expensify.slack.com/archives/C9YU7BX5M/p1719607064770569 |
@izarutskaya reminder to always include the email you're using when logging bugs |
Is this accurate? I don't see it in the video |
It looks like we successfully get a short lived auth token, and we log Pulling the mobile logs from this log search
|
@cead22 Please check my full video. Thank you Screen.Recording.20240701.121907.mp4 |
I removed the deploy blockers and moved to daily based on @AndrewGable's comment in Slack here. |
@staszekscp - Mind commenting here? Thank you! |
Sure, I'll investigate that! |
@AndrewGable, @staszekscp Whoops! This issue is 2 days overdue. Let's get this updated quick! |
With @mateuuszzzzz we're working on it and progress is being made here. The PR will fix this issue |
Commenting here to be assigned |
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. |
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.3-2
Reproducible in staging?: Y
Reproducible in production?: Unable to check
Found when validating PR : #39074
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Expected Result:
After opening NewDot one should see Explanation modal. (if onboarding is not finished then after closing explanation modal, onboarding modal should appear)
Actual Result:
User is stuck on Expensify logo. As a result, explanation modal opens twice.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6527686_1719596307081.Screen_Recording_20240628_202611.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: