-
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
Hmm it is not here error appears briefly when enabling workflows #40219
Closed
ZhenjaHorbach
wants to merge
13
commits into
Expensify:main
from
ZhenjaHorbach:error-appears-briefly-when-enabling-workflows
Closed
Changes from 10 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
f9845ed
Fix bug with Hmm it is not here error appears briefly when enabling w…
ZhenjaHorbach 2344567
Refactor code
ZhenjaHorbach f8c53af
Fix comments
ZhenjaHorbach 6f5b56d
Remove console.log
ZhenjaHorbach 9e46077
Merge branch 'main' into error-appears-briefly-when-enabling-workflows
ZhenjaHorbach c7e87a6
Refactor changes
ZhenjaHorbach fc54584
Fix eslint issue
ZhenjaHorbach 9568c9f
Fix rare bug with display not found
ZhenjaHorbach 7484834
Rename const
ZhenjaHorbach 268b870
Fix bug with not found after reload
ZhenjaHorbach 92a32a7
Remove unnecessary space and check GPG key
ZhenjaHorbach 601f0c7
Refactor changes and fix bug with not found after reload page and upd…
ZhenjaHorbach 2785b4e
Merge branch 'main' into error-appears-briefly-when-enabling-workflows
ZhenjaHorbach File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have any other solution for this? We avoid using setTimeout
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the problem I described here
#40219 (comment)
And this problem is mentioned here
App/src/libs/actions/Policy.ts
Lines 3915 to 3918 in 268b870
It's still reproduce (even on main branch )
When we navigate
We have cases when isFeatureEnabled equals false for a couple of milliseconds
So why don't we make the navigation happen after the switch animation ends?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's take a look at my video, I posted. I waited for all the request were called, so why are you saying that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry
My fault, I didn't notice that you waited for all the request were called
In this case, I fixed the cases you described )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think your explanation here is correct. Let's discuss our situation here, all APIs were called and we still saw the NotFound screen. That shouldn't happen and I think we can avoid using timeout to fix it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to fix a specific case with these changes
When, after enabling a feature, we navigate immediately
That Onyx.update sometimes does not change the value immediately
As result we have NotFound for a couple of milliseconds
I think problem related with Promise which we use
App/src/libs/actions/Policy.ts
Lines 3915 to 3921 in 268b870
But so as not to cause regression
I was thinking of using setTimeout inside Promise
To be sure that everything is called in the correct order
2024-04-17.13.39.19.mov
(Video is from main branch )
but okay )
I'll try to find an alternative solution )
Thank you for review )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any update here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll look into this issue thoroughly over the weekend
If you do not mind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah yeah, np. Please keep me posted