LoadingView | LoadingView is easy to implement Loading indicators | Animation library

I will focus only on the call to getData(). Your view is calling the following command:

To avoid refresh all components when data change, you should use "key" attribute for your component.

There are a couple of things that could be adjusted with your code.

• I'd make Load a @StateObject on a parent view so that the LoadingView can be conditionally displayed and not displayed all the time and just default to an EmptyView
• In a ZStack, the topmost view should be last -- you have it first.
• You can use .background(.ultraThinMaterial)

Since for now you just need a loading animation that lasts for a set duration and updates a 0 - 100 value on screen, you can use a ValueAnimator.ofInt

Since you need to use one of the passed-in parameters in the initialization of the @StateObject, you'll have to write a custom init for your View. Using your current code, it would look something like this:

As already written in the comments, a modal view will be shown on top of any other view. A modal view is meant to establish a Computer-Human communication, or dialog (thus modal views frequently will be named "Dialog").

The observation, that a sheet (modal view) covers the loading indicator is expected behaviour.

But, IMO the issue described in the question and refined in the comments, can be solved nicely without breaking the behaviour of the modal views:

When you want to show data, that is not yet complete or even completely absent, you may show a "blank" screen, and in additions to this, let the view model generate a view state that says, that the view should show an "Input Sheet".

So initially, the user sees an input form over a blank screen.

Once the user made the input and submits the form (which will be handled in the View Model) the input sheet disappears (controlled by the View State generated by the View Model), and reveals the "blank" view underneath it.

So, the View Model could now present another sheet, or it realises that the input is complete.

Once the input is complete, the view model loads data and since this may take a while, it reflects this in the View State accordingly, for example using a "loading" state or flag. The view renders this accordingly, which is a loading indicator above the "blank" view.

When the view model receives data, it clears the loading state and sets the view state accordingly, passing through the data as well.

The view now renders the data view.

If the loading task failed, the view model composes a view state where the content is "absent" and with an error info.

Again the view renders this, possibly showing an alert with the message above a "blank" view, since there is still no data.

Ensure, the user can dismiss the error alert and the view model handles it by removing the "modal error" state, but the content is still "absent".

Now, the user is starring at a blank view. You may embed an error message here, or even add a "Retry" button. In any case, ensure the user can navigate away from that screen.

And so on. ;)

It looks like you need to call the SwitchCase function, and also return JSX for each case.

I ended up parsing the entire app's dependency tree to figure out if something was really wrong... came to the conclusion that flow is doing nothing wrong, but our imports are to blame, mostly (I think) due to Redux and Sagas, pulling one import end-ups re-checking the entire app.

You can find my how I figured it out here:

https://ospfranco.com/post/2021/08/25/how-to-visualize-flowtype-dependency-tree/

This looks like a bug of NavigationView: without it animation works totally fine. And it wan't fixed in iOS15.

Working solution is waiting one layout cycle using DispatchQueue.main.async before string animation: