Thank you for the response, @RickMaddy To answer your question — yes, we are not using the native back button. Instead, we’ve implemented our own UI button to handle the back navigation.

it is for demo purpose, i am having this kind of real useCase

I included it solely for demo purposes here. It functions correctly when invoked just once. However, in our actual app, the screen refreshes upon receiving response data from the API, and that's when the issue occurs. This behaviour was not present in earlier iOS versions and was working as expected previously.

I included it solely for demo purposes here. It functions correctly when invoked just once. However, in our actual app, the screen refreshes upon receiving response data from the API, and that's when the issue occurs. This behaviour was not present in earlier iOS versions and was working as expected previously.

In our actual app, the screen refreshes upon receiving response data from the API, and that's when the issue occurs. This behavior was not present in earlier iOS versions and was working as expected previously.

I included it solely for demonstration purposes here. It functions correctly when invoked just once. However, in our actual app, the screen refreshes upon receiving response data from the API, and that's when the issue occurs. This behavior was not present in earlier iOS versions and was working as expected previously.

I included it solely for demo purposes here. It functions correctly when invoked just once. However in our actual app, the screen refreshes after received response data from the API call and that's when the issue occurs. This behaviour was not present in earlier iOS versions and was working as expected previously.

I included it solely for demonstration purposes here. It functions correctly when invoked just once. However, in our actual app, the screen refreshes upon receiving response data from the API, and that's when the issue occurs. This behaviour was not present in earlier iOS versions and was working as expected previously.

I included it solely for demonstration purposes here. It functions correctly when invoked just once. However, in our actual app, the screen refreshes upon receiving response data from the API, and that's when the issue occurs. This behaviour was not present in earlier iOS versions and was working as expected previously.