-
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
Favicon - Flashing NEW! Expensify.cash and icon without white background can be seen in tab #2636
Comments
Triggered auto assignment to @lschurr ( |
Issue reproducible during today's KI retests |
Triggered auto assignment to @joelbettner ( |
This seems like a safe enough one for me to use to teach myself a bit more about ReactNative. Snagging it! |
Issue reproducible during today's KI retests |
I've spent some time digging into this today. The issue apperas to be that, although we are overriding the a listener inside I'm not entirely certain what that could be but I'll keep poking around to see if I can figure it out, and if I can't, I'll most likely end up pestering @marcaaron who, like a zen master, will present me with React Native koans till I stumble upon enlightenment. |
What is a page title? An alarm clock when the power returns. |
Ah-HAH! So it's line 43 in NavigationRoot.js that is squashing the NavigationRoot.mp4 |
my work here is done |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Expected Result:
I expected no flashing with NEW! Expensify.cash and switching with Expensify.cash
Actual Result:
Flashing with NEW! Expensify.cash and switching with Expensify.cash
Action Performed:
Workaround:
No need, visual issue.
Platform:
Where is this issue occurring?
Web ✔️
iOS
Android
Desktop App
Mobile Web
Version Number: 1.0.34-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5045902_Recording__37.mp4
Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: