-
Notifications
You must be signed in to change notification settings - Fork 149
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
Loading state is not a initial state? #52
Comments
I always face this issue when showing empty states, and always came to a different workaround.
It worked for me. |
I am unable to reproduce this issue. The example project calls |
I think this may be the same issue I was seeing here (and I am seeing again): #47 Since the view presentation is being pushed to a subsequent run loop with As I suggested before, you could guarantee that this can't happen in the if Thread.isMainThread {
...
} else {
DispatchQueue.main.sync() {
...
}
} |
However, again I notice that the issue is complicated further by the async queue call, which sounds like it could be the more likely culprit, i.e. we have no idea when this code will be executed in relation to the content view's presentation on the main thread. Perhaps if |
When I open my view controller I can see my empty view momentarily then it switches back to loading state. How to avoid that? Either you introduce a new "Initial State" or make Loading state by default state.
The text was updated successfully, but these errors were encountered: