💡 We might want to consider moving the "internet connection" check above the "while" cycle or adding a retry behavior. I'm a bit worried the current implementation might show the error more often than necessary. Wdyt?
(even if you decide to make some changes, we can implement them later - up to you).

I'm a bit worried the current implementation might show the error more often than necessary.

There's a return@flow after NetworkUnavailable is emitted. I think it will take care of it.

if (!networkUtilsWrapper.isNetworkAvailable()) {
    emit(Failure.NetworkUnavailable)
    return@flow
}

I can move it outside the while loop, if network is gone while fix status is in progress, RemoteRequestFailure will be returned instead of NetworkUnavailable. Is that fine?

adding a retry behavior

I'd really like to add a retry behavior, adding it to the backlog.

I can move it outside the while loop, if network is gone while fix status is in progress, RemoteRequestFailure will be returned instead of NetworkUnavailable. Is that fine?

I think that's fine. However, if you plan to implement the retry behavior anyway, I guess we can just wait until it's implemented and do not make any changes now.